Windows 11 Build 2200.282 is available for beta and preview channels

Microsoft has released Windows 11 Build 22000.282 for Windows Insiders in the Beta and Release Preview channels. Today’s update brings a huge list of fixes, fixing several issues and bugs in the latest desktop operating system.

Release Notes for Windows 11 Build 2200.282

• We fixed an L3 caching issue that could affect the performance of some apps on devices with AMD Ryzen processors after upgrading to Windows 11 (original version).
• We fixed an issue for a small number of users that prevented the Start menu from working and prevented you from seeing the updated taskbar design after upgrading to Windows 11 (original version).
• We fixed a race condition that occurred at the start of startup that could cause a Stop error.
• We fixed a regression that could cause a stop error 0x38 on some machine configurations that use non-ASCII text in the registry.
• We fixed an issue with the interrupt handling of some processors that could prevent devices from responding.
• We fixed an issue that caused PowerShell to create an infinite number of child directories. This issue occurs when you are using PowerShell Move-element command to move a directory to one of its children. As a result, the volume fills up and the system stops responding.
• We fixed an issue that caused the Server Manager app to disappear after using it to remove Hyper-V functionality. This problem occurs when you install Server Manager on Windows 11 (original version) clients by using Remote Server Administration Tools (RSAT).
• We fixed a thread issue that could cause the Windows Remote Management (WinRM) service to stop when under heavy load.
• We fixed an issue that prevented the Windows Management Instrumentation (WMI) provider host process from working. This occurs because of an unhandled access violation that occurs when using Desired State Configuration (DSC).
• We fixed an issue that prevented a device from responding when you forcibly shut it down during a Group Policy update.
• We fixed an issue that caused files to fail to migrate between Distributed File System (DFS) paths stored on different volumes. This issue occurs when you implement the migration by using PowerShell scripts that use the Move-element order.
• We fixed an issue that prevented you from writing to a WMI repository after a low memory condition.
• We fixed an issue with a hard-coded font in the PowerShell shortcut file that distorts fonts for Japanese, Chinese, and Korean languages. This update fixed this issue for all newly created users on the machine. Existing users can use the C: Users Default AppData Roaming Microsoft Windows Start Menu Programs Windows PowerShell Windows PowerShell.lnk file to open PowerShell to resolve the issue. Existing users can also create a shortcut to this file on the desktop and use the shortcut to open PowerShell.
• We fixed an issue with parsing time formats in events when milliseconds are excluded.
• We fixed an issue that incorrectly rendered some Enhanced Metafile Format (EMF) files. This problem occurs if you create the EMF files using third-party applications with ExtCreatePen () and ExtCreateFontIndirect ().
• We have provided administrators with the ability to reset the zoom to default for HTML dialog boxes in Microsoft Edge Internet Explorer mode.
• We fixed an issue with the Enterprise Mode Site List redirecting from Internet Explorer 11 to Microsoft Edge. Under certain circumstances, the redirect opens a site in multiple tabs in Microsoft Edge.
• We fixed an issue that prevented Internet Explorer from working when you type certain characters in the Input Method Editor (IME).
• We fixed an issue with PropertyGet in JScript9.dll.
• We fixed a memory leak that occurs when using nested classes in VBScript.
• We fixed an issue that failed to keep NumLock state after a quick restart.
• We fixed an issue with some app windows moving. Moving these application windows can be unusually slow if a File Explorer window is visible on the screen.
• We fixed an issue that intermittently prevented the Mail app from accepting keyboard input in the Address and Subject boxes.
• We fixed an issue with the UI to rename files using Folder View in File Explorer. The UI fails to properly handle inline composition using the new Japanese IME.
• We fixed an issue where using App-V would intermittently cause black screens to appear when logging into the credentials page.
• We fixed an issue with an Internet print server that failed to properly package changed printer properties before sending the package to the client.
• We have implemented a Group Policy setting for the following registry value (for more information, see article KB5005010):

1. Registry location: HKLM Software Policies Microsoft Windows NT Printers PointAndPrint
2. Value name: RestrictDriverInstallationToAdministrators
3. Value data: 1

