Many users report problems with February 2024’s Windows 11 KB5034765 security update. Installing it often fails with cryptic error codes 0x800f0922, 0x800f0982, or 0x80070002.
Even if installed, it may cause File Explorer to crash on reboot or the taskbar to vanish entirely. So, this critical patch is far from seamless for many.
Microsoft strives for universal automated updates without disrupting work, but KB5034765 misses the mark and interrupts productivity for many Windows 11 users. Whether failing the install or enabling nasty post-update bugs, the February 2024 patch frustrates more than helps.
With reboot errors and disappearing interface elements post-install, this proposed “fix” ends up causing new issues like rubbing salt in update wounds. Here’s hoping debugging efforts can reshape KB5034765 into the passive and helpful background update Windows patches aim to be.
Problems installing update KB5034765
Many users report that the security update will start to install but then abruptly fails mid-process. Specifically, the patch successfully downloads and prompts a reboot to finalize the installation. However, during the reboot, Windows Update itself unexpectedly stops. Users are kicked back to the desktop with an error that the update could not complete.
People have tried repeating this process several times, but each attempt shows this same pattern – the patch begins installation after a reboot, then Windows Update encounters an internal error. No specific details show regarding where things went wrong. Ultimately, the OS fails to finalize applying the update and boots the user back into a still-vulnerable unpatched Windows environment.
This pattern of initially successful download followed by failed mid-install during reboot creates great update frustration. Despite troubleshooting efforts and repeated manual update initiation, the essential security patch remains unable to finalize and take effect as Windows’s own update manager raises issues.
Solution to KB5034765 update installation issue
It seems like there’s a workaround available for installing the KB5034765 update by deleting the hidden folder called $WinREAgent. Here are three methods you can try to remove this folder from your Windows 11 installation:
Method 1: Run Disk Cleanup as administrator, select the system drive, and check the boxes for “Temporary Files” and other relevant options. Click “OK” to delete system files, including Windows Update files. This action will remove unnecessary files within $WinREAgent.
Method 2: Open File Explorer, navigate to the system drive, and ensure that you’ve enabled the option to view hidden items in the folder settings. Locate $WinREAgent and remove it from the system.
Method 3: Open the Command Prompt as Administrator and execute the following command: `rmdir /S /QC:$WinREAgent`
You can choose any of these methods that you find most convenient, and hopefully, this will resolve the issue with installing the KB5034765 update.
Problems with File Explorer when restarting
Some PC users face a recurring issue where File Explorer crashes upon rebooting or shutting down the system. This problem initially surfaced with the optional Windows 11 January 2024 update and has unfortunately persisted into the mandatory security patch.
The error message points to an application error with explorer.exe, highlighting a specific memory address and stating, “The memory could not be written.” Despite various troubleshooting attempts, including running the System File Checker tool (sfc /scannow), testing RAM with Windows tools and memtest86+, and even clean reinstallations of Windows 11, the error remains unresolved.
Interestingly, many affected users share a common factor: the presence of a controller accessory like an Xbox 360 controller for Windows connected to their PC. Although this connection has been noted, it’s unclear if it directly contributes to the issue.
Microsoft’s release notes for update KB5034765 indicated a fix for an issue where explorer.exe might stop responding when a PC with a connected controller accessory is restarted or shut down. However, despite this supposed solution, users continue to encounter the problem.
