DamienG1127

We are trying to ensure users are using either Chrome or IE and setting Adobe Reader as Default using a DefaultAssociations XML. However just one slipping the net or forgetting is then causing downtime for everyone else until the Print Spooler is restarted. It seems Windows 10 in general is really temperamental when it comes to network printing.

Good Morning, I am just posting for some advice and guidance if possible regarding network printing and Windows 10. Regardless of printer manufacturer we are getting a similar set of symptoms where when you try and print to a Network shared printer from a Windows Server, you either get stuck with Spooler crashing or other symptoms happening such as weird symbols printing etc. We have implemented a couple of fixes into this. First one being to set Driver Isolation to None and to also change the printer from spooling to print directly. It seems to be mainly if someone prints a PDF using Windows 10 mostly via Edge. Can you advise if you have had these symptoms before and if so if there has been any known reported fix for this? Thanks, Damien