October 2017 CU Issues

[free780]

https://deploymentbunny.com/2017/10/11/the-october-2017-update-inaccessible-boot-device/

 

Anyone get bit?

Obviously have a collection/target group to test before you deploy.

It does seem create nervousness with Windows as a service.

[abaxter2]

I've not seen this issue, but I do not use delta updates on my wsus, only the full CU.

 

The issue looks like it only affects systems that use wsus that have been configured to use delta updates, of course I could be wrong, but I am not seeing this issue with full CU's

[Patrick]

This is causing me massive issues! In some small schools i have admin machines pointing to county council WSUS servers. Normal practice and this is what LEA does. Seemed Ok till they pushed out this update. Cue a number of schools with downed admin machines.

[Michael]

Thanks for the heads up. I agree Full and Delta updates should have different KB numbers but they don't.

 

I have seen Delta updates 'offered' to machines previously, but then fail as they're not at the correct Patch level (one month prior). It's something Microsoft need to address.

 

To be honest, there's nothing amazing about the October update, so I plan on leaving all schools I manage on the September update for now.

[free780]

It would have only hit if you have a ADR in place.

[browolf]

This is causing me massive issues! In some small schools i have admin machines pointing to county council WSUS servers. Normal practice and this is what LEA does. Seemed Ok till they pushed out this update. Cue a number of schools with downed admin machines.

 

Our computers all point at those county wsus servers but it's only killed 3 staff laptops. We don't have much win10 stuff.

[Michael]

Sounds like they have it all set to 'Automatic Approve'. Definitely not a good idea.

[free780]

Or at least have a delay of a few days.