Microsoft has just released a new Build 22000.593 (KB5011563) as an optional “C” update for Windows 11 to fix a large number of bugs. Microsoft states: Recovery discs (CDs or DVDs) created by using the Backup and Restore (Windows 7) program in Control Panel may be unable to start.
On devices with Windows Updates released before January 11, 2022, recovery discs created by using the Backup and Restore (Windows 7) application are not affected by this issue and the system will boot as expected.
Join tip3x on Telegram
Moreover, Microsoft also said that no third-party backup or restore applications have been reported to be affected by this problem, and there is no official solution to the above problem, but Microsoft said they are working hard to solve this problem.
In this version, Win11 displays up to three high-priority Toast notification windows at the same time. This feature is primarily intended for applications that use the Windows notifications in the system to send phone calls, reminders, or alarm notifications.
Therefore, up to four notifications may appear simultaneously on the system — three high-priority notifications and one normal-priority notification.
The following is a list of bug fixes given by Microsoft:
- We fixed an issue that turned off the automatic launch of Universal Windows Platform UWP apps after you upgraded the OS.
- We fixed an issue that caused SystemSettings.exe to stop working.
- We fixed an issue affecting searchindexer.exe that prevented Microsoft Outlook’s offline search from returning recent emails.
- We fixed an issue that increased Windows startup time. The problem arose because a UI thread in the networking API stopped responding when the 5G Wireless Wide Area Network (WWAN) device woke up slowly.
- We fixed a memory leak in the wmipicmp.dll module that caused a large number of false alarms in the System Center Operations Manager (SCOM) data center monitoring system.
- We fixed an issue where execution policy settings were incorrectly returned from the registry.
- We fixed an issue where modern browsers would not render HTML generated by gpresult /h correctly.
- We fixed an issue that resulted in an “Access Denied” exception for a file when PowerShell testing AppLocker.
- We fixed an issue that caused the Remote Desktop Services (RDS) server to become unstable when the number of logged-in users exceeded 100. This prevents you from accessing published applications using RDS on Windows Server 2019.
- We fixed an issue where an error message was returned when you browsed a domain or organizational unit (OU). This problem occurs due to improper memory zeroing.
- We fixed an issue that caused the Group Policy Management Console to stop working after you closed it. The system logs Application Error Event ID 1000 and Error, 0xc0000005 (STATUS_ACCESS_VIOLATION); the failing module is GPOAdmin.dll.
- We fixed an issue that could cause the Group Policy service to stop processing telemetry information for Group Policy registry preferences.
- We fixed a stop bug (0xD1, DRIVER_IRQL_NOT_LESS_OR_EQUAL) in the DirectX kernel component.
- We fixed an issue that could cause Kerberos.dll to stop working in the Local Security Authorization Subsystem Service (LSASS). This happens when LSASS processes both User Service (S4U) User-to-User (U2U) requests for the same customer user.
- We fixed an issue affecting the Key Distribution Center (KDC) agent. The KDC agent was not able to obtain the Kerberos ticket correctly to sign the Key Trust Windows Hello for Business.
- We’ve added support for Microsoft Account (MSA) penetration scenarios in Azure Active Directory (AAD) Web Account Manager (WAM).
- We fixed an issue where Event ID 37 was logged in certain password change scenarios, including failover Cluster Name Object (CNO) or Virtual Computer Object (VCO) password changes.
- We fixed an issue that prevented the User Account Control (UAC) dialog from correctly displaying applications requesting elevated privileges.
- We fixed an issue that could cause Microsoft OneDrive files to lose focus after you rename them and press Enter.
- When you searched for the word widgets, we returned the corresponding settings page.
- We fixed an issue that prevented event 4739 from showing new values for certain properties after a policy change.
- We fixed an issue that caused the Move-ADObject command to fail when you moved computer accounts across domains. The error message is: “Multiple values were specified for a property that can only have one value”.
- We fixed an issue where you could not access the Server Information Block (SMB) share using an IP address when SMB hardening is enabled.
- We fixed an issue that caused stop error 0x1E in the SMB server (srv2.sys).
- We fixed an issue that caused the NetBIOS and DNS Active Directory domain names do not to match when you created a cluster.
