Share via

Windows 10 Professional remote desktop error 0x4

Anonymous
2018-07-11T13:29:14+00:00

Hello,

I have been connecting to a computer at another location (Windows 10 Professional) using my Mac for quite some time now. Suddenly, last week the remote desktop program gave an error code "0x4". I tried connecting with the previous version of the RDP client to no avail. I also tried connecting with iPhone and another Windows 10 Professional – nothing seems to work.

The connection is over the public internet and I do know the correct IP for the device. No changes have been made to the network structure (e.g. port settings, or such). The environment in which the target computer resides is exactly the same as before.

How could I fix the problem? I'd like to note it is extremely hard for me to access this computer physically, so if it is possible by any means to fix this remotely I'd love to give it a try. I have not allowed other connection than RDP to the computer so I cannot SSH or use other measures to change the target computer.

Windows for business | Windows Server | User experience | Remote desktop clients

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

19 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-09-13T14:37:14+00:00

    I was running into this same problem for the past week with Microsoft Remote Desktop Version 10.2.1 (1143) for Mac, and I may have just solved it. This does not help if you are stuck already and do not have access at all, but once you do have access, configuring this should prevent the problem in the future. The solution I used is to enable keepalives for remote desktop connections:

    1. If you can manage the remote machine through group policy, follow the instructions posted here:

    http://jbcomp.com/keeping-remote-desktop-connections-alive/

    Otherwise keep reading.

    1. Open the registry editor (just search for it-- win-S, "regedit").
    2. In the tree view, navigate to HKEY_Local_Machine -> SOFTWARE -> Policies -> Microsoft -> Windows NT -> Terminal Services
    3. In the pane on the right-- right-click, New -> DWORD (32-bit) Value
    4. Name it "KeepAliveEnable", then double click it and enter a value of 1
    5. Repeat steps 4 and 5 with the name "KeepAliveInterval"
    6. Close the registry editor.
    7. To be sure the setting will be used, reboot the machine, or restart Remote Desktop Services from the Services management console (Win-S, "Services"). 

    That's it. So far this has prevented the issues I was having multiple times a day with receiving the 0x4 error on attempting an RDP connection. As usual with Microsoft products, YMMV.

    10 people found this answer helpful.
    0 comments
  2. Anonymous
    2018-08-25T19:59:54+00:00

    I have the same problem when I'm connecting with Version 10.2.1

    When I use the old version 8.0.44 I'm able to connect

    4 people found this answer helpful.
    0 comments
  3. Anonymous
    2018-07-11T19:42:22+00:00

    The only thing i can suggest at this point is to either reset that PC or use something like teamviewer.

    Because you are stating nothing has changed so very hard to determine what is going on really. Sorry can't be more help.

    4 people found this answer helpful.
    0 comments
  4. Anonymous
    2018-07-16T20:34:51+00:00

    I have exactly the same problem. It worked until a few days ago.

    3 people found this answer helpful.
    0 comments
  5. Anonymous
    2018-07-11T13:41:02+00:00

    Thanks for your reply.

    We have disabled any updates from downloading/attempting to restart the computer so those should have not had any effect to the device.

    We have also disabled remote Powershell, so it is not possible to connect via Powershell.

    According to our logs (posted to an internal server by a program that monitors the power state of the computer), the computer has been online for several months (so no restart).

    3 people found this answer helpful.
    0 comments