Generally... after doing an In-Place Upgrade, you won't HAVE to do another for a loooong time.
Most of us, after doing one of these, learn to employ backup software religiously.
Macrium Software | Macrium Reflect Free
With good backups, it's pretty hard to get Windows messed up enough to require an In-Place Upgrade.
Thanks ... although getting astray aka OT ...
I've used the Media Creation Tool on previous occasions but getting an iso that was not compatible with my beta insider build and the options to keep personal data and apps was just greyed out ... so I actually didn't want to use it (2004)
(Irrelevant comment: Although my profile says "junior member" I'm not really junior Windows user LOL! In a dark past I have used Windows version 1.0 ...a very very long time ago, but I appreciate all thinking paths to solve problems!)
I'm not really ON the beta channel. I just ended up on 19043 accidentally. (long story).
Anyways... maybe try this?
For older ISO image versions, go here instead...
Download Windows 10 ISO File
I use 3 different backup programs making images and backing up stuff to half a dozen of places, all in an automated but monitored way, external HD's and including 2 NAS devices, but that doesn't solve the problem of a failing update
That's true too, and I have a Full licence for Macrium because it's so useful. If a CU fails to install there's no option but to do a repair install to get to the latest version, as was the case with going from .899 to .906Generally... after doing an In-Place Upgrade, you won't HAVE to do another for a loooong time.
Most of us, after doing one of these, learn to employ backup software religiously.
Macrium Software | Macrium Reflect Free
With good backups, it's pretty hard to get Windows messed up enough to require an In-Place Upgrade.
- - - Updated - - -
Exactly this
Well there's always the last resort option....
Get on a 3-4 hour chat with MS support and let them figure it out.
They will eventually do the same thing... try to reset WU, and if that doesn't work... In-Place Upgrade.
As for your backups... you might try going back to say... February backup and THEN trying this April 13th CU.
In other words... back before the problem developed in the 1st place.
/edit
I was on 19042 until March 1st, when I ran an enablement package to go to 19043.
But technically, I'm NOT on beta channel.
In fact, up until this CU, I had to get my updates manually from the catalog, cause WU was confused.
My version said I was on beta channel, but MS disagreed.
So... I couldn't "automatically" get either the 19042 or the 19043 updates.
BUT... this April 13th update fixed all that somehow.
I think I must now be on the "charlie channel" or something.
Done on non-production machine with no issues:
Perhaps try the only thing that worked for me (posted on the previous page). I had gone through every other option being suggested here:
KB5001330 Windows 10 Insider Beta 19043.928 21H1 and RP 19042.928 20H2
Installed on both test machines without issue. Kind of missed this post at first, though...
Sigh.
--Ed--
Quote
