So yesterday I had a go on restoring a dead printer spooler service, a user had tried installing a HP printer using the installation wizard on the CD and something went terribly wrong and crashed the service.
The service would start but would quickly come to a halt displaying a DEP warning and you would never get anywhere near the printers.
I tried reinstalling Windows Server 2003 SP2 in the hope that any corrupted DLL’s etc would be refurbished but to no avail, in hindsight I should have tried SFC.EXE /Scannow (checks vital Windows files) but hindsight is often way too easy 
There was no HP Jetdirect or other suspect things to uninstall.
Then I moved to restore the printers using PrintMig (we do have backups handy for just such occations see http://www.kanmandet.dk/?p=256) however as the Spooler service was not running this was impossible.
Then the time came to cleanspl.exe from the resource kit for Windows 2003 server, this was a partly success as it actually enabled the service to start – great – but as I just had clicked ‘yes’ to everything even the regular TCP/IP printing was disabled as well as ALL printers (the latter was to be expected as that is what cleanspl.exe does), ok so I tried again restoring the printers backed up with PrintMig and the problems was back the service once again could not start.
Examination of the eventlogs and the registry let me to believe that the culprit was the “HP Standard TCP/IP port” monitor, so after making an export of the registry, I moved to delete ALL but the LPR, Standard TCP/IP Port, USB monitor and local Port under the registry key “HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlPrintMonitors”, and sure enough now the spooler service again was up and running. Now I reverted to the exported registry and then repeated the process just removing one monitor at the time, and viola once the “HP Standard TCP/IP port” was gone the service worked fine.
So here are my suggestions if you ever run into a similar problem;
1. Before this ever happens make a backup of your printers using PrintMig
2. Run SFC.EXE /Scannow just to be sure no important windows files are corrupted.
3. Check the eventlog see if you can find any references to a “monitor” name (from the; “HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlPrintMonitors” registry key).
4. Make an export of the registry branch;
“HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlPrintMonitors”,
5. Try to delete one sub-branch of the;
“HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlPrintMonitors”,
branch at a time, after each delete try to start the spooler service.
A tip to prevent things like this to happen is to avoid all custom “monitors” (specially installed printer management software and ports), use regular TCP/IP and LPR ports whenever possible, sure it’s easier to install using some HP installation wizard but it is often not necessary and your windows installation will love you for not installing all that ‘crap’.
Some helpful links;
http://members.shaw.ca/bsanders/CleanPrinterDrivers.htm
http://www.windowsreference.com/windows-xp/how-to-clean-print-spooler-in-windows-xp2003/
http://www.pcreview.co.uk/forums/thread-3490411.php
So you would like to run MSRT manually (the Microsoft Malicious Software Removal Tool, the one that comes once a month from Microsoft via Windows Updates and cleans different infections from your pc), well as written in an earlier post http://www.kanmandet.dk/?p=463 you can download a version straight from Microsoft, however it turns out there is an even easier method, simply go to your “start menu”, select “Run” and enter “MRT” and hit enter..
For many years I have used Mdaemon as my mailserver, its very easy to use, have great security and anti spam, have very little hardware requirements and a superb webmail client.
Pioneer has announced that they will halt production of 
So the storyline from all those SciFi films are one step closer to fulfillment, it would seem that scienstists have optimized earlier effords in this field to provide a even better version of their ‘cloak’.
