Windows 10 22H2 is here.

[nukecad]

Microsoft has announced the availability of Windows 10, version 22H2 (aka the Windows 10 2022 Update), now rolling out to all eligible devices.

I'm not being offered it on 'Check for Updates' yet.
EDIT- I just booted my much older, much less powerful, second laptop and that one is being offered 22H2 straight away without me even checking. Microsoft works in mysterious ways.

It is available on the Update Assistant if you want to get it that way, (or if you want to create installation media):
https://www.microsoft.com/en-gb/software-download/windows10

[hazelnut]

It's a bit of a non event really, nothing has really changed apart from the build number.

Took approximately 2 minutes to install.

[nukecad]

About 25 mins to do this months Patch Tuesday updates on the old laptop, then straight after restarting 3 mins to do 22H2.

It is an enablement package, so it's just activating stuff that's been downloaded previously.

[nukecad]

It's  done a few odd things, but that may be because the Windows on that laptop is unactivated?

All the normally hidden little partitions. eg. the System Recovery partition, have been given a drive letter and so now all of them appear in File Explorer. Plus my mapped network drive dissapeared.

I've sorted them out but still odd that it did that.

Be interesting to see if anything similar happens with the main laptop which has activated Windows when that updates.

[hazelnut]

16 minutes ago, nukecad said:

  but that may be because the Windows on that laptop is unactivated?

 

I would think so.

[Andavari]

Typical, it wasn't offered to my laptop so I did the whole image download thing yet again which at this point I'd do anyways because I actually want the full setup files archived after Win10 nuked itself earlier this year and was very corrupted.

Did the usual:
1. ChkDsk /F all drives.
2. Full disk image backup with Macrium Reflect.
3. Downloaded the installer and made the USB Flash Drive version which was rather fast this time since I used a USB 3.0 Flash Drive for the first time.
4. Watched the setup loop several times re-doing things it had already done or attempted, then it finally got past the looping looking for updates glitch it was having before it actually started. No errors displayed though, but it was weird and easily doubled the time it took.
5. After setup ChkDsk /R the OS drive, then in Windows I had to restore all of my non-standard "tweaks" and settings that it always nukes.
6. Had to restore the setting for Windows to automatically create a registry backup, it always nukes that setting.
7. Ran the corruption fixes with DISM and SFC, and as typical it had corrupted something and automatically fixed it.

Interestingly enough all those restarts it does installing look to me like it's just pulling the plug, and when I looked at the S.M.A.R.T. events for my boot Micron M.2 SSD it does seem to be doing that as they were logged as unexpected power loss events. Now I'm wondering if that's when it seems to always corrupt something!

[OlinTucker]

Thanks for sharing this news with the community. It's great to hear that the latest Windows 10 update is finally here. As for not receiving the update on your device, sometimes it takes a bit of time for updates to roll out to everyone. It's good to hear that you were able to get it on your older laptop, though!