For some time on my Windows 10 desktop PC, neither does the "Microsoft XPS Document Writer" nor the "Microsoft Print To PDF" virtual print drivers seem to work.
Whenever I try to print a document using either one, it prompts a file dialog for me to pick a filename and location, and when I click OK to print, it does nothing. The dialog window disappear, no error is shown, and nothing else happens. When I look at the directory where the file was supposed to be created, there is nothing, not even a zero-byte file. The directory where I save the file does not have any special characters in it (no comma), and I have full admin access to it. The Windows Event Viewer doesn't show any error either.
If I try to print a test page using the Printer properties panel of each virtual printer, it gives me an error saying "Test page failed to print." and proposes me to use the troubleshooter (which I did and it found nothing).
I have also tried to uninstall and reinstall both printers (using the "Turn Windows features on or off" panel), with a reboot in between, but that didn't fix the issue.
I have a network printer installed which is working fine. User access Control is also disabled (slider all the way down) and my account type is administrator.
This used to work before (although I can't pinpoint when exactly as I don't use it often enough). I suspect it was caused by a Windows update, but since Windows 10 updates are mandatory and can't easily be excluded, even if I uninstall the last updates in the Installed Updates list, they come back the minute I reboot, and I can't hide them like I could in Windows 7.
This is a fresh install of Windows 10 Pro, and not an upgrade.
I have spent quite a while searching Google for this issue but the only cases I found were about commas in the filename or path and was only affecting printing from Edge, which is not my case. Any help would be appreciated. Thanks !
Best Answer
When Microsoft CEO Satya Nadella has decided to cut 5,500 Microsoft employees, with Windows hit the hardest, much has changed in the Windows world. Nadella has cut a lot of testing engineers, adding the role of testing to that of product manager, and relying much more on the Windows Insider Program.
Unfortunately, that coincided with the release of Windows 10, an operating system that was rushed out much too soon and without enough testing, relying instead on a very rapid rhythm for updates to fix the expected problems, which did arrive soon after.
Unfortunately again, because of a lack of testing and quality assurance, the fixes that are now being rushed out tend also to cause problems in their turn.
It is with great sadness that I witness on this forum, after each and every major update of Windows 10, the arrival of new problems. Most of them have no solution except waiting for a fix from Microsoft or downgrading back to the very stable Windows 7.
So there are very few solutions that I can offer to your problem :
Run sfc /scannow to verify that, for Windows, its actual broken state is "normal".
Check the Event Viewer for error messages relating to your problem.
Report the bug to Microsoft using the "Windows Feedback" app and wait for it to be fixed.
Use a third-party product, such as the CutePDF Writer that you have already tried and found to work properly, as a temporary solution until the problem is fixed by Microsoft.
As a sort of desperate measure, in case the 1511 Windows 10 update caused the problem, you could maybe find a post-1511 ISO and do a clean install of Windows 10. This is in the slight hope that some Windows component that wasn't fully updated before would now work correctly.