Local RDP broken after April Update (1803)

Hi,

Not sure if this is the right topic area, but as part of my dev work I frequently need to switch local user sessions. "Fast User Switching" isn't particularly fast, so I just RDP into another local user session on my Windows 10 Home machine. That worked a treat and allowed me to quickly alt-tab between desktops. Now after the April Update, it no longer works.

I've seen reports of other RDP-related problems with this update, but I would appreciate any pointers on how to get this functionality back, as it's a big time saver.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

I'm Greg, an installation specialist and 8 year Windows MVP, here to help you.

One initial thought is you could use TeamViewer just works, doesn't break and is free for personal use. I wouldn't a waste a minute with RDP or any other built-in features that fail as often as they work.

If this was caused by April Version 1803 update can roll back Version 1803 in Settings>Update & Security>Recovery and then hide it until it matures using the Hide Updates Tool downloaded from here: http://download.microsoft.com/download/f/2/2/f2...

Otherwise go over this checklist to make sure the install is set up correctly, optimized for best performance, and any needed repairs get done: http://answers.microsoft.com/en-us/windows/wiki...

Start with Step 4 to turn off Startup freeloaders which can conflict and cause issues, then Step 7 to check for infection the most thorough way, then step 10 to check for damaged System Files. Then continue with the other steps to go over your install most thoroughly.

Update your drivers from the PC's Support Downloads web page, using the full model number, Serial Number or Dell Service Tag on sticker. Compare the latest drivers available for download with the ones presently installed in Device Manager reached by right clicking the Start Menu. Make sure you have the latest BIOS or UEFI firmware, Chipset, Display (Video), Sound, USB3, Bluetooth, Network and all other drivers, or else download and install the latest now.

If nothing else helps then run a Repair Install by installing the Media Creation Tool and choosing from it to Upgrade Now. This solves many problems and will also bring it up to the latest version which you need anyway and by the most stable method. http://windows.microsoft.com/en-us/windows-10/m...

But remember that Factory or Upgrade installs are inferior installs which most enthusiasts won't even run because they'd expect endless issues. Consider now or later doing the Clean Install in this link which compiles the best possible install that will stay that way as long as you stick with the tools and methods given: http://answers.microsoft.com/en-us/windows/wiki...

There is also an automated Refresh that reinstalls WIndows while shedding corrupting factory bloatware, saves your files, but doesn't clear the drive to get it cleanest: https://www.howtogeek.com/265054/how-to-easily-...

I hope this helps. Feel free to ask back any questions and let us know how it goes. I will keep working with you until it's resolved.

________________________________________________________
Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.
----------------------------------
I am a volunteer and not Microsoft.

Over 100,000 helped in forums for 10 years. I don't quit for those who are polite and cooperative.

Windows MVP 2010-20

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Wow, thanks for the lightning response!

I did actually grab for TeamViewer right away, but unfortunately it doesn't work either. It just shows a black screen and opines that maybe Fast User Switching is to blame for its inability to capture the remote screen.  Based on forum posts on the TeamViewer site, I switched it to Windows authentication, but it rejects my password even though it's correct. I read something somewhere about UPN credential format, so I can give that a try and/or pursue it further on the TeamViewer forum. I might also try Real VNC, AeroAdmin, etc., though cross-session RDP on the local machine seems to be a rare use case.

I didn't know about the update hiding tool, so thanks very much for that link. I don't know how long I would be able to avoid this update, but I will have to go that route unless I can get TeamViewer or a similar tool working. I'll update here when I've done more testing. Thanks again.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Here is a fix that works for many users:
https://superuser.com/questions/1321418/remote-...
Sumit

Windows Insider MVP 2018-current and Moderator
Dell Inspiron 5590 - i5 10210U/12GB DDR4/ 4GB Nvidia MX230/ 512GB nvme
https://www.yourwindowsguide.com

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

OK, so many hours later -- but still no solution -- I have the following.

When I went in to Settings>Update & Security>Recovery, I did not see a rollback option. That means that it's been more than 10 days since the April Update -- so it wasn't the April Update that caused it, it was cumulative update KB4103721. That ran the night before the problem started. OK, so I uninstalled that, but the problem wasn't fixed. I don't know if the uninstall leaves registry changes it originally made in place, such that it doesn't completely revert the update, or what. I fiddled with various terminal services registry settings, but no matter what I do, I get 

"Remote Desktop can't connect to the remote computer for one of these reasons:

1) Remote access to the server is not enabled

2) The remote computer is turned off

3) The remote computer is not available on the network etc."

