Windows 10 Pro 1709  Build 16299.19 Remote Desktop not working

botisys
botisys used Ask the Experts™
on
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?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Commented:
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)
Most Valuable Expert 2012
Expert of the Year 2018

Commented:
I have it working.  Go into Remote Desktop and turn OFF Printers and Clipboard in Local resources tab. Works fine.

Author

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.
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

JohnBusiness Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018

Commented:
I am connecting via VPN to machines at a client. RDP would not work at all until removing printers and then it connected

Author

Commented:
Using a VPN would not help.  It even fails inside the network -- PC to PC.  All the Resources are unchecked.
JohnBusiness Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018

Commented:
I do not have any issues inside a client network. If no VPN why are using a gateway?

Author

Commented:
I've tested from inside and outside the network -- no difference.  I'm working offsite right now.
JohnBusiness Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018

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.

Author

Commented:
These computers have been on 1709 for at least a couple of weeks.  RDT stopped working today.
JohnBusiness Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018

Commented:
Take one problem computer and do a repair install

Go to the Media Creation Link

https://www.microsoft.com/en-us/software-download/windows10

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.
Distinguished Expert 2018

Commented:
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?
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)
Distinguished Expert 2018

Commented:
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.

Author

Commented:
It worked.
Josh RNetwork Administrator

Commented:
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.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial