Comments on: Windows 10 22H2 Upgrade using SCCM Feature Update Option

By: Ian Spencer

Ian Spencer

Hi all,
Interesting, I am desperately trying to test deploy 22H2 Win 10 via the In-place FU enablement package. I am possibly getting side-tracked by the Dynamic update switch which is currently not-configured in the devices client settings? According to the above article it is a prerequisite but not much of a mention here? MS seems to talk about it being key when you are building Wim files for OS imaging. But cannot see anywhere else where it is required. We never had this problem with other earlier version 21H2/1909 etc. in-pace FU upgrades? I am gonna enable Dynamic updates on few devices I am trying to FU and see what happens. Any thoughts? Cheers

By: Harish

Harish

Hi Prajwal,
Have an issue in our environment where 100 machines upgraded from 21H2 to 22H2.
Findings from SCCM are
1) No servicing plans configured.
2) No download or deployments for feature update (5015684) from All Windows feature updates.
3) Windows Update for Business policies not configured in SCCM
Still is there any chance for updates to go from SCCM? Please advise
Note: Windows Update for Business policies configured via GP0 with 180 days deferral

By: Sam

Sam

Having the same problem here, PCs saying they are compliant when they are in 20h2 or 21h2

By: Duane McCullough

Duane McCullough

Hi Guys, I am getting the same issue as everyone else. Curious is there are any updates on this. My only work around is creating an ISO of Win 10 22H2 performing an inplace upgrade and sent a task sequence to perform the install. It works, but not ideal and also doesn’t work on computers not on prem.

By: Juliet Jagiella

Juliet Jagiella

22h2 is failing on half of my machines of about 5k. Logged into one machine and stuck at 0% downloading. Reinstalled client with no luck.

By: Oleg

Oleg

Sorry for my preview question. Fixed by adding suppress reboot.

By: Oleg Pro

Oleg Pro

Thanks, Prajwal. I remember when I did push the upgrade to 21H2 it didn’t force the reboot, instead it was just waiting for the next reboot and this way I was able to upgrade silently all workstations. Not sure if there is any changes or I’m missing something. Is there a way to force the install, but not force the reboot?
Much appreciated thanks.

By: Jeff

Jeff

Thank You for this information. Very helpful

By: Irwin

Irwin

TargetReleaseVersionInfoI have the same scenario with you all. I wonder why my build 19044 version 21H2 devices are detected as compliant when I force install 19045 22H2 enablement package, so it wont gonna install. I noticed it too from 19042 (20H2) and 19043 (21H1) devices.

By: Irwin

Irwin

is TargetReleaseVersionInfo the culprit? Maybe not? Others are able to upgrade tho