Microsoft Server 2008 Standard Edition (Not R2)
DHCP, DNS, Print Server
Virtual Machine (VMWare, ESX Version 4, VMTools installed)
Recently a change was made to my server in which a printer driver was installed without being tested and no snapshot or backup of the server was made before it was installed.
It was specifically for a Kyocera KM-5035. As far as the Driver version I believe it was KM-5035 KX.
Anyway, ever since this installation, the print spooler service is constantly eating up CPU at about 100%.
Here's what I've done so far:
1. Reinstalled the original printer. No good
2. Removed driver using Print Manager. No good.
3. Restarted Server. No good
4. Stopped sharing all printers. No good
5. Deleted printers that used the new driver. No good
6. Restarted the spooler service numerous times.
7. Went to System32/Spooler/PRNTERS and deleted and SPD and SHD files. No good
The worst part about this is that if anybody is connected to the print server, their spooler service starts eating up CPU on their workstation also. Nonetheless, trying to access a print dialog causes any application to freeze as it tries to access the print server.
I cannot delete the networked printer from their list either, as it seems to freeze again.
The only current fix I have right now is to turn off the print spooler service and allow people to work that way. Pretty much they just can't print, though it seems that those that are not connected to the 5035's can print to other printers. Otherwise, our print server is just constantly at 100% CPU usage at the moment and I can't figure out what to do.
It seems as though I have uninstalled the new printer driver, the spool service still won't return to normal.
I would prefer not to remove every driver of every printer, as there about over 30 of them. I'm hoping some experts can help me find an alternative to doing this.