|
Patch reliability is unclear, but widespread attacks make patching prudent. Go ahead and patch, but watch out for potential problems. |
Microsoft has just posted that Windows 10 22H2 is now out for “seekers” who manually “check for updates” Remember if you want to stay at a certain fe
[See the full post at: Windows 10 22H2 is out along with “Moments” for Windows 11]
Susan Bradley Patch Lady/Prudent patcher
Just checked WuMgr, it was there, I Macrium imaged the SSD, installed it, it took about 2 minutes plus a reboot. I find it tough to believe they actually changed anything other than the label 
Edition Windows 10 Pro
Version 22H2
Installed on Thu 10-06-2022
OS build 19045.2130
Experience Windows Feature Experience Pack 120.2212.4180.0
Edit: I do need to remember to grab the iso. At the moment I have taken ubuntu/Mint out of the boot order in the BIOS so only running 10.
Windows 10 IoT Enterprise LTSC 2021 accidentally get the upgrade (Enablement Package) to version 22H2, which is not applicable and won’t install (stuck loop)
Updated Windows 10 Pro 21H2 to 22H2 using WUmgr.
All is well.
winver 19045.2130
Sorry Noel, not that I can find..sounds like nemo or thunar file explorers in linux. I’m sure there will be a GP/registry trick somewhere, sometime, somehow
Might be an idea to check https://www.elevenforum.com/tutorials/ from time to time, Brink is the dude when it comes to tweaks
Microsoft has just posted that Windows 10 22H2 is now out for “seekers” who manually “check for updates”
I say BEWARE of this. I wanted to get it done early because I am going to be really busy for awhile.
My comments on my experience:
https://www.askwoody.com/forums/topic/22h2-for-windows-10-completely-underwhelmed/#post-2490033
That was a painless experience from W10 21H2 to 22H2 
All that I done was to change GP settings before seeking:
WUfB resetting all within to ‘not configured’
Restarted the system then using WUMgr offered the ‘creature update’ and installed, simple!
2 systems now at 22H2. No issues
WUfB GP settings now as they were reflecting TRV 22H2 and SAC notify at 2
Edit: Did notice that Microsoft Defender threw a wobbly post installation which seemed to be attributed to O&OShutup 10++ v1.9.1431 settings.
Edit2: As I suspected, there’s an update for O&OShutup 10++
Had a punt at W10 22H2 32-Bit on a legacy laptop. Very quick install. Appears to be behaving itself.
RDP to my NAS, checked for updates, Windows 10 22H2 was ready for download and install. Clicked the button, and the entire process took less than five minutes.
Now running Windows 10 Pro Version 22H2 (OS Build 19045.2130). No hiccups.
Note that if you had Windows 10 21H2, and used the optional Windows update (as opposed to an ISO upgrade), the upgrade to 22H2 takes very little time. This leads me to believe the upgrade is very incremental unless you are several feature releases behind.
I’m testing with an ISO upgrade right now on one system. That is taking far longer. It appears to be going over the entire OS.
I have the target version set to 21H2 on all of the systems I manage, so they shouldn’t upgrade until it’s time. That said, I think it will be fairly quickly based on my above thoughts, unless there’s a show-stopper bug in the next 72 hours.
We are SysAdmins.
We walk in the wiring closets no others will enter.
We stand on the bridge, and no malware may pass.
We engage in support, we do not retreat.
We live for the LAN.
We die for the LAN.
Just like 20H2, 21H1 and 21H2, the update to 22H2 is via an “enablement package” (KB5015684) that simply turns on already existing features of the previous version which is why it’s so fast and only requires a single reboot.
KB5015684: Featured update to Windows 10, version 22H2 by using an enablement package
Just like 20H2, 21H1 and 21H2, the update to 22H2 is via an “enablement package”
On my Windows 10 Pro (Intel i7, 32GB RAM) the “enablement package” update to 22H2 took 3x time than previous “enablement packages”, about 10Min with A/V disabled.
The “features” for the new version of Windows (in this case Win10 22H2) already exist in the previous version (in this case Win10 2004 — 21H2) but they’re disabled.
An enablement package does exactly what the name implies, it “enables” the already existing features that Microsoft has now approved for use as a new version of Windows.
Because all the new features are already in place, enablement packages are very small (the 22H2 Enablement Package is only 177 KB) and it can update an older OS to the new version very quickly (typically 5 mins or less with a single reboot.)
If you go the ISO route instead, it takes significantly longer because it replaces the entire OS with the new version, while also making a back-up copy of the old version so you can do the “revert it within 10 days” thing if you don’t like the changes it makes, instead of simply enabling the disabled features.
BTW, it’s quite possible, maybe even likely, that Win10 22H2 already includes some features Microsoft intends to make available for the next version of Win10 that are currently disabled because they haven’t been fully tested/approved yet.
I only found four (or was it 5?) group policy changes. There’s not much. IMHO this is a lifecycle feature update meaning that it just extends the lifespan.
Susan Bradley Patch Lady/Prudent patcher
Ah, so the 22H2 stuff I originally read was for Win 11. Good, I haven’t allowed that yet and won’t soon.
On to put Win 10 22H2 into a VM to see what it does… Sigh. I remember when I used to look forward to the new releases.
-Noel
I have an old system that was running Win 10 Pro and I turned it on for the first time in quite a while today. I did already have the Group Policy Product Version set for Windows 10 and the Target Version was set to 22H2. I didn’t have to even check for updates before Windows Update started to download the 22H2 update.
I didn’t even bother to try to stop the upgrade since I just use this system as a canary in the Microsoft coal mine.
The system is old enough that its CPU is too old for Windows 11 so I shouldn’t have to ever worry about getting asked to install anything other than Windows 10 updates.
For you WSUS admins beware. The Feature Update to Windows 10 22H2 was/is available for WSUS administrators.
My Admin accidentally enabled / assigned this and my computer downloaded and installed the enablement package. This inspite of having a policy via Registry entries for to lock the machine to Windows 10 21H2.
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\TargetReleaseVersionInfo=21H2
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\ProductVersion=Windows 10
WSUS will take precedent. The reg keys are just for Windows update.
Susan Bradley Patch Lady/Prudent patcher
This is the first time I’ve seen the term “moments” related to Windows updates. I haven’t really kept up with Windows 11, so I had to go look up what it meant. Suddenly, I was craving some General Foods International Coffee.
https://winaero.com/how-to-enable-task-manager-in-taskbar-context-menu-on-windows-11/
By releasing the “Moment 1” October update for Windows 11 2022 Update, version 22H2, Microsoft has finally shipped several long awaited features, such as Tabs in File Explorer, Taskbar Overflow, and the Task Manager item in the context menu of the taskbar. As Microsoft rolls out new features gradually in its typical fashion, some users didn’t get the Task Manager entry even after installing the 22621.675/KB5019509 update. Here’s how to force enable the new taskbar context menu.
There are two ways to enable the Task Manager right-click menu option for the taskbar. You can either use the ViveTool app or a Registry tweak. Let’s review them….
regedit :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\4
Right-click the 4 subkey and select New > Key
Name the new key as 1887869580
Now right-click the newly created 1887869580 key and select New > DWORD (32-bit) value.
Name the new value as EnabledState, and set its value data to 2.
Now, right-click the 1887869580 key once again and again select New > DWORD (32-bit) value. Name it as EnabledStateOptions and leave its data as 0.
Reboot Windows 11….
DOWNLOAD READY-TO-USE REG FILES
Navigate here to download the ZIP archive. Extract it to any convenient location, and double-click the following file.
enable task manager in taskbar context menu.reg – applies the reviewed Registry changes.
undo task manager in taskbar context menu.reg – removes the changes from the Registry.
Now restart your computer, and you are done.
What new in Windows 10 22H2 ?
Windows 10 21H2 Build 19044.1862 (KB5015878) Release Preview Channel list changes
source Neowin
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
Notifications
