Windows Remote Desktop disconnects frequently or automatically

As the name suggests, the Remote Desktop feature in Windows, helps us to access another computer from our computer remotely. This feature plays an important role to solve issues on our system, in case any support representative wants to access our computer remotely and fix it. Today, while using this feature, I noticed that I could connect to other computers from mine, but then the Remote Desktop connection cut off automatically. So, I tried to connect to another computer of mine, and found the same result.

Remote Desktop disconnects frequently

First of all, I ensured that Windows Firewall was switched off to ensure that the Firewall was not the culprit. It did not help. I’ve read somewhere that WiFi printers could also cause the issue while using the Remote Desktop feature, so I disconnected them too but that too did not solve the problem. I came around the following solution and it worked:

Remote Desktop disconnects frequently

1. Press Windows Key + R; type sysdm.cpl and hit Enter. Switch to Remotetab. Make sure you have selected the options highlighted in the below image:

Remote Desktop Disconnects

2. Moving on, press Windows Key + R combination, type put Regedt32.exe in Run dialog box and hit Enter to open the Registry Editor.

REGEDIT Fix: Blurry Fonts or Poor Display Scaling In Office 2013 Programs

2. Navigate to the following location:



3. In the right pane of this location, look for the registry string (REG_SZ) named ObjectName, if you’re really facing the issue, then this string must have Value data as LocalSystem. Double click on the same string to modify its Value data:


4. In the above shown box, input the Value data as NT Authority\NetworkService. Click OK then and close the Registry Editor and reboot the machine to get the issue fixed.

Hope the fix helps you.

Posted by on , in Category Windows with Tags
An Electrical Engineer by profession, Kapil is a Microsoft MVP and a Microsoft Content Creator. Please read the entire post & the comments first & create a system restore point before making any changes to your system.


  1. Eric Leone

    Step 3 and 4 contradict each other. I presume you mean LocalSystem in step 4 since it is already NT AuthorityNetworkService by default.
    so it should say:
    “In the above shown box, input the Value data as LocalSystem. Click OK then and close the Registry Editor and reboot the machine to get the issue fixed.”

  2. ^^ Not that 🙂 Actually the machine on which you’ve issue have LocalSystem by default. The image we’ve shown here is snapped on a fresh (non-issued) machine.

  3. maxxxem

    If you want to control your Pc remotely try (windows 8 controller) for your smart phone @ play store …You will love it ! works great on windows 8.1 pro

  4. ^^ Thanks for suggestion, might helpful to others 🙂

  5. massiveloop

    Something I wanted to bring up is that Win8 rdp will not function properly if there is not a valid key present. I used a generic RTM license key to get 8.1 Pro updated on my machine (through the “get more features” optin in SysProperties) then when I went to enter what I though was a valid key it wasn’t, however when you update using the RTM key you cannot easily move back and while you can still use the system (with reduced customization and a reminder to activate windows) it seems to not allow outbound rdp sessions to live more than a couple minutes at most. Now that I have purchased and applied a valid w8 key, my RDP dropping has disappeared.

  6. Naseeb Jamal Morad

    you helped me thanks!

  7. Mike

    The default on my machine is NT AuthorityNetworkService not LocalSystem.

  8. Juliet Bell

    The above steps seems to be complicated. Instead, I would recommend using remote desktop tools such as logmein, gosupportnow, gotomypc, R-HUB remote support servers etc. They are easy to use.

Leave a Reply

Your email address will not be published. Required fields are marked *

2 + 1 =