Windows 10 Insiders on 22H2 are getting a new build today for the Release Preview Channel, bumping the build number up to 19045.2670. There’s quite a long list of fixes:
- We fixed an issue that stopped hyperlinks from working in Microsoft Excel.
- We fixed an issue that affected the Appx State Repository. When you removed a user profile, the cleanup was incomplete. Because of that, its database grew as time passes. This growth might have caused delays when users signed into multi-user environments like FSLogix.
- We provided support for the United Mexican States’ daylight-saving time change order for 2023.
- We fixed a resource conflict issue between two or more threads (known as a deadlock). This deadlock affected COM+ applications.
- We fixed an issue that affected IE mode. The text on the status bar was not always visible.
- We fixed an issue that affected cbs.log. This issue logged messages that were not error messages in cbs.log.
- We improved how the Remove-Item cmdlet worked for Microsoft OneDrive folders.
- We fixed an issue that affected AppV. It stopped file names from having the correct letter case (uppercase or lowercase).
- We fixed an issue that affected Microsoft Edge. The issue removed conflicting policies for Microsoft Edge. This occurred when you set the MDMWinsOverGPFlag in a Microsoft Intune tenant and Intune detected a policy conflict.
- We fixed an issue that affected Azure Active Directory (Azure AD). Using a provisioning package for bulk provisioning failed.
- We fixed an issue that affected a certain streaming app. The issue stopped video playback after an advertisement played in the app.
- We fixed an issue that affected MSInfo.exe. It did not correctly report the enforcement status of the Windows Defender Application Control (WDAC) user mode policy.
- We fixed accessibility issues. They affected Narrator on the Settings home page.
- We fixed an issue that affected the Local Security Authority Subsystem Service (LSASS). LSASS might have stopped responding after you ran Sysprep on a domain-joined machine.
- We fixed an issue that affected virtual machines (VM). They stopped responding when you added a new disk to a storage pool in thin provisioning scenarios.
Are you a Windows 10 Insider? Let us know in the comments below.