An experience of upgrading to 20H2 - comments/advice appreciated

Talk about confusing updates... see first vs last..

dalchina said:

Talk about confusing updates... see first vs last..

Yeah LOL. They seem to cancel each other out. With the Adobe Flash removal... being the winner.







Side note: Some of these 2021 updates seem to take longer to install, than they should.
They've started mixing the SSU in with the CU.
So the computer has to think for a while, about which to install first. :/

But they DO work, without outside assistance.

During the installs, I can just hear the computer thinking...

Ok, install the CU. Oh wait, I need the SSU first. Ok, reverse the install of the CU, install the SSU, then go back to installing the CU.
About as smooth as 16 grit sandpaper.

- thought including the SSU sounded a good idea.. there was 1 thread where the update was failing 'cos the SSU was lacking...

dalchina said:

- thought including the SSU sounded a good idea.. there was 1 thread where the update was failing 'cos the SSU was lacking...

It's a great idea. MS just needs to adjust the way the overall monthly update "checks" to see if it needs to also install the SSU. They DO work. At present they "feel" a tad clunky, during the install though.

IF there's another SSU coming with tomorrow's CU, we'll find out if they got the process smoothed out a bit.

Btw, KB4023057 in your list, is an SSU.

Hi, first, I created a current disk image.

Then as I'd used Sledgehammer to stay with 1903, I uninstalled that (took a couple of goes reinstalling and uninstalling to get the WU service running again- not possible manually). There was an update to 1903.

I uninstalled Aeroglass (which would be incompatible with a later build).
I didn't change anything about Avast antivirus which I happen to run.

Then I simply let Windows Update do its job.

There was one case where I downloaded an iso file and used that, and performed the upgrade offline (no updates during it, as Windows Update or upgrading with updates failed on that occasion.

Depends on what you're facing, really.

Things to check after upgrading:
Device Manager- any missing or indications of problems
Devices which your manufacturer might specifically support e.g. backlighting, special keys
Fingerprint reader- sometimes not supported after an upgrade

Check and redo any hacks or modifications you've done that you might expect to be overridden by an upgrade.

E.g. I have a program (now no longer available, although I've seen something similar recently) that replaces 70+ icons in imageres.dll with nice Win 7 icons in a few seconds.

Check all startups have done so.

Look for broken/changed features - loss of data in MS originated apps (like my reminders!)

When happy, create a new disk imaging job and a new base (initial) disk image for the new build.

Find solutions or replacements for things that no longer work as they did.

I agree about not relocating those folders.
a. There's no need
b. It's easy to make a bad mistake
c. They often contain folders created by programs you've installed, so they're not 'your' folders entirely
d. It's easy enough to create your own and add them to a library or create your own if you wish.
e. Some have had issues when upgrading with relocated folders.
I can't think how definite the line is on that. I believe that should generally be fine- although be careful you don't end up with, say, a new Recovery partition on a different drive.

It is, however, a very good idea to keep personal data off C: for O/S maintenance reasons.