Unable to uninstall after updating Win11 KB5034765?

The recently released Windows 11 cumulative update KB5034765 caused issues with the desktop and taskbar displaying slowly after installation, but this has now been replaced with a fixed version by Microsoft.

Is Win11 KB5034765 frustrating? Fixed issues and new ones

I also uninstalled the original version of KB5034765 and installed the replacement version of KB5034765.

However, in some environments, after installing KB5034765, there seems to be an issue where the share button does not work when connecting an Xbox controller via Bluetooth (X formerly Twitter), so some users may want to uninstall it.

Thinking about this, I decided to try uninstalling it.

However, on both of my PCs, I am no longer able to uninstall the replaced version of KB5034765.

Windows Update Even when I go to "Update History" > "Uninstall Updates" from the above screen, KB5034765 is not displayed on one of the two computers, but it is displayed on the other computer, but even after uninstalling it, it reappears (it cannot be deleted).

The wusa command cannot be executed (it cannot be uninstalled because it is required for the computer), and the Dism command displays error code 0x800f0825 and says "DISM failed."

Uninstalling with the wusa command
Uninstalling with the wusa command

I don't know if this is just my situation, a bug in the superseded version of KB5034765, or if Microsoft did this intentionally.

Also, it seems that there are still some environments where KB5034765 cannot be installed.

postscript:

Apparently, the cause was "Windows Update Cleanup" in "Settings" > "System" > "Storage" > "Temporary files".

When deleting temporary files, the "Windows Update Cleanup" option may be checked by default, so please be careful if you plan to uninstall KB5034765.

Normally, "Windows Update Cleanup" deletes files related to old updates (such as those from several months ago), but on both PCs where KB5034765 could no longer be uninstalled, "Windows Update Cleanup" had been performed after installing KB5034765.

I don't think it affects files related to recent updates, so maybe this is a bug?

*Although there are some minor issues, KB5034765 includes fixes for many vulnerabilities, making it a must-have update for security.

If you found this article helpful, please share it on social media.

Person who wrote this article

Driven by questions arising from my daily PC use and the desire to "do more," I have been pursuing self-study in Windows since around 2008. I am sharing the "aha!" techniques and solutions I discovered through trial and error with the sole purpose of helping you in your PC life.

View profile

Comment:

To comment

[About submissions]
We welcome any questions or information regarding the content of the article.
However, please note that content unrelated to the purpose of the article, criticism of specific individuals or organizations, offensive language,Inappropriate wordsComments containing the above may be deleted or made private without notice at the discretion of the administrator.
Please note that spam may be automatically deleted by anti-spam measures.

CAPTCHA


table of contents