Win10 1803 Aug cumulative update: repeatedly ”Update couldn’t apply, reverting changes”

Topic

New Reply

Looks like this problem (which has occurred with every version of Win10, as far as I know) has reared its ugly head with the August Win10 1803 update.
[See the full post at: Win10 1803 Aug cumulative update: repeatedly ”Update couldn’t apply, reverting changes”]

1 user thanked author for this post.

Schnarph

Reply | Quote

Replies

Yep, just another month of rolling the dice.

1 user thanked author for this post.

BobbyB

Reply | Quote

That rolling of the dice game wouldn’t be called ‘craps’ by any chance?
Says it all really..

Windows - commercial by definition and now function...

1 user thanked author for this post.

BobbyB

Reply | Quote

I was hoping to confirm this on my pc but did not have any issue. The only updates my system needed were the August flash update and KB4343909. Mt work pc is a Dell optiplex 3020 SFF with an Intel SSDSC2BF256A5 256 GB sata. July updates were never installed on this pc so perhaps that is the issue.

Reply | Quote

Looks like I did install July OS updates on my system. I did not approve in WSUS however. My pc was the only one that had them. Sorry about that. Nevermind….

Red Ruffnsore

Reply | Quote

Isn’t this sort of thing precisely the justiification for updates being cumulative? Not to mention DISM being able to reach out to the network to clean up serviceability problems? We really shouldn’t be having this kind of difficulty, and NO, it’s not a good justification for having to reinstall the entire OS every 6 months.

Though I’ve experienced the subject problem in both v1703 and v1709, my current v1803 Win 10 test VM – installed afresh from a v1803 ISO early on – has, happily, survived without experiencing this issue THIS time around.

I have been keeping it up to date from the catalog a short time after each new cumulative update has become available, since I’ve finally tamed it so that it doesn’t auto-update on its own. It’s now at:

Notably, when updated from the catalog the way I am doing it the Malicious Software Removal Tool doesn’t run (and malware checks haven’t revealed any problems so far).

V1803 has for me been the most serviceable Windows 10 version so far, and has not had unexplained problems. That being said, it’s also the most bloated and promiscuous online yet, with 100 processes running to support an empty desktop (vs 40 with Win 8.1).

I’m starting to feel pressure to update my hardware system (presently running 8.1 quite stably) to v1803 because there are new applications that I’m going to need that only work on Windows 10, but MAN, it’s difficult to want it with all the extra baggage it brings along, not to mention the constant change.

-Noel

Reply | Quote

Just a thought, but does running a full reset of the Windows Update mechanism and services do any good in this case? Not just the built-in Troubleshooter, but the diagnostic cabinet you download from Microsoft?

Fix Windows Update issues

https://support.microsoft.com/en-us/help/10164/fix-windows-update-errors

(And of course, a full Disk Cleanup, including cleaning up Microsoft Updates, and emptying the Software Distribution folders.)

Methods to be used:

How to reset Windows Update on Windows 10 to fix downloads and installs issues

Here are two techniques to reset the Windows Update components to fix stuck updates trying to download and install on Windows 10.

https://pureinfotech.com/reset-windows-update-windows-10-fix-downloads-installs/

If the problem runs any deeper, I would use my latest system image archive to perform a rollback to the system state before the error occurred. If this doesn’t fix the issue, maybe it’s time to revert to Version 1709 (or 1703) after all.

If this is occurring shortly after an in-place 1709 to 1803 upgrade, does removing the Windows.old stuff and doing a complete Disk Cleanup with Windows Update Cleanup do any good?

-- rc primak

Reply | Quote