wsus updates gone missing / not showing

[mrstrong]

was checking updates on wsus using the search box under actions

searching for KB's for win 10 1809 ltsc as listed here

https://docs.microsoft.com/en-us/windows/release-health/release-information

 

For some of them search returns nothing e.g. a search for KB5007206

but I know that update was pushed out via wsus last year as I have a lot on

build 17763.2300 !

 

Also if I search for next one KB5008602 still get nothing, but

for this one (later still) KB5009557 I do get 3 returned (x86, x64 and ARM64)

 

any ideas whats going on?

 

I need to get some up to build 2300 i.e. apply KB5007206

 

Maybe I could get from Microsoft Update Catalog and re-add to wsus?

[Koldov]

KB5007206 is the November CU?

 

Are they declined and removed by a WSUS script?

 

As far as I can see KB5008602 was an out of band update not pushed through WSUS (see 'Release Channel' near the bottom of the info in the centre panel)... I also get nothing for that in my WSUS.

 

https://support.microsoft.com/en-au/topic/november-14-2021-kb5008602-os-build-17763-2305-out-of-band-8583a8a3-ebed-4829-b285-356fb5aaacd7

 

If you're sure it isn't there you should be able to add it from Microsoft Update Catalog, but any reason you don't just go straight to the latest CU that you have?

 

January 11, 2022—KB5009557 (OS Build 17763.2452)

Edited January 28, 2022 by Koldov

[mrstrong]

Yes KB5007206 is the November 9 CU, it's the last one I deployed site wide.

(after testing it didn't break printing )

 

Now you mention it I did run the Aj tek wsus script, so maybe that's removed KB5007206 ?

 

I see your point re KB5008602.

 

I'm currently testing 2022-01-11 17763.2452 KB5009557 (this is the last one that appears in my wsus)

but given all the MS / update issues of late just wanting to err on side of caution.

 

I've now got a few laptops come back onsite that are on an old build version (<2300) and printing doesn't work

on them. They are reporting "You're up to date" on the laptops.

 

I might try and add it (KB5007206 ) back.

 

Currently stopped doing updates to the servers as I can't see how to really test those updates before rolling out, open to any ideas!

[Koldov]

We run 1809 LTSC site-wide (apart from a few LTSB that I just can't get back in to upgrade)... We've had no issues with the January CU - KB5009557 update for clients (printing wise I have just about every workaround going so that possibly helps with that).

 

For the servers we run 2012R2 and I thought I was immensely clever having a 2012R2 VM on my work PC (actually I've got LTSC and LTSB clients too) and tested it did the update and came back up and both the clients could print.

 

Safe in the knowledge that it was working, I rolled it out... Next day came in to DCs rebooting, reports of VMs not starting up (from EDUGEEK) and researching on the internet found that ReFS was killed (not that I use it)...

 

How was I to know that I needed my Test Server VM to have a VM, be a DC and be using ReFS to fully test it!

 

Best bet (and my new strategy) is to wait a good week or so after the update release and ask/search on here (there's plenty of guinea pigs)...

 

Edited January 28, 2022 by Koldov