Issues with Remote Desktop on Windows 11 after Update 22H2

Thanks Randall for the registry export solution.

But I still have to remotely restart the computer.

So far, I'm not able to remotely restart it.

If I RDP to one of my local network pc (Win10 Pro) and I try a "shutdown /m \IP_ADDRESS /r /f" from within an elevated prompt, I get an "access denied".

The pc I want to restart is not joined and only have one local user.

In the previous instance of this problem, I remember coming across an error message stating something to the effect that the local user had been used to many times. I didn't copy the actual error message because I had someone on site able to perform a physical hard reboot. After the reboot, the pc seemed to be back in working condition until a few days ago.

Is it possible that the problem we're facing is more a question of how many times we open/close a RDP session? As if the RDP sessions we close remain open in the background thus preventing new ones to be opened?

One way would be to create the fix on a different computer, then use the export function in the registry editor to export just that key, then get the export to the user if they have local admin rights they can just import the the fix then restart. That way they dont have to go into the registry.

I have a number of users having this issue where we use published apps that was my quick fix. Today i am going to look at using group policy to push the registry fix out as this has been going on for a while now.

Hope that helps make it easier.

I would like to execute the fix, but I can't RDP to the troubled pc from my remote location or from within the local network (via RDP on another local pc).

I would like to force a restart on the troubled pc, but since I don't have physical access to that troubled pc, I have to find a way to do it via a RDP session. So far, all my attempts from another local pc (via RDP) give me an "access denied".

Does anyone know how to solve this issue.

Thanks

Hi

We tried this solution and it worked but only temporarily.

We found that any further attempts to connect to our servers via Remote Desktop only worked if we rebooted the laptop. Had to do this each time the Remote sessions were closed. The fix also had a knock on effect that prevented Outlook from syncing and returned server connection issues (local version of Outlook using Gmail as host). Deleting the fix got us back up and running with email but put us back where we started.

Any ideas on why the fix only worked 'once' before having to reboot and how to prevent the knock on effect to Outlook?

Thanks

Jerry, you have to create it or run the command (as admin):
REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client" /v fClientDisableUDP /t REG_DWORD /d 1 /f