I've turned off the firewall, and that didn't help. I've also tried TeamViewer, AnyDesk, RealVNC, and maybe another solution, nothing works right for remoting into another session on the same machine.

Now, of course since this is Windows 10 Home, the Remote page says it's not supported. Yeah, but it was before the update! If I knew for certain that upgrading to pro would do it, I would consider it (despite the insult of having functionality removed and then being expected to pay for it), but I have a Windows 10 Enterprise machine at the office for which RDP doesn't work either -- so I wouldn't bet a nickel let alone $99 that it would work after that.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi, PRiha

My local RDP was broken by the latest updates, but I got it working for connecting between PCs on my home private network.

The first thing I had to fix was to get network discovery working again on the machines (I used technique here: 

https://www.techrepublic.com/article/how-to-resolve-network-problems-caused-by-the-windows-10-april-2018-update/)

But after that, trying my saved RDP file still reports "Remote Desktop can't find the computer". 

I could connect to the remote PC this way:

1 - In File Explorer, expand the Network to show the PCs

2 - Right-click on PC to start a session on

3 - Select "Connect with Remote Desktop Connection"

There was no prompting for credentials, it might only be passing the credentials of the current session, so not sure if this fits what you're trying.

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thanks to all who've replied, even if the solution was not applicable.

I've been a loyal Microsoft dev for just about forever, but I must say this is pretty irritating. The only thing that actually works is using RDPWrapper and/or hacking termsrv.dll with a hex editor. Not the most stable or best long-term solution, but whatever.

Now, I understand that MS probably didn't consider my use case, i.e. that being able to RDP into other sessions on your local machine makes testing session-aware software easier, along with easier admin (though there are definitely a lot of admins). But what is the dreaded use case that they patched here? Disallowing two active users on a machine? Who cares? Who is going to do this without a legitimate need for remoting? What is the fear? Someone is going to buy a single copy of Office and share it with their small business? Give me a break. I don't think people are that desperate, nor do average users even know about RDP. Are a bunch of Linux users going to do this? Of course not. If they are Linux fans, they surely are snobbish about Windows and will not use it (except for game development :) ). Seriously, if they are such devs, they will dual boot, use virtual machines, etc. They will still need their own Windows license to do serious work, so this seems a useless punishment for licensed users.

So I really don't see what is driving this paranoia. Hopefully this will be addressed in the future, but there does not appear to be an easy way short of some hacking.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Priha:  If you have Home edition your done. Only solution is to back out the update that created this, then go into services.msc and find windows updates / properties / and disable it, so it never re-updates. You basically are EOL with that system as Microsoft has decided that RDP on home editions was never really intended and not going to be partially used anymore. People should not reply until after reading a persons problem 3 plus times.  :) It would appear that most replies in this thread, fail to understand your problem. I totally understand it, as I have the same problem. 

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

The best fix would be to wipe out home and update to windows 10 pro. Where you can then go into gpedit.msc and modify a setting to continually RDP as you have in the past. However Microsoft has fubared pro with their latest update and failed to fix half of their problems, I would recommend either waiting for fixes or finding another alternative, Such as loading a full pro edition x64 of Windows 7  :) Where most things still work, but you are then more open to security issues...  One thing I have found that not many have mentioned with the new build that is broken...   NETWORK MAP, everybody is complaining how other systems / printers / shared files are not showing up correctly, and there is a way to correct this in Services.msc, but once they do all show up, the map itself is broken, as you can not RDP to any of those systems on the map anymore (sometimes it works, sometimes it don't) Sometimes it will show the shared files on other systems , sometimes it sits and spins.     Noticed this when working between all systems that are upgraded too 1803. If your using the MAP from any windows 7 system it all still works fine. Anyway hope this helps. Microsoft has obviously bitten off more than they can chew, or trying to move us all in a direction that increases the size of their pocket books. I have said it before and will say it again. They are not concerned about the common population / businesses, they are obviously always going in the direction of money  IE ...xbox / android.  Be interesting to see where this goes. Keep hanging on as we are all on a roller coaster ride to the future.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I had problems with both RDP and network discovery after the April Fools update and what seems to have solved it for me is by starting these services (through services.msc):

Function Discovery Provider Host

Function Discovery Resource Publication

Some brainiac at MS thought that the startup for these should be changed from automatic to manual with the April update. Microsoft needs to stop using recruitment agencies for clowns when they hire developers.

8 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Wait, you're a Microsoft Windows MVP and your first suggestion to a Windows update breaking a MS provided tool with a 15+ years history with updates is to go buy a 3rd party tool that's going to cost me $588 a year ??? WOW ! 

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated August 23, 2020 Views 10,933 Applies to: