Spoolsv.exe crashes after enabling printer driver isolation

    General discussion

  • New issue I'm facing here.

    After enabling print driver isolation on all network print drivers, spoolsv.exe started crashing (processes was utilizing 98-100%).  This is the first time since the print server was migrated from w2k3 to w2k8-r2.  As a result, all the network printers and drivers are unable to load.  Booted server several times in diagnostic/clean/safe mode with little success.

    Any guidance is greatly appreciated.

    • Changed type Bruce-Liu Monday, March 26, 2012 1:55 AM
    Wednesday, March 14, 2012 3:04 PM

All replies

  • If you setup isolation by driver name, the isolated driver setting is in this reg key


    Using policy, it's here

    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers\PrintDriverIsolationOverrideCompat

    I suggest safe mode, then removing the driver names in this key or 0 if by policy and rebooting.

    This is the first time I have heard of this.  I'm interested in get a list of the drivers installed you have the spooler running.

    Alan Morris Windows Printing Team

    Wednesday, March 14, 2012 5:24 PM
  • Forgot to mention that the server is operational again after disabling printer driver isolation through group policy.  The server had to be rebooted after the change.

    Driver Name Environment Driver Version Driver Isolation Provider Server Name Print Processor Packaged Driver Date Inf Path
    TP Output Gateway PS Windows x64 None ThinPrint PRINT01 (local) winprint false 6/18/2008 C:\Windows\System32\DriverStore\FileRepository\oemprint.inf_amd64_neutral_1e110e780b7dbb69\oemprint.inf
    TP Output Gateway Windows x64 None ThinPrint PRINT01 (local) tpwinprn false 7/12/2007 C:\Windows\System32\DriverStore\FileRepository\oemprint.inf_amd64_neutral_dca7bcb7115916d3\oemprint.inf
    RICOH Aficio MP C4500 RPCS Windows NT x86  Isolated Ricoh PRINT01 (local) RPCSPRN false 1/30/2009 C:\Windows\System32\DriverStore\FileRepository\rc96e12k.inf_x86_neutral_e3618c71cba2ba96\rc96e12k.inf
    RICOH Aficio MP C4500 RPCS Windows x64  Isolated Ricoh PRINT01 (local) RPCSPRN false 1/30/2009 C:\Windows\System32\DriverStore\FileRepository\rc96e164.inf_amd64_neutral_5ceb0825e3bcaa50\rc96e164.inf
    RICOH Aficio MP 9000 RPCS Windows NT x86  Isolated Ricoh PRINT01 (local) RPCSPRN false 7/8/2011 C:\Windows\System32\DriverStore\FileRepository\rc37e12k.inf_x86_neutral_3fd19483a0921b7a\rc37e12k.inf
    RICOH Aficio MP 9000 RPCS Windows x64  Isolated Ricoh PRINT01 (local) RPCSPRN false 7/8/2011 C:\Windows\System32\DriverStore\FileRepository\rc37e164.inf_amd64_neutral_fd547b564fa0b2cb\rc37e164.inf
    RICOH Aficio 3245C RPCS Windows NT x86  Isolated Ricoh PRINT01 (local) RPCSPRN false 1/6/2010 C:\Windows\System32\DriverStore\FileRepository\rc8fe12k.inf_x86_neutral_75f78cae673f1ba0\rc8fe12k.inf
    RICOH Aficio 3245C RPCS Windows x64  Isolated Ricoh PRINT01 (local) RPCSPRN false 1/6/2010 C:\Windows\System32\DriverStore\FileRepository\rc8fe164.inf_amd64_neutral_d334ab95084427ad\rc8fe164.inf
    Remote Desktop Easy Print Windows x64 6.1.7601.17514 None Microsoft Remote Desktop Services PRINT01 (local) winprint true 6/21/2006 C:\Windows\System32\DriverStore\FileRepository\tsprint.inf_amd64_neutral_c48d421ad2c1e3e3\tsprint.inf
    Microsoft XPS Document Writer Windows x64 6.1.7601.17514 None Microsoft PRINT01 (local) winprint true 6/21/2006 C:\Windows\System32\DriverStore\FileRepository\prnms001.inf_amd64_neutral_9fe8503f82ce60fa\prnms001.inf
    Microsoft Shared Fax Driver Windows x64 6.1.7601.17514 None Microsoft PRINT01 (local) winprint true 6/21/2006 C:\Windows\System32\DriverStore\FileRepository\prnms002.inf_amd64_neutral_d834e48846616289\prnms002.inf
    HP Universal Printing PS Windows NT x86 Isolated HP PRINT01 (local) hpcpp115 true 6/6/2011 C:\Windows\System32\DriverStore\FileRepository\hpcu115d.inf_x86_neutral_d7a739029c69cf31\hpcu115d.inf
    HP Universal Printing PS Windows x64 Isolated HP PRINT01 (local) hpcpp115 true 6/6/2011 C:\Windows\System32\DriverStore\FileRepository\hpcu115v.inf_amd64_neutral_f6a5b51fb5c5ab11\hpcu115v.inf
    HP Universal Printing PCL 6 Windows NT x86 Isolated HP PRINT01 (local) HPCPP115 true 6/6/2011 C:\Windows\System32\DriverStore\FileRepository\hpcu115c.inf_x86_neutral_89c704d2fef0ef48\hpcu115c.inf
    HP Universal Printing PCL 6 Windows x64 Isolated HP PRINT01 (local) hpcpp115 true 6/6/2011 C:\Windows\System32\DriverStore\FileRepository\hpcu115u.inf_amd64_neutral_4a9d334b04ff58b2\hpcu115u.inf
    HP LaserJet 9050 PCL 6 Windows NT x86 61.74.561.43 Isolated HP PRINT01 (local) HPCPP5r1 true 3/18/2008 C:\Windows\System32\DriverStore\FileRepository\hpc9050c.inf_x86_neutral_da19e7842eb0b37b\hpc9050c.inf
    HP LaserJet 9050 PCL 6 Windows x64 61.74.561.43 Isolated HP PRINT01 (local) HPCPP5r1 true 3/18/2008 C:\Windows\System32\DriverStore\FileRepository\hpc9050u.inf_amd64_neutral_29ca1fb43b80c6c7\hpc9050u.inf
    hp LaserJet 1320 PCL 6 Windows NT x86 61.74.561.43 Isolated HP PRINT01 (local) HPCPP5r1 false 3/18/2008 C:\Windows\System32\DriverStore\FileRepository\hpc1320c.inf_x86_neutral_2b6c9fd50fde559a\hpc1320c.inf
    hp LaserJet 1320 PCL 6 Windows x64 61.74.561.43 Isolated HP PRINT01 (local) HPCPP5r1 false 3/18/2008 C:\Windows\System32\DriverStore\FileRepository\hpc1320u.inf_amd64_neutral_5575b777ec07b135\hpc1320u.inf
    HP Color LaserJet 5550 PCL 6 Windows NT x86 Isolated HP PRINT01 (local) hpcPP6de true 2/23/2008 C:\Windows\System32\DriverStore\FileRepository\hpc5550c.inf_x86_neutral_8ce125ac20f36f36\hpc5550c.inf
    HP Color LaserJet 5550 PCL 6 Windows x64 Isolated HP PRINT01 (local) hpcPP6de true 2/23/2008 C:\Windows\System32\DriverStore\FileRepository\hpc5550u.inf_amd64_neutral_1af25f84a2a48871\hpc5550u.inf

    • Edited by nfts Wednesday, March 14, 2012 7:30 PM
    Wednesday, March 14, 2012 7:03 PM
  • After reinstating the driver isolation, the spoolsv.exe process still utilized 97-99% CPU.  Again, the remediation was to disable via group policy.  Enabled the operational log for print service to see if anything may turn up.
    Thursday, March 15, 2012 12:42 AM
  • If spoolsv.exe is causing 99% cpu usage then it may have a corrupted print file stuck in the system32 folder. To fix it do the following
    Go to Control Panel, Administrative Tools, Services and stop the Print Spooler services
    Turn off the printer.
    Now go to C:\WINDOWS\system32\spool\PRINTERS and delete the files there. You may find some '00002.SHD' and '00020.SPL'. or something similar.
    Now turn your printer back on and restart the print spool service.
    Spoolsv.exe should be at 2% or less.

    Thursday, March 15, 2012 3:27 PM
  • This has happened twice.  And both times, after disabling the driver isolation feature, the printers/drivers loaded and print spooler was functioning normally (under normal conditions, the spoolsv.exe utilizes less than 50%).
    Friday, March 16, 2012 1:40 PM
  • Hi,

    Have you tried 1robert1’s suggestion? If you need further assistance, we may have to analyze memory dump file to narrow down the cause of this issue. It’s suggested to contact Microsoft Customer Support Services (CSS) so that a dedicated Support Professional can help you on this issue.

    To obtain the phone numbers for specific technology request please take a look at the web site listed below.;EN-US;PHONENUMBERS

    If you are outside the US please see for regional support phone numbers.


    Tuesday, March 20, 2012 2:01 AM
  • When the spoolsv.exe service crashes, I am unable to stop it through the services mmc.
    Tuesday, March 20, 2012 2:20 PM
  • Then, to narrow down the root cause, I suggest you contact CSS to analyze some dump files as forum is not the best place for analyzing dump. With CSS, a dedicated Support Professional will help you on it.

    Hope the issue will be resolved soon.

    Wednesday, March 21, 2012 2:15 AM
  • There should be a solution without contacting CSS, no?
    Tuesday, March 27, 2012 6:26 PM
  • Bruce is refering to generating some dump files of the spooler process and analyzing those.  Why set all the drivers to Isolated?  Shared should be fine?  Isolated is mainly for a single known bad driver that fails more than it works.

    Alan Morris Windows Printing Team

    Wednesday, March 28, 2012 1:14 AM