Microsoft is still torturing its users with the Windows 11 2024 update officially released on October 1 24H2 East affected by many errors. And now a new update designed to fix some of those bugs is adding new bugs. One of which, extremely ironically, prevents us from… installing it.
Rolling out from October 24th KB5044384 is reported to have fixed some issues which affected people who installed Windows 11 24H2. These include:
- A bug where the System File Checker incorrectly reported certain files as damaged
- Disk Cleanup’s inability to handle the deletion of 8.63 GB of cache
- Fixed an issue where the screen would jump back and forth on some computers when using Alt+Tab to switch windows.
Patch not installing!
But the correction itself turns out to be problematic, as indicated The latest Windows. The main problem seems to be that it doesn’t even establish itself in some people. These users report that the update gets stuck at about 40%, then stops or rolls back, showing error codes like 0x800f0922, 0x800736b3, 0xc015001a, 0x800f0991, and 0x80242008.
In other cases, the patch hangs at 90-95%, prompting you to try again, but triggering an install error when you do. Installation issues do not appear to be specific to any particular hardware. Even computers with relatively new chipsets are affected.
A workaround suggested by Windows Latest is to manually install the KB5044384 patch instead of downloading it from Windows Update on your PC. To do this:
- Access to Microsoft Update Catalog page
- Click the Download button for the appropriate “KB5044384” link for your system
- Click the link to get the MSU file
Please wait before updating!
But even if the patch is installed successfully, problems may persist. In some cases, Task Manager cannot correctly count the number of background processes.
“Sources close to Microsoft” told Windows Latest that the company is aware of this issue. She puts it down to a reporting problem. Also, pressing Alt+Tab to switch to another window can still trigger a black screen, although the hotfix supposedly fixed this issue.
Probably aware of the problems, Microsoft is gradually releasing KB5044384.
Rather than be out of luck, better wait for the next Patch Tuesday scheduled for November 12th.
