To improve Windows Server I suggest you ...

Issue on Windows10 Pro as RDP listener - internal error occurred

Hello,

I want to report one issue that is easy to reproduce, it occurs with any rdp client that connects to Windows10 Pro with enabled RDP connections, actually used mstsc.exe to connect from one Windows10 pro machine to another Windows10 pro machine with enabled RDP.

After ~100 tries to restore interrupted connection the server refuses future rdp connection tries with internal error occurred message reported by mstsc.exe.

It doesn't matter if you have logged off the session during running, as example did 20 connection restorings then logged off, logged in and did next 80 connection restorings, that was only example, only what matters is that you have only to restore any interrupted session at least ~100 times to send server to nirvana. As example after WiFi lost connection or during any network problem that requires rdp connection restoring. Only what helps to restore functionality is to restart remote desktop service in services.msc

I highly assume by restoring connection with reconnection cookie the bug counter counts up and by reaching 100 (the counter seems to be not reset by any action) so finally it completely stops to accept any future connections with internal error occurred message.

Such error doesn't exist on Windows2016 but Windows10 pro is affected.

More over few months ago this bug didn't exist on Windows10 too.

Please forward this issue to your RDP server developers, thank you!

Sincerely yours.

3 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Wegenall shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base