Microsoft Print to PDF Errors on Windows Server 2016 via Remote Desktop

Glenn Barber 1 Reputation point

We have had a number of problems with Microsoft Print to PDF on Windows Server 2016 which is used as a remote desktop host.

The Printer seemed to disappear from the selection of printers - but it appears to be in an error condition - and wont let us either remove it or replace it..

I see other postings about similar problems but no real solutions.

How do we correct this problem?

(Please - nobody with answers for Windows 10 - its a different beast)

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,311 questions
Windows Server Printing
Windows Server Printing
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Printing: Printer centralized deployment and management, scan and fax resources management, and document services
627 questions
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Anonymous

    Hi, For better clarity and to assist you better I would require more information regarding this: 1. Please run the command get-hotfix via PowerShell on the Windows Server 2016 to see if there is an update installed recently? 2. Is it a simple RDP connection from the client to the client, or in an environment where the RDS server is deployed? By the way, is it possible provide a screenshot and attach a description, which will help us to troubleshoot. Please make sure that the pictures you post do not contain your company and your private information (including but not limited to domain name, public IP, email account, domain account, etc.). These private information must be altered. 3. Please compare the drive folder permissions and drive file content of Microsoft Print to PDF and whether these is the same as the working fine Windows Server 2016 based on the figure below. ![98869-annotation-2021-05-24-140751.png][1] ![98898-annotation-2021-05-24-140814.png][2] ![99011-annotation-2021-05-24-140905.png][3] C:\windows\System32\DriverStore\FileRepository\prnms001.inf_amd64_10bd6dee10a7dfd0 ![99022-annotation-2021-05-24-141910.png][4] If the answer is helpful, please click "Accept Answer" and upvote it. Best regards [1]: /api/attachments/98869-annotation-2021-05-24-140751.png?platform=QnA [2]: /api/attachments/98898-annotation-2021-05-24-140814.png?platform=QnA [3]: /api/attachments/99011-annotation-2021-05-24-140905.png?platform=QnA [4]: /api/attachments/99022-annotation-2021-05-24-141910.png?platform=QnA

    0 comments No comments

  2. Anonymous


    Haven't received your message in a few days, was your issue resolved?

    I am proposing previous helpful replies as "Answered". Please feel free to try it and let me know the result. If the reply is helpful, please remember to mark it as an answer which can help other community members who have the same questions and find the helpful reply quickly.

    Best Regards.

  3. Anonymous

    Hi, is everything ok?

    0 comments No comments

  4. Norman Viljoen 1 Reputation point

    Hi all, I can recreate what seems to be the same issue reported above. In a Windows Server 2016 RDP session choose a redirected "Microsoft Print to PDF (redirected 2)" for example and then select the print test page under the manage options. Provide a file name and select save. Then to create the error, do the same print options but use the same file name that you used previously. You will get the overwrite warning "Do you want to replace?" Select Yes and you will see the error condition happen. In the Printers and Scanners page you will see the redirected pdf writer showing Error. The only way to fix this is to recycle the termsrv on the windows 2016 host.

    0 comments No comments