Share via

Microsoft Print to PDF Keeps Disappearing after ca. 1hr or so on a RDS Server

Anonymous
2024-07-31T12:05:10+00:00

Microsoft Print to PDF Keeps Disappearing after 1hr or so on a RDS Server 2016

We did different types of troubleshoting methods, but non of them helps.

Already tried solutions.

  • Disabled and re-enabled the Microsoft Print to PDF feature.
  • Set Microsoft Print to PDF as the default printer.
  • Reinstalled Microsoft Print to PDF drivers.
  • Updated Windows 10.
  • Removed ALL the print queues just in case.
  • Rebooted the machine multiple times.
  • Cleared all print jobs and restarted the Print Spooler service.
  • Disable and Enable Microsoft Print to PDF Feature from Command Prompt
  • Disable and Enable Microsoft Print to PDF from Windows PowerShell.
  • sfc /scannow in CMD

Can somebody help me solve this issue?

Thanks in advance.

Windows for business | Windows Server | User experience | Print, fax, and scan

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-08-01T02:42:43+00:00

    Hello,

    Have you made any recent configurations or updates on both the server and client sides? If the issue only started after an update, it's likely that the update is causing the problem. A temporary solution could be to uninstall the update and wait for a new one to be released.

    Does this issue affect all RDP clients attempting to access Server 2016? Does it occur during console sessions as well?

    Also confirm the following:

    1. The nprint.inf_amd64_guid and ntprint.inf_x86_guid driver files are present in the c:\windows\system32\DriveStore\FileRepository folder.
    2. The c:\windows\inf\ntprint.inf file may be missing.
    3. The HKEY_LOCAL_MACHINE\DRIVERS\DriverDatabase\DriverInfFiles\ntprint.inf reg key is missing.
    4. Permissions were missing from the ntprint.inf_xxx_guid files. Only SYSTEM is listed.

    Additionally, monitoring system logs and event viewer for any relevant error messages or events can provide insights into the root cause of the issue and help in resolving it effectively.

    Best regards,

    Karlie

    0 comments