Steps to fix printer not showing up in Windows Remote Desktop session

Have you installed a printer on your Microsoft Windows computer, but the printer is not showing up during the Remote Desktop session? There are a few things you need to check when experiencing this problem.

1. Check if the printer is turned on when connected

Make sure you have the Printers option selected in the Remote Desktop settings. You can check this by bringing up the Remote Desktop Connection screen, selecting Local Resources, and making sure the Printers option is selected.

Steps to fix printer not showing up in Windows Remote Desktop session Picture 1

2. Check server settings

If you are connecting to a Windows Server box, make sure the settings on the server do not disable printer sharing. Log in to the server and perform these steps.

Windows Server 2016 & 2019

In these versions of Windows Server, RDP settings are controlled in Group Policy.

Step 1: Launch gpedit.msc.

Step 2: Navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host.

Step 3: Expand Printer Redirection.

Step 4: Make sure that the Do not allow client printer redirection setting is set to Not configured or Disabled. Another setting you might want to check is Redirect only the default client printer. This policy should also be set to Not configured or Disabled, if you want more than just the default printer available for use.

Windows Server 2012

Step 1: Open Server Manager.

Step 2: Select Remote Desktop Services.

Step 3: Select Collections.

Step 4: Select Tasks, then select Edit Properties.

Step 5: In the Client Settings tab, make sure that Windows Printer is enabled.

Windows Server 2008

Step 1: Go to Start > Administrative Tools > Remote Desktop Services > Remote Desktop Session Host Configuration.

Step 2: Select Connections, right-click on the name of the connection, select Properties > Client Settings > Redirection. Make sure that Windows Printer is not selected.

3. Make sure the drivers are installed on the server

Check that the driver for the printer you want to use is installed on the computer you are connecting to. If the driver is not installed on the computer you are connecting to, the printer will not appear at all.

Above are some causes and solutions to fix the error that the printer does not appear in the Remote Desktop session. Hope this information is useful to you!

Micah Soto

Update 31 October 2021

You should read it

May be interested

Steps to Fix the error that cannot be copied and pasted into the Remote Desktop session
some users have particular problems when copying and pasting files from the local computer into a remote desktop session. they can still copy paste locally, but the option to paste will be grayed out on the remote desktop computer.
Steps to fix the error can't drag and drop in Windows 10
you can always move files around by pressing ctrl + x and ctrl + v or browse through folders when you want to attach files to an email, but the simple drag and drop feature is still more convenient.
Steps to fix 'Shell Infrastructure Host Has Stopped Working' error in Windows
is your windows device showing 'shell infrastructure host has stopped working' error? in most cases, this problem occurs when running the application on a windows guest account.
Steps to fix 'Application Has Been Blocked From Accessing Graphics Hardware' error in Windows
it's really annoying when you randomly get the error 'application has been blocked from accessing graphics hardware'. however, troubleshooting is pretty easy.
How to fix error 0x8024001 when updating Windows
error 0x8024001 appears will make windows unable to update (update) and also unable to restart the computer if they do not handle them thoroughly.
Errors related to msvcp140.dll, download msvcp140.dll here
errors related to msvcp140.dll can arise for a few different reasons. for example, a faulty application, msvcp140.dll has been deleted or misplaced, a file has been corrupted by malware present on the pc, or the windows registry has crashed.