• We fixed an issue that could cause Xbox Game Bar recording features to be unavailable.
• We fixed an issue that could cause distortion in audio captured by voice assistants.
• We fixed an issue that caused a memory leak in lsass.exe when the pTokenPrivileges buffer is not released.
• We fixed an issue that could cause Kerberos.dll to stop working within the Local Security Authority Subsystem (LSASS) service. This occurs when LSASS is processing concurrent User-to-User (U2U) User-to-User (S4U) service requests for the same client user.
• We fixed an issue with a non-paged pool (NPP) leak from the UxSF pool tag. This leak occurs when lsass.exe Stops processing of asynchronous Security Support Provider Interface (SSPI) calls.
• We fixed an issue that prevented you from enabling BitLocker on a thin-provisioned virtual machine (VM). The error is “A device connected to the system is not working” and the system logs, “STATUS_UNSUCCESSFUL”.
• We have improved the performance of MsSense.exe in environments with User Datagram Protocol (UDP) applications that require high amounts of bandwidth.
• We fixed an issue in Windows Defender Exploit Protection that prevented some Microsoft Office apps from working on machines with certain processors.
• We have enabled credentials for Azure Active Directory (Azure AD) Active Directory Federation Services (ADFS) users in Quick Assist.
• We fixed an issue that sometimes prevented Quick Assist users from using full screen view after starting a Remote Assistance session.
• We fixed an issue where Set-RDSessionCollectionConfiguration did not set the camerastoredirect: s: value custom property.
• We fixed an instability of the IME mode in the RemoteApp scenario. You must install this update on the Remote Desktop server and the Remote Desktop client.
• We fixed an issue that caused the IME toolbar to display even when RemoteApp was closed.
• We fixed a registry key paged pool memory leak for Virtual Desktop ID that occurs in explorer.exe.
• We’ve made small adjustments to the colors of the contrast theme, such as making the hyperlinks more distinct when you hover over them while using the desert theme.
• We fixed an issue that prevented Narrator and other screen readers from announcing that the Start menu is open in some cases.
• We fixed an issue that occurs if the search index is corrupted in certain ways; attempts to search using the taskbar or file explorer fail.
• We fixed an issue that prevented the search window from appearing on a secondary monitor.
• We fixed an issue that could cause the File Explorer window to lose focus when mapping a network drive.
• We fixed an issue that sometimes caused the lock screen to appear black if you set up a slideshow.
• We fixed a reliability issue with LogonUI.exe, which affects the rendering of network status text on the credentials screen.
• We fixed an issue that prevented you from opening multiple instances of an app using Shift and clicking the app icon on the taskbar.
• We’ve updated the visual design and animations of the Chat icon in the taskbar.
• We’ve removed the warning about losing other people’s unsaved work when shutting down or restarting if no other user is logged in.
• We fixed an issue that could occur when configuring the “Delete user profiles older than a specified number of days on system restart” policy. If a user has been logged in for longer than the length of time specified in the policy, the device may unexpectedly delete profiles on startup.
• We fixed an issue that failed to establish a connection to the Remote Desktop Protocol (RDP) service or immediately drop an RDP connection under certain circumstances.
• We fixed an issue that could cause input delays for some Bluetooth mice and keyboards.
• We fixed an issue that prevented the Start menu from opening after upgrading the video driver.
• We have improved the precision of downtime estimates when the estimates are at least two minutes or more.
• We fixed a local Security Authority Subsystem Service (LSASS) domain controller memory leak reported in Privileged Access Management (PAM) deployments.
• We fixed an issue that occurs when the Lightweight Directory Access Protocol (LDAP) bind cache is full and the LDAP client library receives a referral.
• We fixed an issue in Adamsync.exe that affects the synchronization of large Active Directory subtrees.
• We fixed an issue that caused a crash when offline files are enabled. Therefore, CscEnpDereferenceEntryInternal holds parent and child locks.
• We added the ability to configure a period or period (.) Delimited IP address We have fixed interchangeably with fully qualified hostnames in the following Group Policy settings:

For more details, visit the official blog.

Windows 11 PRO keys have started selling, get them for the cheapest price of $ 19.46