Spend any time working in windows and sooner or later something will upset Windows Explorer, and when it crashes it has a habit of taking something with it (usually your desktop experience – or something you’ve been working on and have not saved!).
The underlying problem can be anything from some poorly coded software, a dodgy device driver, or a wayward Windows update. But you can offset the problem by running Windows Explorer in its own sandboxed process, then if it does fail, it wont break anything else.
Warning there is a slight performance overhead to doing this but if you have a reasonable machine – crack on!
Solution
1. Open Windows Explorer (Windows Key +E)
2. Click Tools > Folder Options > View > Place a tick next to “Launch folder windows in a separate process” > Apply.
Note: If you can’t see the Tools Menu Press F10.
Related Articles, References, Credits, or External Links
This is seen on Windows 7 Clients, when logged onto a domain, after unlocking the machine. If you inspect the Event Log you will see Event ID 1015
“A critical system process, C:Windowssystem32lsass.exe, failed with status code 255. The machine must now be restarted.”
Solution
I put up with this for a while, and did a lot of Internet searching, some people suggested power settings and a host of other stuff, nothing worked, The final solution was found on “Technet”, it involves changing the authentication method to the domain, and needs a registry change.
1. Start > In the Start Search box type type regedit > {enter}
2. Navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLsaKerberosParameters
3. Create a New DWORD entry called DefaultEncryptionType
4. Set its value to (decimal) 23 or (Hexadecimal) 0x17
5. Reboot the machine.
Or If you are feeling lazy just download this, extract and run it, then click “Yes” to add it to the registry, and reboot.
Related Articles, References, Credits, or External Links
If that is the case then you need to exempt both your user and the computer from this method of printer deployment while you are troubleshooting.
Solution
1. As we cant be sure what printer/driver is causing the problem, we need to remove them ALL > Devices and Printers > Select each one in turn, and remove (Note: Keep one for the next step, but remember to delete that also when you have completed the next step).
2. Select your last printer > Print Server properties > Drivers > Remove them ALL.
3. Launch ‘appwiz.cpl’ and ensure there is no printing software installed, if there is uninstall it.
4. Launch ‘services.msc’ > Locate the Print Spooler service and ensure it is set to log on as ‘Local System’.
Note: As shown, from here you can manually start the service, but for now we will leave it as it is.
8. Start > In the search/run box type ‘regedit’ > navigate to;
[box]
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Print > Environment > Windows NT x86
[/box]
Here there should be two sub keys called Drivers and Print Processors, if there are any more delete them.
Warning: You might want to right click and ‘Export’ the keys in case anything explodes, you can simply double click the ‘exported’ file to merge it back in.
9. If your machine is running x64 bit Windows navigate to;
[box]
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Print > Environment > Windows x64
Here there should be two sub keys called Drivers and Print Processors, if there are any more delete them.
Warning: You might want to right click and ‘Export’ the keys in case anything explodes, you can simply double click the ‘exported’ file to merge it back in.
10. Now navigate to;
[box]
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Print > Monitors
[/box]
Here delete ALL Keys Except,
AppleTalk Printing Devices (This may not be present)
BJ Language Monitor (This may not be present)
PJL Language Monitor (This may not be present)
Local Port
LPR Port (This may not be present)
Microsoft Document Imaging Writer Monitor (This may not be present)
Microsoft Shared Fax Monitor
Standard TCP/IP Port
USB Monitor
WSD Port
11. At this point, physically unplug all printers from the PC, (make sure no scripts or group policies are going to attempt to reinstall the printers). Then reboot the machine.
12. When the reboot is complete, make sure the Print Spooler service stays up without error.
13. Get the latest drivers for your printer(s) and reinstall them one by one, (I would say after each printer install, let the system run until you trust it, before installing the next printer).
Print Spooler Fails when attempting to print from Internet Explorer.
If this problem only manifests itself when printing from IE, then go to Internet options > Advanced > Reset.
12. If that does not rectify the problem, make sure you are running the latest version of Adobe flash (or for troubleshooting remove the current version).
Related Articles, References, Credits, or External Links
When using the Exchange Admin Center with Exchange 2013, on a Server Running Internet Explorer Version 10, you see the following error (particularly when working on the recipients > mailboxes tab!
Problem Details
Problem signature:
Problem Event Name: APPCRASH
Application Name: IEXPLORE.EXE
Application Version: 10.0.9200.16384
Application Timestamp: 50107ee0
Fault Module Name: msvcrt.dll
Fault Module Version: 7.0.9200.16384
Fault Module Timestamp: 5010ae12
Exception Code: c0000005
Exception Offset: 0000986a
OS Version: 6.2.9200.2.0.0.400.8
Locale ID: 2057
Additional Information 1: a65c
Additional Information 2: a65c2884b2d8aca525c1cbb50e388db9
Additional Information 3: 396e
Additional Information 4: 396e9fe5e0fa1a3f9a73d5b2c9681128
You can also round the problem by accessing the Exchange Admin Center from a client (Windows running IE10 works fine). If you must access it on the server install the hofix or use Firefox
Related Articles, References, Credits, or External Links
