Upgrading to Windows 11 is a somewhat contentious issue. First, there are a whole raft of perfectly serviceable computers that can’t upgrade, due to various reasons often related to the security chip capabilities. Or the wrong CPU. Or a banana, or something.
For those that have updated, we have started to see the rollout of 22H2. Though “rollout” is not quite the right term; I prefer “dribble”. My Dells have had the upgrade for a month or so, while my new Samsung Galaxy Pro laptop (which I bought for its excellent Wi-Fi 6E implementation, for test purposes) is still waiting for the green light. Some say it’s down to specific printer drivers, but that can’t be the case because my Samsung has no printers installed on it. It must be something else, but what?
Anyway, I decided to upgrade my trusty rugged Dell laptop to Windows 11 22H2 a few days ago. It was delivered via a regular check-up on Windows Update, but I only let it kick into action once I’d had a quick trundle around Dell Update, Office Update, Chrome and Firefox. Best to start a session at a known updated state, after all.
I anticipated that this would be a quick update so I didn’t even bother to fire up the coffee machine. For some reason, though, it took the Dell the best part of an hour to go from fully patched 21H2 to 22H2. This is not a bargain basement device, but one with plenty of RAM, CPU and fast storage.
Given that I had decided at 15 minutes in that this had been a
