Microsoft Print to PDF feature no longer appearing for MAC Windows App users on 2022 Server

Thomas Gellar 5 Reputation points
2026-10-19T14:10:36.7333333+00:00

Running a Windows 2022 Server on AWS, the Microsoft Print to PDF feature no longer appears to enable MAC remote desktop clients to print to redirected printer.

Any advice to restore that capability?

Windows for business | Windows Server | User experience | Remote desktop clients
0 comments No comments

3 answers

Sort by: Oldest
  1. AI answer

    2026-10-19T14:12:56.5966667+00:00

    Microsoft Print to PDF is a server-local virtual printer and does not provide Mac physical-printer redirection, so first determine whether the missing item is “Microsoft Print to PDF” itself or a Mac printer whose name should end in “(redirected n).”

    If the Mac printer is missing

    1. Verify Windows App is redirecting printers.
      • Edit the Server 2022 remote-PC entry in Windows App.
      • Open Devices & Audio and enable Printers, if that control is available.
      • For a direct remote-PC connection, Use customized settings does not apply; do not expect that checkbox. For managed resources, select Use customized settings, enable the required device, and save. Windows App for macOS supports printer redirection, subject to administrator policy. ^1^
      • Disconnect completely and start a new session.
    2. Apply the Mac permission workaround if Windows App lost printing after a macOS or app update.
      • Open macOS System Settings → Privacy & Security → Local Network.
      • Enable access for Windows App or Microsoft Remote Desktop, whichever appears.
      • Fully quit Windows App, reopen it, and reconnect.
      This is a community-reported workaround for Mac Windows App printing failures, not a documented RDP prerequisite or guaranteed Server 2022 fix. ^2^
    3. Verify the effective Server 2022 policy using an administrator account.
      • Run gpresult /h C:\Temp\gpresult.html or Resultant Set of Policy first.
      • Check: Computer Configuration → Policies → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Printer Redirection
      • Set Do not allow client printer redirection to Disabled or Not configured.
      • Set Use Remote Desktop Easy Print printer driver first to Enabled or Not configured.
      • Apply the GPO, restart the server as documented, and establish a fresh session. ^3^ ^4^
    4. Check whether Easy Print created redirected queues.
    $printers = Get-Printer |
        Where-Object DriverName -eq 'Remote Desktop Easy Print'
    if ($printers) {
        $printers | Sort-Object Name | Format-Table Name, DriverName -AutoSize
    } else { Write-Host 'No redirected Easy Print queues found.' }
    

    Redirected queues should appear under Settings → Printers & scanners with names ending in (redirected n). They use Remote Desktop Easy Print; the remote session does not need the Mac printer’s vendor driver. ^3^

    Conditional server repairs

    Only use these after effective policy and client redirection have been verified:

    • If both fEnablePrintRDR and fEnableRDR are 0 under
      HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\rdpwd, set both to 1. This repair applies specifically to that registry condition. Back up the keys first. ^5^
    • If no printers redirect and the spooler security descriptor lacks the Authenticated Users entry AU, use Microsoft’s documented sc sdshow spooler procedure to preserve the existing descriptor and add the missing ACL. Do not replace the descriptor with a generic value. ^4^

    If only Microsoft Print to PDF is missing

    On Server 2022, run OptionalFeatures.exe, enable Microsoft Print to PDF, restart if requested, and confirm it appears as a local server printer. This restores PDF-file creation inside the server session; it does not restore Mac physical-printer redirection. ^6^

    The published 2025 Print-to-PDF update defect applies to Windows Server 2025, not Server 2022, so its KB-specific fix should not be applied solely because the printer disappeared.

    If every check passes

    Test the same Mac, printer, account, and Windows App version against another Windows host. A recent matching report describes redirection working to Windows 11 but failing against Server 2022, without an accepted resolution or an official Microsoft known-issue bulletin. ^7^

    If that comparison reproduces the Server 2022-only failure, open a Microsoft Support for Business case and include:

    • macOS and Windows App versions
    • Server 2022 build number
    • effective gpresult
    • Easy Print query output
    • PrintService and TerminalServices event logs
    • TSS User Experience printing traces, as recommended by Microsoft ^4^

    References

    1. Redirect local devices, audio, and folders in Windows App
    2. Unable to print on the windows app (Remote Desktop) from my iMac - Microsoft Q&A
    3. Configure printer redirection over the Remote Desktop Protocol (azure-virtual-desktop)
    4. Windows Server printer redirection isn't working
    5. Printer redirection and drive redirection don't work in a Terminal Server session
    6. Hi, I can't add Microsoft Print to PDF - Microsoft Q&A
    7. Server 2022 Printer Redirection not working for MacOS using Windows app ...
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. Chen Tran 13,695 Reputation points Independent Advisor
    2026-10-19T16:58:31.29+00:00

    Hello Thomas Gellar,

    Thank you for posting question on Microsoft Windows Forum!

    The fact of the matter is that Microsoft Print to PDF and Mac printer redirection are two entirely separate mechanisms. The former is a local virtual printer on the server for creating PDFs inside the session, while the latter is the feature that allows a Mac's local printer to appear as a redirected queue inside the remote session. Microsoft Print to PDF itself does not enable or provide Mac printer redirection.

    The suggestion here is to verify Mac RDP client settings and making sure the Mac client is explicitly configured to pass local printers through to the AWS session. Open the Microsoft Remote Desktop app on your Mac. Right-click your connection profile (or click the Edit pencil icon) and navigate to Devices & Audio (or Devices) and ensure the Printers checkbox is selected. Save the settings, disconnect completely, and log back in. Also, making sure access is enabled for Windows App or Microsoft Remote Desktop under System Settings → Privacy & Security → Local Network .Then fully quit and reopen the app.

    Another point worth mentioning is that the server must be configured to allow client printer redirection and to use the Easy Print driver. On the Server 2022 host, making sure the following two settings Do not allow client printer redirection is set to Disabled or Not Configured and Use Remote Desktop Easy Print printer driver first is set to Enabled under this path Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Printer Redirection. This is crucial because it allows redirection without needing to install the Mac printer's specific driver on the server. After applying the policy, run gpupdate /force and restart the server to ensure the changes take effect.

    Also, it is worth verifying the status of Print Spooler in state of "start" or restart the service and navigate to Control Panel -> Devices and Printers on the server during an active user session. Check if the Mac's local printers show up as [Printer Name] (redirected X). Please note: If a Mac user is looking for "Microsoft Print to PDF", they should ideally select Save as PDF or print to their Mac's native PDF handler natively from their local Mac preview, which maps through smoothly via Easy Print. If they expect the server's "Microsoft Print to PDF" to generate a file on the AWS server, remember that it saves to the remote server's C: drive, not the local Mac.

    If the Microsoft Print to PDF virtual printer itself is missing from the server's printer list (for creating PDFs locally), you can try to reinstall Microsoft print to PDF by running OptionalFeatures.exe and enable the Microsoft Print to PDF feature, then restart if prompted.

    I hope you have found something useful here. If it helps you get more insight into the issue, it is appreciated to accept the answer. Should you have more questions, feel free to leave a message.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.