Windows 10 Pro 1709 Build 16299.19 Remote Desktop not working

Starting today, I can no longer remote into a couple of PCs at the office.  They are both using the latest build of Win 10.  PCs on the same network, not yet upgraded to 1709, work fine. Remote Desktop Connection does not work on or off the network with or without a RD Gateway.  The problem appears only on 1709 version.  
Is there a fix for this?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

William MillerIT SpecialistCommented:
This is a "known issue" it seems. At least, known to the people trying to use RDP with version 1709 of Windows 10. Some possible fixes have included:

- Disabling printer redirection in RDP
- Rolling back to 1703
- Installing "Remote Desktop" from the Windows App Store (Note that TSPrint has been listed to not work with this software)
JohnBusiness Consultant (Owner)Commented:
I have it working.  Go into Remote Desktop and turn OFF Printers and Clipboard in Local resources tab. Works fine.
botisysAuthor Commented:
I unchecked all the local resources and tried to connect using the RD Gateway.  Still won't connect.  
Rolling back to 1703 is not an option.  Old version has already been cleaned up.
I downloaded Remote Desktop from the Microsoft Store -- no change.
Get Blueprints for Increased Customer Retention

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

JohnBusiness Consultant (Owner)Commented:
I am connecting via VPN to machines at a client. RDP would not work at all until removing printers and then it connected
botisysAuthor Commented:
Using a VPN would not help.  It even fails inside the network -- PC to PC.  All the Resources are unchecked.
JohnBusiness Consultant (Owner)Commented:
I do not have any issues inside a client network. If no VPN why are using a gateway?
botisysAuthor Commented:
I've tested from inside and outside the network -- no difference.  I'm working offsite right now.
JohnBusiness Consultant (Owner)Commented:
Check other things possibly wrong in your system and try a different V1709 computer. I tried on two and my colleague uses his V1709 system to talk to other computers.
botisysAuthor Commented:
These computers have been on 1709 for at least a couple of weeks.  RDT stopped working today.
JohnBusiness Consultant (Owner)Commented:
Take one problem computer and do a repair install

Go to the Media Creation Link

Windows 10 is running, so click on the Download button (not Upgrade Button, select Open (Run) but NOT Save. Allow the program to run. Allow drivers to update. Then select Keep Everything.

You can also Keep Data, or Keep Nothing. Keep Nothing is very close to a clean install.
Since it works without issues or modifications here, it will be probably some incompatibility with software that you use. You need to do some tests:

1 install 2 clean 1709 VMs and let them access one another via RDP - it will work.
2 join those same two to your domain - does it still work afterwards?
3 if yes, install your key software including security software - does it still work?
botisysAuthor Commented:
I found the solution else where.
The solution that worked was to go to Windows Defender Firewall with Advanced Security and enable the 3 newer Remote Desktop firewall rules:
Remote Desktop - Shadow (TCP - In)
Remote Desktop - User Mode (TCP - In)
Remote Desktop - User Mode (UDP - In)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
You should wait with closing. These rules are not needed for standard remote desktop. They are disabled here and still, it works. Please investigate to find out what is wrong at your place. The standard rule "remote desktop", which opens up port 3389 would be perfectly enough.
botisysAuthor Commented:
It worked.
Josh RNetwork AdministratorCommented:
I was having a similar issue. My issue was after the update, I was using a remote port besides 3389. Even though the registry was correct with my new port, it didn't propagate to the Windows Firewall for some reason. I created a new rule in Windows Firewall with my correct RDP port and it worked.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Remote Access

From novice to tech pro — start learning today.