Occurs on Server 2008R2, 2016, and 2019, but not Win10. Sumatra is set as the default pdf reader. Sumatrapdfrestrict.ini is set to allow printing, but not allow disk access. Opening a pdf and trying to print results in a “Couldn’t initialize printer” message. Simply right-clicking a file and selecting Print works fine. Happens for both local and client printers. If I change the ini file to allow disk access, printing does work; however that also gives the users access to the file system via open/save dialogs, which we can’t have.
I see that DiskAccess restricts a fair number of things. Is there a way to allow the printing function to do whatever it needs to without allowing open/save, hyperlinks, etc.?
I would swear this worked until recently; users would certainly have been complaining. I would blame it on Windows updates, but that wouldn’t explain the 2008R2 machines, nor why it still works on Win10.