
We fixed an issue that causes a device to stop responding when you forcibly shut down the device while a Group Policy is being updated. This occurs because of an unhandled access violation that occurs when using the Desired State Configuration (DSC). We fixed an issue that causes the Windows Management Instrumentation (WMI) provider host process to stop working. We fixed a threading issue that might cause the Windows Remote Management (WinRM) service to stop working when it is under a high load.
This issue occurs when you install Server Manager on Windows 11 (original release) clients using Remote Server Administration Tools (RSAT).
We fixed an issue that causes the Server Manager application to disappear after you use it to remove Hyper-V features. As a result, the volume fills up and the system stops responding. This issue occurs when you use the PowerShell Move-Item command to move a directory to one of its children. We fixed an issue that causes PowerShell to create an infinite number of child directories.
We fixed an issue with the interrupt handling of certain processors that might cause devices to stop responding. We fixed a regression that might cause stop error 0x38 on some machine configurations that use non-ASCII text in the registry. We fixed a race condition that occurs during the early part of startup that might cause a stop error. We fixed an issue for a small number of users that prevents the Start menu from working and prevents you from seeing the updated taskbar design after upgrading to Windows 11 (original release).
We fixed an 元 caching issue that might affect performance in some applications on devices that have AMD Ryzen processors after upgrading to Windows 11 (original release).
This update includes the following improvements: Hello Windows Insiders, today we’re releasing Windows 11 Build 22000.282 to Windows Insiders in the Beta and Release Preview Channels.