Update to 21H1 vanished from WU

Try the Windows Update reset. I already did it worked for me. Do it several times following if you want.


Reset Windows Update in Windows 10

itsme1 said:

Try the Windows Update reset. I already did it worked for me. Do it several times following if you want.


Reset Windows Update in Windows 10

I was looking at that script before - I found another problem where reset was suggested but instead installing 21H1 directly from Catalog was chosen.
Going through the script it looks like a voodoo, while I was hoping to get a simpler and possibly solution I can understand.
If I decide to use it, why should I run it several times?
Anyway, thanks for the suggestion!

Berton said:

Further down in that page is the choice.

Found it but am currently not trying to install any update via other means but WU. So basically I will have to wait for another update released to Windows Update channel and see if my Windows picks it up. If yes, then 21H1 may have been blocked for some compatibility reasons. If not, then my WU is definitely broken and needs some serious repair.


EDIT: Just as I posted this, I checked WU and it installed CU KB5004945...

Andy Roid said:

EDIT: Just as I posted this, I checked WU and it installed CU KB5004945...

Good, that is the most recent update from official history -
https://support.microsoft.com/en-us/...2-f7f86728a6e3

If you now want to advance to 21H1, just install this tiny enablement package,KB5000736 from post 1 and in a few minutes you'll have it with the same Build as your current 20H2. You already have the most recent SSU mentioned -
KB5000736 Featured update Windows 10 version 21H1 enablement package

Andy Roid said:

I was looking at that script before - I found another problem where reset was suggested but instead installing 21H1 directly from Catalog was chosen.
Going through the script it looks like a voodoo, while I was hoping to get a simpler and possibly solution I can understand.
If I decide to use it, why should I run it several times?
Anyway, thanks for the suggestion!

My windows update was in a search loop after doing a windows update, I believe I solved it by doing the script multiple times.There is nothing complicated, you follow the instructions to launch the script, the rest is done automatically.

Download the script-> copy / paste it on the desktop-> right click on the file-> choose property-> at the bottom right of the window select "unlocked" and click "apply" and "ok" -> right click on the file and choose "run as administrator"

Bree said:

Everyone get's this one. It's an out of band security fix and is non-optional.

I wanted to see if I will get KB5004945. I did but want that I didn't to have something (in this case WU) to blame. Why is 21H1 update different from that CU from WU standpoint?

mrgeek said:

If you now want to advance to 21H1, just install this tiny enablement package,KB5000736 from post 1 and in a few minutes you'll have it with the same Build as your current 20H2. You already have the most recent SSU mentioned

I know, but I'm trying to solve several problems and one is WU. It just cracks me that there is no official real solution but toy "troubleshooter" that always says "no problems found". I wonder why is that enablement package hidden on Catalog and not offered through it like 1909 was? I guess people snooped the network to get the link.

Paul Black said:

Hello @Andy Roid,

Hello @Paul Black

Paul Black said:

You could try this FIRST => Reset Windows Update in Windows 10

That's the part I'm unsure of. My WU sees several antivirus/antimalware updates per day, CUs but not feature update.

Paul Black said:

. . . and if you wanted to STAY on v1909, then this would work . . .

> How to Specify Target Feature Update Version in Windows 10

If I only knew this earlier, I would update to 21H1 (instead to 20H2 on April 20, one month before 21H1 was released).

itsme1 said:

There is nothing complicated, you follow the instructions to launch the script, the rest is done automatically.

Download the script-> copy / paste it on the desktop-> right click on the file-> choose property-> at the bottom right of the window select "unlocked" and click "apply" and "ok" -> right click on the file and choose "run as administrator"

It's not about how to run the script and deblock it but what the script does and if it can do even more harm. Your problem was WU stuck in loop, i migh have safeguard hold in place.
When I see something like "D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)" I start to wander...

Anyway, today I got CU KB5004237:


So my WU downloaded 3 updates, but it doesn't see feature update. I was digging a little and found this docs article talking about safeguard holds. It says if there is a hold for longer time, then WU displays info that the feature will be available soon, like this:

But I don't have either update nor the info so I still don't know if this is a server side or my WU side problem.
I did SFC and DISM checks along with cleaning component store (4 claimable packages found) but it changed nothing.

-SIGH-

Andy Roid said:

It's not about how to run the script and deblock it but what the script does and if it can do even more harm. Your problem was WU stuck in loop, i migh have safeguard hold in place.
When I see something like "D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)" I start to wander...

I haven't had anything broken with this sript, I have used it several times.

Andy Roid said:

If I may ask, which update will bring you to 1082 and is it from Catalog or Windows Update?
Thanks for the feedback! My WU window looked like yours, except it didn't have "View optional updates" just above the 21H1 update.

I've got another physical PC running 2004 that I checked, and it is offering 21H1.
So basically, it seems my WU is broken... and usually there is no simple remedy for that. The troubleshooter said all is OK, SFC and DISM scanning doesn't find problems.

- - - Updated - - -

I noticed WaasMedic Agent was active on each boot while I had this update offered, but not any more since the update is gone.

Don't assume WU is "broken". I was offered 21H1 on all but two of my computers. Used the enablement package but had a problem with one computer later so sys restore put it back on 20H2 and again no 21H1 is being offered.