![asus drivers for windows 10 printspool asus drivers for windows 10 printspool](https://1.bp.blogspot.com/-zEZld9zYDnQ/WusjwGh02kI/AAAAAAAAGfc/4a4qiCT-lVYnt4Fu2x76js0oZIXxiQyOACLcBGAs/s1600/net-start.png)
If there is a bogus path for the spool directory DefaultSpoolDirectory under, we log that information to the desktop log file.If ntprint.inf is missing, we log that to the desktop log file.If any of the core print spooler binaries are missing (spoolsv.exe, spoolss.dll, localspl.dll, win32spl.dll), the package attempts to copy that file from dllcache – if they aren’t present in dllcachce, we log that in the desktop log file.Ensure that the winprint print processor is present for the architecture of the computer – for example:.Make sure the standard print monitors are present (USB, Local Port, and TCPIP) under (and WSD on 2008/Vista only).Turn on logging of print errors and warning to the event log (Printers -> File -> Server Properties -> Advanced Tab -> “Log spooler error events” and “Log spooler warning Events” will be checked).Delete any print jobs from %windir%\system32\spool\printers (shd and spl files).Remove any dependencies that the spooler may have on 3rd party services.Set the print spooler service back to its defaults (automatically start, run as Local System, etc.).
![asus drivers for windows 10 printspool asus drivers for windows 10 printspool](https://60a99bedadae98078522-a9b6cded92292ef3bace063619038eb1.ssl.cf2.rackcdn.com/images_TechSupportArticlePix_9796Image5.jpg)
#Asus drivers for windows 10 printspool windows 7
Obviously, it doesn't even clear out the spooler files (because that's one of the suggestions to try if running the troubleshooter didn't help).Īs explained in the TechNet blog I linked, the Windows 7 tools: What exactly does the printer "Troubleshooter" do? Is there any similar tool available for cleaning out/resetting the printing subsystem for Windows 10? I assume that the script will not work on Windows 10, although I haven't tried it. Of course, Microsoft "retired" these helpful routines long before the actual end of Windows 7 support.įortunately, however, the PowerShell script that was the guts of the FixIt routines was preserved, and is still available at GitHub: For the latter OSes, the tool was released as a "FixIt" automatic routines. The tool was later modified to work for Windows 7 and Server 2008 R2. This was quite useful in situations where nothing else could get a printer installation working. Quite a while ago, Microsoft had a tool for resetting the Windows printing subsystem.