So, it may be that there is a problem in one of these third-party modules. You might consider either selectively uninstalling printers; if you notice that the behavior changes after uninstalling a printer, the driver for that recently uninstalled printer may be buggy, and you may wish to check for an update for that driver.
Or, you might choose to leave that printer uninstalled. Or, you could just try updating all printer drivers. However, there may not be an update available that addresses the problem you are encountering, or the problem may be some other component loaded into spoolsv. Given the nature of the process, though, a printer driver seems to be the most likely culprit, so I'd suggest starting there.
I'd expect that restarting the print spooler service would cause the CPU usage to drop, and the RAM consumption to be reduced. You might also wish to set the startup type for the Print Spooler to Manual, and start it only when you need to print.
Stop the service when you are finished printing. Of course, these would just be workarounds Saturday, February 6, PM. Hi DamPee, In addition, I would like to suggest you perform the following steps to check the issue.
Monday, February 8, AM. The materials may include technical inaccuracies or typographical errors and may be revised at any time without notice. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Turn off the printer. Turn printer back on and restart the service. Ya I am not trying to be callous, what I am getting at is I don't know if there is much you can do outside of moving to esx.
From what I get in your description, you are running a terminal server in a virtual box, and using it as a print server. I dont know what that would do to a box. Does each terminal session try to share out it's printers? Maybe that is causing the issue? Could it be that someone is trying to access the spool service such as the hokey 32 bit only app :.
As mentioned above, stop the Print Spooler, set it to manual, reboot the server and see if it pops up again, if it does you have a virus. If everything works smoothly, start the spool service manually and see if the usage spikes again. Then start looking to see what is accessing the spool service by looking in your process monitor. Are you using HP printers? I had this issue before - you have to delete a HP file and replace it with a blank text file with the same name.
I had this a while back, on vmware 1. Brian Smallwood. I had problems with the spooler taking all the CPU when printing to a network resource with a virtual drivers. The printers we had only supported a windows type driver GDI, I think is called. This type of driver did not work thru Citrix and most likely thru TS it would not either. Beside installing the PCL board there was nothing else to do, but not use those printers when connecting to the remote servers.
Another problem that I saw after converting a server was that a program was using the LPT port to create file reports in crystal report format. I needed to add the LPT port to the virtual server.
It will list the OS all the drivers are for, and I've found that removing all the ones not being used - especially those labelled NT fixes this problem and a few other TS printer problems. System Restore fails during recovery. Best Answer. JoeWilliams This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. Clearing out all the entries from the Monitors and Printers keys stopped the misbehaviour. View this "Best Answer" in the replies below ».
0コメント