Skip to main content

Windows 11 22H2 unable to connect to some Windows 10 via RDP

Windows 11 22H2 unable to connect to some Windows 10 via RDP

I have one machine that got pushed an upgrade from Windows 10 to Windows 11 22H2. Before the upgrade remote desktop was working to all of my Windows machines. 

After the upgrade to Windows 11 22H2 RDP only works for certain machines. It was working for domain joined machines and machines that were using default local/domain policies related to RDP. 

Below was the error message I am getting from RDP client (Microsoft Windows 11 Version 22H2 [Version 10.0.22621.1344])

[Window Title]
Remote Desktop Connection

[Content]
An internal error has occurred.

[^] Hide details  [OK]

[Expanded Information]
Error code: 0x4
Extended error code: 0x0
Timestamp (UTC): 03/04/23 04:00:05 AM

Press Ctrl+C to copy.
 

As a workaround, on the target machine (RDP server), change the following policy using gpedit.msc.

Local Computer Policy | Computer Configuration | Administrative Templates | Windows Components | Remote Desktop Services | Remote Desktop Session Host | Security

Require use of specific security layer for remote (RDP) connections = Enabled
Security Layer = RDP

//end

Comments

Popular posts from this blog

Error! Could not locate dkms.conf file install VirtualBox 4.1.8 on Ubuntu 11.10

Tried to update my Ubuntu host today and it did pickup that new version of VirtualBox is available (4.1.8). All other packages installed properly except that VirtualBox installation was complaining about missing dkms.conf file, see error message below. $: sudo /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel modules [ OK ] * Uninstalling old VirtualBox DKMS kernel modules Error! Could not locate dkms.conf file. File: does not exist. [ OK ] * Trying to register the VirtualBox kernel modules using DKMS [ OK ] * Starting VirtualBox kernel modules [ OK ] Though it looks like installation was fine but I am concerned about its effects to VirtualBox functionality. To fix this, do: $: cd /var/lib/dkms/vboxhost $: sudo rm -r 4.1.4 $: sudo /etc/init.d/vboxdrv setup Of course you have to re

The following add-ins could not be started MonoDevelop.GnomePlatform

Installing MonoDevelop in OpenSUSE 12.2 from its repository was very easy. When running it for the first time though I got the message: The following add-ins could not be started: The root of the trace shows MonoDevelop.GnomePlatform,2.8 A quick search shows that MonoDevelop depends on libgnomeui . This should have been part of dependencies when installing the application but well.... Below is the screen shot of the error message. References: http://software.1713.n2.nabble.com/MonoDevelop-and-openSUSE-12-1-td7462957.html [2013/04/09] - Same issue observed in OpenSUSE 12.3 and also the same fix. [2014/11/02] - Same issue observed in OpenSUSE 13.3, mondevelop 3.0.6 and the same fix.