KB5040525 is exclusively available for Windows 10 22H2 PCs, encompassing x64, x86, and ARM64 architectures. Rather than providing individual download links that may expire, users are directed to an official page hosting the offline installer file for all processor types.
What’s New in the KB5040525 Update for Windows 10?
Unlike June’s optional update, which introduced the Copilot app to Windows 10, this month’s update is primarily focused on resolving existing issues. With the end-of-support date looming 15 months away, it's not surprising to see fewer feature additions. Here are the key issues addressed by the KB5040525 update:
- Windows Defender Application Control (WDAC): Previously, WDAC would malfunction if more than 32 policies were applied simultaneously. Additionally, memory leaks occurred during device provisioning, and some applications failed post-policy application.
- Print Support App: The app would become unresponsive when attempting to print from a USB device.
- Universal Print Service: When Web Proxy Auto Discovery (WPAD) was enabled, Universal Print clients failed to work with the Universal Print service, affecting numerous printing functions.
- Windows Backup App: The app failed on devices with an EFI system partition (ESP).
These are some of the significant issues Microsoft has addressed with July’s optional update. Notably, the DHCP Option 235 problem, which has persisted since the January 2024 optional update, has finally been resolved. For a comprehensive list of bug fixes, users can refer to the official support document. However, the profile picture bug remains unresolved.
Known Issues
The notorious profile picture bug, which generates the error code 0x80070520, continues to plague Windows 10 users. Despite Microsoft's efforts, this issue remains unresolved. The Settings app erroneously displays the error code while users browse and change their profile pictures. Although the picture change is successful, the misleading error code message still appears.
Windows Latest attempted to replicate the error by changing the profile picture and found no issues, suggesting that this problem might be isolated to certain users.
