Have you tried uninstalling reinstall the Sage 500 client, plus any Sage 500 product updates and/or client side customizations ?

-Tony

No I didn't.  Discovered that Windows 2016 changed the registry key where the default printers are stored.  Had to build a startup PS script to copy the default printer from the new registry location to the old registry location that Sage is still using.  The PS script below worked around the problem.

"$key = 'HKCU:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\SessionDefaultDevices'
$keyproperty = Get-ChildItem -path $key | Select-Object Name
$keyenv = $keyproperty.Name
Copy-ItemProperty -path Registry::$keyenv -destination 'HKCU:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\' -Name Device"

No I didn't.  Discovered that Windows 2016 changed the registry key where the default printers are stored.  Had to build a startup PS script to copy the default printer from the new registry location to the old registry location that Sage is still using.  The PS script below worked around the problem.

"$key = 'HKCU:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\SessionDefaultDevices'
$keyproperty = Get-ChildItem -path $key | Select-Object Name
$keyenv = $keyproperty.Name
Copy-ItemProperty -path Registry::$keyenv -destination 'HKCU:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\' -Name Device"

Would this work for the issue with using a default redirected printer and Sage 500 not detecting it?

If you have the same version of Windows, I imagine you would have the same issue with redirected printers, yes.

Windows 2016 creates printers and redirected printers in the same 'new' registry folder location, and Sage is still looking in the 'old' registry folder location.

Kevin, This seems to be missing a piece of code. I tired to run it and it didn't give any errors but it did not put the Default printer into the old location. It looks like under \SessionsDefaultDevices there is a child folder with SID ID and then the Device is there. Does the code copy that string to the old path?

The script should get the device(s) from the SID ID sub folder and copy them directly into the Windows folder (without a sub folder).  You will need to run the script with admin access.

I figured out the issue. Forgot to remove the Quotes! (ouch)