
Microsoft released WindUpdate only last month, but the OS already suffers from various bugs.

There is no workaround for this issue as the cause of the failure is currently unknown. Provisioning packages which are applied during initial setup are most likely to be impacted by this issue. PPKG files which are used to help configure new devices for use on business or school networks.

Windows might only be partially configured, and the Out Of Box Experience might not finish or might restart unexpectedly. Using provisioning packages on Windows 11, version 22H2 (also called WindUpdate) might not work as expected. The broken provisioning is mentioned on the mentioned on the Health Status page for Windows 11. Microsoft is aware about these issues and is working on a fix. There, create a new 32-bit DWORD named fClientDisableUDP and set it to 1. As Bleeping Computer suggest, by disabling UDP for Remote Desktop you can get things back to normal.įor that, open the Registry and navigate to the HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client key.

The issue appears to be related to a bug with UDP.
