On January 9, 2024, Microsoft released the KB5034129 update for Windows Server 2022 based on Windows 10, to fix issues including problems affecting InTune, and an error where Microsoft Excel stops responding when sharing Excel spreadsheets as PDFs in Outlook.
KB5034129 is a mandatory update as it fixes an issue with wireless network cards, and most companies will install it promptly. However, many users reported that after updating Windows Server 2022, browsers like Microsoft Edge, Google Chrome, and Mozilla Firefox only display a blank page when opened.
Windows Latest tested and confirmed this issue.
After installing the update, Edge occupied about 50% of CPU usage, with 12 Edge processes and 8-10 Windows error reporting processes running. It also caused disk space to be fully occupied, but this only affected some of the terminal servers.
Chrome would open to a blank screen, and logs showed a GPU loading failure. Attempts to update VMWare Tools, the latest Chrome Beta version, and reinstalling Chrome did not resolve the issue, and the only solution was to remove the update.
Solution
After installing the KB5034129 update, if browsers like Chrome or other applications crash, as tested by Windows Latest, the following methods can be tried for Chrome as an example:
Deleting the registry key “HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionImage File Execution Options” under “chrome.exe” can solve the problem. Use PowerShell to run the following command to delete the .exe file: reg.exe delete “HKLMSOFTWAREMicrosoftWindows NTCurrentVersionImage File Execution Optionschrome.exe” /f
Alternatively, renaming chrome.exe, for example to chrome_test.exe, can restore Chrome to normal functionality.
Other Issues Related to KB5034129
Additionally, when installing the KB5034129 security patch, you may encounter the error code 0x80070643. This occurs even on Server 2022 virtual machines newly created from the official ISO file, which have a standard 200GB virtual hard disk with a 573MB recovery partition, indicating that the issue is not related to the image or the base image.
Windows Latest testing found that this issue occurs when the system detects a recovery partition with low storage space. You can resolve this issue by increasing the size of the partition.
Related:
- Google Faces Monopoly Verdict, DOJ Demands Chrome Sale
- Unlocking the Future: Microsoft Embeds AI in Notepad App!
- A Complete Guide to Upgrading ASUS Motherboard BIOS
- New ChromeOS Feature: Tailor Keyboard Shortcuts Your Way!