22H2 Enablement Package via MEMCM. Compliant yet still 20H2

[Gongalong]

Hi folks,

 

(Sorry, this is a mix of MEMCM and Win 10, so putting in the Win 10 forum)

 

I've followed Prajwal Desai's guide to using the 22H2 enablement package and have deployed it to a test machine that's on 20H2. I set the update to be required and not to show in software center as I just want it to be applied. I did not set restarts to be forced.

 

I checked the test machine in MEMCM 10-15 minutes later and it showed it as compliant. I went to the machine itself and it wasn't prompting for a restart and still showed as 20H2. I restarted it, still showed as 20H2.

 

Any ideas as to why it's showing as compliant and not updating?

 

Thanks

[bknaggs]

I found with my MDT deployment the enablement package on its own isn't enough.

 

I deploy 2021-08 20H2 Servicing Stack Update, 2022-05 20H2 Servicing Stack Update, 2022-11 20H2 Cumulative Update and then the 22H2 enablement package and the PCs show as running 22H2. There might be a different combination that works but this is what works for me.

[Gongalong]

Thanks.

 

I have an ADR setup to deploy critical updates, definition updates, security updates, update rollups, and updates. It doesn't deploy feature packs, service packs, tools, and upgrades. Do servicing stack/cumulative updates fall into either of those, or do they have to be picked individually and deployed?

[bknaggs]

Not sure. I'm not using MEMCM.

 

I just wanted to point out the chain of updates that got me to a PC showing it was running 22H2.

[Gongalong]

OK. Will have a search through the updates and see if they display a category. I did think it sounded all too easy...

[Gongalong]

Have managed to get a second test machine to 21H2 using that specific enablement package (I "broke" my first test machine by going into Windows Updates, which kicked off the 22H2 download). Will see if I can go straight to 22H2 from there, or whether it requires CUs/SSs. Oddly the latter don't seem to be listed with a product category, but perhaps that's because they have to be deployed manually.

[Gongalong]

Solved I think. I had to deploy the latest servicing stack and cumulative update for the relevant Win 10 version, then the enablement package works. They don't show under a category so presumably have to be deployed manually, which is how I'm doing it.

 

I want to test with one more machine, and if that's OK I will deploy to the remainder.