Windows 11 Version 22H2 updates, installing, failing, rolling back, failing....

Just curious.. how many times will windows try to install the failing Cumulative update packages before it gives up? It's wasting 10 minutes of my time whenever it tries; installing, failing, rolling back, failing, rolling back... What will happen when the next cumulative update is downloaded?

After having spent a couple of hours performing suggested fixes on the net. I dont intend to waste more time on this. If I wanted to be a Windows system engineer I would have chosen another education. And no, it's out of the question to reinstall a fresh OS.

I have noticed that a lot of other recurring updates like security threats and drivers for instance are no problem which makes me believe there's no problem with the basic system updates procedures.

Just curious.. how many times will windows try to install the failing Cumulative update packages before it gives up?

Click to expand...

If only the folks at Microsoft knew it themselves

MartinK said:

Just curious.. how many times will windows try to install the failing Cumulative update packages before it gives up? It's wasting 10 minutes of my time whenever it tries; installing, failing, rolling back, failing, rolling back... What will happen when the next cumulative update is downloaded?

After having spent a couple of hours performing suggested fixes on the net. I dont intend to waste more time on this. If I wanted to be a Windows system engineer I would have chosen another education. And no, it's out of the question to reinstall a fresh OS.

I have noticed that a lot of other recurring updates like security threats and drivers for instance are no problem which makes me believe there's no problem with the basic system updates procedures.

Click to expand...

It won't give up, if the updates won't install there's a problem with the update process. I had something similar where the Defender updates would install but nothing else. Once an update fails, it will keep failing.

Only solution is to try a Repair install (this won't delete everything, just replace the existing Windows image with a new one, keeping all your files and settings). Letting the installer check for updates will likely fix the problem. Once the process starts it takes 30-40 minutes depending on your disk speed.

You could also get an integrated ISO from UUP Dump which contains the latest update already in the image. Run a repair install using that.

More like "a Windows Beta Tester" - cause engineering is about the creative process. And truth be told - we kinda are (even if not part of the Windows Insider program). The thing about Windows (or a potential issue - if you will) - it's a collective product. And when i say collective - it's not just about all the people from Microsoft - but all the partnerships involved (OEM like ASUS - which makes a custom build paired with Chips from Intel, AMD, nVidia, realtek, etc) + Microsoft (the Windows devs). Another way to put it: Windows was not particularly made for your exact model (Asus PN51-1E MiniPC) - more like Asus made a custom PC while using hardware from multiple manufacturer - which should be able to run Windows. And it does - since it was tested and passed that test for a particular Windows build (latest at the time of manufacturing). And that's just it - a new Windows build and X updates are also beta tested - but in a more general way. Also, the closer your PC is - to the general designs (with the highest amount of beta testers) - the higher the comparability. This is actually among the main reasons - why in a professorial environment (big corporations in particular) - monthly Windows Updates are not a thing even a worry (be it a Windows Update issue or otherwise - they don't afford to waste time on solving this type of issue / i mean sure - they might afford it in the literall sense - but they could still be costly time wise and loosing money can be triggering even for the richest of corporations).

It's not like an Xbox, a Smartphone, or even a system made by Apple - where the ones in question "tailored the OS for those particular components (not the other way around)". It's why using the custom OS that came with this devices - most issues are also beta tested by the actual engineers working on that exact same model.

Still, sometimes it's actually an issue with Windows itself - like the updater or the cache getting corrupted for whatever reason. That being said, what exactly did you try so far?!

