Default printer registry key not set correctly on Windows Server 2016/2019 ("HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows\Device") RRS feed

  • General discussion

  • While running some older legacy applications on Windows Server 2016, Windows Server 2019 and all builds of Windows 10 we have encountered the following issues as it relates to printing:

    1. The redirected default RDP printer fails to update the "HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows\Device" registry key while using session printers (such as Easy Print feature in RDP remote sessions or the Citrix Universal Print Driver) in Windows Server 2016/2019 or redirected printers in Windows 10. Prior version of Windows did not have this issue and the registry key is updated correctly.

    2. If you change the default printer using the standard Print dialogbox as found in Wordpad (File, Print, then right-click on the printer and select Set as Default) in Windows Server 2016/2019 or any build of Windows 10, the newly set default printer won’t be marked as the default one unless you press F5 to refresh the list of printers. Prior versions of Windows did not have this issue and the default printer was updated immediately in the standard Print dialogbox.

    We have confirmed that issues are bugs and need to be corrected in all builds of Windows 10 and Server 2016/2019.
    Friday, December 21, 2018 10:28 PM

All replies

  • Have Microsoft acknowledged this as a bug?

    I've used a script in the past to assist our users with this issue. It's a bit rough and ready but just incase it helps.

    $a = Get-ItemProperty "HKCU:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\SessionDefaultDevices\*\"
    if ($a.Device) {
    Set-ItemProperty -path "HKCU:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows" -name Device -Value $a.Device
    write-output "Legacy Default Printer set to $($a.Device)"
    write-output "Default Printer is not Redirected"

    Tuesday, February 12, 2019 6:17 PM
  • I have come across this bug and it still seems to persist in a fully-patched Windows Server 2019 RD Session Host.  Did you ever identify a fix, or follow-up with Microsoft and open a bug report?
    Thursday, October 29, 2020 7:27 PM