Windows 10 Version 22H2 (KB5022834) will not update

Can confirm, had the the same thing happen on 2 machines as of right now, both are notebooks for some bizarre reason.

HP ProBook 450 G1 and 470 G1 both fail to install KB5022834, everything else installs fine. Both are clean installs. The odd thing is i took a Dell OptiPlex 3020m that i had on hands and did a clean install on that, all updates installed no problem.

I have tried everything and still no success!

I fail to see how Microsoft or those purporting to assist them are not able to investigate the source code and find out what the software is actually trying to do when it fails, but that's Microsoft for you.

Given that it is impossible to permanently disable an update (even one that clearly does not work) I have now had to set this to their maximum 35 days to avoid extended shutdown and boots while it repeatedly tries to install then immediately uninstalls. In accordance with Microsoft policy, when they report 100% they actually mean something else as this meaningless figure only applies to Microsoft and not he rest of the planet!

I am reminded of a similar thing when Win98 changed to XP, when XP changed to 7, when 7 changed to 10, and now when 10 changed to 11. Each time, because it wouldn't update I had to install from new every time and reinstall all my software. I suspect this is another Microsoft ploy to ensure everyone changes to 11, by forcing you to do it. As after each new install with the same hardware and configuration the updates included in the new software work without a problem so it cannot possibly be hardware related.

I can see no reason why a clean 10 install with nothing else added or changed would fail to install this update too, but you may have already guessed that Win 11 installs from a fresh iso including this update.

I am now using Linux with the bare essentials that require Windows working in virtual environment with no updates and therefore no more dodgy MIcrosoft.

Once Google get a rival system working then Microsoft are truly screwed. It's only a matter of time!

Well it appears that many hours (both billable and non-billable) have been wasted by many trying to resolve this issue to no avail. As a contractor, my client has so far spent way more than is reasonable trying resolutions to a known issue by Microsoft which do not work. Microsoft's quality control and regression testing (or lack thereof) is getting worse instead of better. I too am headed toward Linux and hopefully another option in the future. This is totally unacceptable as is all the collective time that has been wasted with these garbage "solutions" that don't work. So now I guess I'm faced with babysitting these pages to see when an actual solution that works is posted...if that's even on Microsoft's agenda. As Annie states above, it looks like Win 11 is getting jammed down our throats even though a number of business critical apps do not work on it. Gotta love it

Windows 10 Version 22H2 (KB5022834) will not update >

Complete joke this, and Microsoft is laughing at us.

Hi,

Meanwhile I found the solution in my case. I found out that not Microsoft is responsible for the impossibility to install this update, but Rollback Rx Pro. RBX is a way better alternative to the Windows Restore System, that don’t solve most of the more serious problems one can have with the OS. RBX (combined with a with Macrium Reflect cloned system on an external M2 SSD Drive for the worst cases) avoids very often the necessity to reinstall the system and saves a lot of time. But RBX don’t say that it must be disabled for some Windows updates and proposes only the option “Allow updates that cannot be rolled back” and “Turn off automatic Windows Update”. When I disabled RBX, the update could install. Thus, the honesty obliges me to correct my point of view about the actual updates, even if we encountered many problems with the major updates in last years, as also reported in the specialized computing press.

Hope, this last info can be useful for Rollback RX Pro users. This shows also that one the best solutions in the actual case is probably to search for interactions between third part software that have an influence on the system management and the Windows Update process. ;)