PS. For certain PCs (more uncommon - where there's usually less beta testers besides the OEM - Asus in your case) - it can help to Pause major Updates for at least a month.

Preview and Insider releases are not as stable as Production releases. My experience with Production releases of W 11 has been very good so far.

MartinK said:

What will happen when the next cumulative update is downloaded?

Click to expand...

Once one fails they'll all fail until whatever problem that's causing the failure is resolved. What fixes the issue for one will not always be the fix for the next guy. I believe the cause of cumulatives failing is machine specific. The kicker is, from reports here, mosttimes it's only cumulatives that seem to cause the most problem.

This began happening to me back in 2022. I spent days testing over a period of 3 months and multiple cumulatives, running through every solution I could find and putting my machine into many configurations. In my particular case, I found that running a 3rd party AV (MWB) kept it from applying. I proved my AV being on did not affect any other updates, only cumulatives. Yet other people using MWB experienced no problem.

But I also found that once a cumulative failed with AV on, turning off the AV AFTER a failure was not enough to get the update to apply. I had to restore an image first (or do a repair install), turn off AV, and apply update. My hypothesis is that once a cumulative fails some sort of bit is set in my machine which puts it into a sort of update failure loop. (but here again I'm speaking for my PC. I can only surmise what was happening in my case).


Now, every month the day before update Tuesday, I make a new image and manually stop my AV until after that month's cumulative applies. I turn AV back on and wait another month until I do it again.

glasskuter said:

Once one fails they'll all fail until whatever problem that's causing the failure is resolved. What fixes the issue for one will not always be the fix for the next guy. I believe the cause of cumulatives failing is machine specific. The kicker is, from reports here, mosttimes it's only cumulatives that seem to cause the most problem.

This began happening to me back in 2022. I spent days testing over a period of 3 months and multiple cumulatives, running through every solution I could find and putting my machine into many configurations. In my particular case, I found that running a 3rd party AV (MWB) kept it from applying. I proved my AV being on did not affect any other updates, only cumulatives. Yet other people using MWB experienced no problem.

But I also found that once a cumulative failed with AV on, turning off the AV AFTER a failure was not enough to get the update to apply. I had to restore an image first (or do a repair install), turn off AV, and apply update. My hypothesis is that once a cumulative fails some sort of bit is set in my machine which puts it into a sort of update failure loop. (but here again I'm speaking for my PC. I can only surmise what was happening in my case).


Now, every month the day before update Tuesday, I make a new image and manually stop my AV until after that month's cumulative applies. I turn AV back on and wait another month until I do it again.

Click to expand...

Yes there were plenty of people with Cumulative update problems back in July if I remember correctly. In the end I did a repair install and let Windows find the latest update during the process. It's worked ever since, with every update.

BrianInEngland said:

Yes there were plenty of people with Cumulative update problems back in July if I remember correctly. In the end I did a repair install and let Windows find the latest update during the process. It's worked ever since, with every update.

Click to expand...

Then you're lucky a repair install was a permanent solution for you. If I do not intervene it will happen to me every single month. During those months of testing, I was cross-eyed after doing so many multiple repair installs and image restorals.

After 38 years MS still hasn't 100% mastered its update process. I guess it can't considering how many different configurations it has to work with.

MartinK said:

it's out of the question to reinstall a fresh OS

Click to expand...

Never say never. I highly recommend that once you determine and fix whatever is causing updates to fail for you that you develop some sort of backup solution. Hardware fails, files get corrupted. Having a system image is the ONLY solution to never having to reinstall everything again.

All of you are of course right. I know that much about windows, there isn't a conclusion to such problems. So despite my frustration, at some point I guess I have to go for a repair install. The suggested integrated ISO from UUP Dump install with the latest update sounds like one solution.

Another thought.. it's obvious that the more changes MS stuff in to their cumulative updates, the bigger are the chance for an error. In addition they should optionally be available as updates broken down in smaller portions. That would show immediately which updates are failing. ?

.. and another follow up!

Baffling Windows 11 TPM Bug Is Wreaking Havoc On Some AMD Ryzen Systems

This article is one of several that might explain the problem? TPM module on the AMD Ryzen 51 is not acknowleged by MS, hence the updates will not work.

Resetting WU is worth a shot. It might be all that's necessary in your case. Reset Windows Update in Windows 11 Tutorial

MartinK said:

.. and another follow up!

Baffling Windows 11 TPM Bug Is Wreaking Havoc On Some AMD Ryzen Systems

This article is one of several that might explain the problem? TPM module on the AMD Ryzen 51 is not acknowleged by MS, hence the updates will not work.

Click to expand...

That has nothing to do with Windows Updates. It affects only the TPM feature - if you happen to use it (that is). It's also worth to be added - that you can install Windows 11 on systems lacking the TPM labeled as a requirement (thus, officially - not supported for Windows 11). Yet, even those can work/update just fine. While other systems - where all the official requirements are met - could still run into some issues.

Giving credit where credit is due.... This days - Windows Update is one the most prioritized feature by Microsoft , as in:

They added multiple services by now - which are suppose to help with Windows Updates (even actively check/monitor).
There's a Windows Updates troubleshooter - which is actively improved as well.
There's also the option to install Windows Update - using a standalone installer: Microsoft Update Catalog

If none of above works - there's also tons of extra info on the internet for people who ran into similar issue. More often than not - clearing the cached Update files (which got corrupted for whatever reason) - and resting/restarting the Windows Update Services - does the trick.

What can say - the Windows Updating feature is rather outdated in terms of functionality and not as transparent as other Operating Systems. But this is more of a Windows issue - getting constantly recycled with every new release - instead of a rework from the ground up. Point being - technically, you could call Windows 11.... Windows Vista Service Pack 18 - since Windows 11 is more about the surface (user interface), or DirectX Ultimate and some extra features here and there. While underneath - there's tons of recycled features from older Versions of Windows. Maybe that will chance with Windows 12 or... Windows XX - hard to say...

neves said:

That has nothing to do with Windows Updates. It affects only the TPM feature - if you happen to use it (that is). It's also worth to be added - that you can install Windows 11 on systems lacking the TPM labeled as a requirement (thus, officially - not supported for Windows 11). Yet, even those can work/update just fine. While other systems - where all the official requirements are met - could still run into some issues.

Click to expand...

Ok, one issue less to look into. Might as well try the Reset Windows update in Windows 11 suggestion allthough I have tried some similar things before.