KB4592438 CU Windows 10 v2004 build 19041.685 and v20H2 19042.685 Win Update

bitwise said:

Hey Dave. I don't know if you're still struggling with the update, but if you uninstall the 20H2 Enablement Package, it reverts back to 2004 and then you can do an in-place repair/upgrade. I was on 19042.630 and doing that worked like a charm for me.

Thanks for that @bitwise, sorry for the delay replying but I didn't get any notification of replies!

I've tried rolling back recent updates to try and solve the problems, and one of them turned out to be the 20H2 update, even though it said it was installed today, which is nonsense, it was installed several weeks ago!
It then reverted to 2004, but offered the 20H2 update, which failed with the same error (0x80070003).

I ended up having to do a system restore, which has put it back to 20H2 19042.630.
The KB4586853 update is now being offered again, but still failing, same error.

I have now tried doing an in-place repair, but it's not letting me keep my files and apps.
It says "Your files, apps, and settings can't be kept because your current version of Windows might be installed in an unsupported directory (it isn't), or you're trying to install an older version of Windows (I'm not!)
So, what do I do now?
I'm NOT doing a clean install!

steve108 said:

Must be a regional word - I was wondering too.

It's something of a Britishism.

(Also for Steve108 and Rose)

After a long battle (at least for me!): Dead, wounded, survivors, cute nurses wiping my forehead I managed to upgrade to 685.

With a Steve McQueen audacity I cut, as they say, the bull's head: I just followed the excellent Brink's excellent "Repair Install Windows 10 with an In-place Upgrade" on the spot using option 3 and the fears disappeared and in the end I found all my… stuff.

Yup! It's true!

The battle lasted a long time: at least a few hours, but now it is over and everything seems to be fine and peace reigns.

What I do not understand, however, are the new elements that have appeared in the Firewall and you know Microsoft despite having provided the "Details" button, which are sometimes disabled, is very stingy with information ... otherwise the suspense is less.

Thanks for the heads up Paul. Much appreciated!

Clintlgm said:

Thanks I didn't know this word

No problem Clint. I did not want to beat about the bush explaining it. Leaving someone high and dry and barking up the wrong tree with regard to language can make them feel they are a few sandwiches short of a picnic.



@sneekez

Here is how I kitted out the USB with Windows 10.

Use "Rufus" to create Bootable Window 10 USB for Legacy BIOS and UEFI