KB5005568 and wsus

[ticktock]

Hi

 

KB5005568 is the 2021-09 ltsc update. For some reason it hasn't downloaded to wsus which is odd. Everything has been ok up to now. I have windows 10 ticked in wsus and all the other 2021-09 updates have downloaded ok except this one.

 

https://support.microsoft.com/en-us/topic/september-14-2021-kb5005568-os-build-17763-2183-d19b2778-204a-4c09-a0c3-23dc28d5deac

 

I was wondering if anyone else had the same.

 

Thanks in advance.

[Koldov]

I created an 'Update View' called Windows 10, which includes 'Windows 10' and 'Windows 10 LTSB' and it appears for me.

 

 

In the detailed status for that update it is in the Classification 'Security' and Product 'Windows 10 LTSB'.

 

 

Are you set to receive updates for Windows 10 LTSB in your 'Products and Classifications' options?

 

[ticktock]

Thanks for the reply @Koldov, much appreciated. I haven't got LTSB ticked just windows 10 which has always downloaded them before. I'll give it a try.

[ticktock]

That worked. Big thanks again @Koldov. Enjoy the weekend.

[Koldov]

No worries, you too!

 

Just out of interest I looked at the Products section for the last few CUs and...

 

2021-09 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5005568) - Products = Windows 10 LTSB

2021-08 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5005030) - Products = Windows 10, Windows 10 LTSB

2021-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5004244) - Products = Windows 10, Windows 10 LTSB

2021-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5004947) - Products = Windows 10 LTSB, Windows 10

 

So it seems that this last update has dropped the Windows 10 'Product' identification and is just for LTSB (LTSC) maybe because 1809 pleb version is EOL now?

[ticktock]

Ah that would make sense. That could catch quite a few people out. Hopefully they will see this thread.

[sigma]

Tread carefully: https://www.bleepingcomputer.com/news/security/new-windows-security-updates-break-network-printing/

 

Includes KB5005568

[Koldov]

Hmmmm... so 1809 = LTSC = Server 2019?

 

Does it seems to suggest that 1809/LTSC 'clients' get the printing problem with this update, or is it only when you install it on 'Server 2019' Print servers it causes an issue?

 

This is all getting proper confusing now as if it wasn't bad enough already...

 

Full list of affected KB's from another post:

 

http://www.edugeek.net/forums/windows-10/223374-printing-issues-driver-update-needed-11.html#post1917676

[sigma]

Unless there is an urgent need to patch, I always delay for two or three weeks until others have beta tested..... and then miss some out if the risk of service dissruption is greater than the risk of not installing (based on available evidence).

[Koldov]

Yeah, I'm not one to jump in too quickly myself on updating anything.

 

However, workstation clients are set in WSUS to get updates ASAP, with 'Automatic Approvals' on 'Critical' and 'Security' updates (although I might revisit this now) - Servers, SIMS and that sort of thing get left until I HAVE to do it.

 

Never mind, this will all be fixed in Windows 11...

[sigma]

Sad, but I manually approve everything. I've seen to many bad updates break things over the years. Desktops get everything in one go, laptop updates get dribbled out one at a time hopefully so that nobody notices with the exception of staff latops that get them all in one go and forced reboots as otherwise they don't.

[ticktock]

I've had this on one W10 pro machine today. "The user" preference item in the" Group Policy Object did not apply because it failed with error code '0x8007011b' This error was suppressed." all other machines seemed ok, a mixture of W10 education 20H2, LTSC and Pro 20H2. The machine in question was out of date (which I hadn't realised) and was on 1803 Pro. I'm going to update it on Friday and see if the printer will then install. It wouldn't let me install directly from the print server either, came up with another error as the article above posted by @sigma

[ticktock]

I've had this on one W10 pro machine today. "The user" preference item in the" Group Policy Object did not apply because it failed with error code '0x8007011b' This error was suppressed." all other machines seemed ok, a mixture of W10 education 20H2, LTSC and Pro 20H2. The machine in question was out of date (which I hadn't realised) and was on 1803 Pro. I'm going to update it on Friday and see if the printer will then install. It wouldn't let me install directly from the print server either, came up with another error as the article above posted by @sigma

I updated the above to 20H2 and printing is now working.