This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 90%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
After installing the latest updates on my Windows 11 business notebook I am unable to connect mit my business server. Only hours ago I could establish my VPN connection via ShrewSoft VPN client and then use Microsoft's "Remote Desktop Client" to access my server. Now I can establish the VPN connection as usual but "Remote Desktop Client" instantly says "error 0x4, extended error: 0x0" (not very helpful indeed). No settings changed in any way. No other software has been added. I tried to reboot, restart services, add items to the registry as some suggested - nothing helped. It' ridiculous!
On my Macbook I can access the server as usual (using the internal macOS VPN functionality and the macOS version of "Remote Desktop") so I'm quite sure it's not a problem on the server side or a problem related to the server's internet access.
How can I fix this?
Hi @Mountain
Check this page for setting the registry values, this could be after Windows 1122h2 update I guess? windows-11-22h2-rdp-disconnects-and.html
Hope this helps.
==
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
@JimmySalian-2011 : thanks for your reply. Indeed it started with the Windows 1122h2 update. I followed the link and added another entry into the registry + reboot but nothing changed. There is still an error code 0x4 / extended error 0x0 poping up instantaneously.
Can you upload system and app event logs to onedrive so I can check. Thanks.
Where do I find the logs you need?
Hi,
This is a security change in 22H2 that is securing your server from possible attack. I suggest that you check to make sure that the RDP port 3389 is protected. You should only allow connections from trusted IP addresses into the RDP server. This can be implemented by your server administrator, or may have already been. Hence the issue you're having accessing the server.
----------------------------------------------------------------------------------------------------------------------------------------------
--If the reply is helpful, please Upvote and Accept as answer--