RDP Stopped after Update, Must Reboot Server REPEATEDLY

Question

On April 15th, KB5001347 & KB5001402 were installed on my remote hosted Server 2016

Now, about 90% of the time, when I try to connect I get "Internal Error Has Occurred" on my Windows 10 pro desktop.

But I CAN connect to other servers (mostly 2012 R2s) on other hosting platforms. Specifically ones that did NOT have this patch installed to break the server.

This was NOT happening before the patches were applied.

I can go to the hosting service control , and FORCEBLY reboot the server. Then it works... for about 15 minutes. Then mostly fails again...

It falls back to allowing successful connections about 10% of the time or less.

What did you break??!!

Answer 1

The hosting service gave me a solution... Not anyone from Microsoft.

Apparently, there were many DoS attacks and login attempts going on.
The solution is to change the IP address of RDP server, and of course the client you are using.

https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/change-listening-port

The best I can guess is that overloading the RDP connection in a DoS attack wasn't working before, so MS decided to patch it so that hackers COULD successfully achieve DoS attacks. Because it didn't cause problem before the patch.

I can think of no other reason MS would change it this way, unless it was outright incompetence and lack of testing.

Answer 2

I have the exact same problem and I have been working through the entire https://appuals.com/fix-remote-desktop-connection-internal-error-has-occurred/ without any success. I worked through the entire internet, because with Mac os RDP client, I get error "0x4": ". Yay.

I suspect it is some kind of SSL certificate error but after 5 hours, I just kind of give up. It definetly came after update KB5001402 for me! I did NOT have had KB5001347 installed when this first appeared.

For me, Remote Desktop / RDP stopped working completely, with Mac OS Microsoft Remote Desktop App I get said error "0x4", and with windows remote desktop trying it from a Windows PC I get the exact same error like @ScottWeber-1142: "an internal error occurred".

The only thing I can try tomorrow is a complete reinstallation and hope for the best.

Answer 3

Hello @ScottWeber-1142 & @Kopp, Nikolas (external) ,

This may be an error due to OS update. Please also check the following links for troubleshooting.
https://learn.microsoft.com/en-us/answers/questions/300054/remote-desktop-connection-an-internal-error-has-oc.html
https://social.technet.microsoft.com/Forums/en-US/be97b9c5-d439-4e15-b1a0-4b8b2500073d/mac-os-your-session-ended-because-of-an-error-if-this-keeps-happening-contact-your-network?forum=winRDc

Best regards,
Leila

----------

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 4

Hi @Leila Kong ,

yes, this definitely due to update KB5001402. Sadly, I already worked through the exact same links you just provided yesterday, without any success. I tried every single suggestion, including setting MaxOutStandingConnections to 10,000 and all the other tips, but none worked so far. Basically I somehow need to revert update KB5001402, but I suppose it's just not possible without reinstallation.

Thank you,
Nicolas

Answer 5

Hello @CSW2541 & KoppNikolasexternal-7238 ,

Thanks for your sharing.