It's Patch Blues-day: Bad October Windows updates trigger BSODs

Microsoft's latest fixes blamed for crashing WSUS-managed boxes during start-up

By Shaun Nichols in San Francisco

Posted in Data Centre, 12th October 2017 21:22 GMT

Microsoft's October batch of security patches and bug fixes caused some corporate PCs to suffer blue-screen-of-death crashes when starting up this week.

The Redmond software giant has fielded multiple complaints on its support forum from system administrators, who said the KB4041676 and 4041691 updates are making their machines go titsup.

Specifically, admins said that for some boxes managed by WSUS – Microsoft's Windows Server Update Services – the October patches cause the computers to halt during power up with "inaccessible boot device" errors.

Machines that are not managed through WSUS are not impacted by the issue, meaning home and small business users should not experience any problems with the October update – and are still advised to install the fixes as soon as possible in order to close up the myriad security vulnerabilities addressed.

According to IT consultant Mikael Nystrom, the boot errors are the result of a delta update package that was pushed out through WSUS in error.

"Those updates was never intended to show up in WSUS, they should be deleted or declined," Nystrom explained. "You should never have delta updates in WSUS. It was a 'whoops'."

Nystrom recommended administrators whose machines are afflicted with the bad updates, released on Tuesday, remove them using either PowerShell or the DISM app. Microsoft is pushing out fresh updates to correct the boot failures: sysadmins should clear the cache on WSUS servers to ensure the latest packages are fetched and deployed.

A spokesperson for the software giant told The Register on Thursday: “Some customers may have experienced issues in Windows Server Update Services (WSUS) deployment of KB 4041676 and KB 4041691, which has been resolved. Most customers automatically receive updates from Windows and Microsoft Update, and were not affected.”

You can find some official information on the technical cockup, and solutions to tackle the "publishing issue," right here. ®

Sign up to our NewsletterGet IT in your inbox daily


More from The Register

Windows 10 Spring Creators Update team explains the hold-up: You little BSOD!

Microsoft Windows Insider chief 'fesses up to potential blue-screen inducing glitch

Half of all Windows 10 users thought: BSOD it, let's get the latest build

April is the cruellest month – and the quickest rollout of an update in the OS's history

Well, debugger me. Microsoft's BSOD fixer is getting a makeover

Grey screen gets ribbonised

'Oi! El Reg! Stop pretending Microsoft has a BSOD monopoly!'

Your wish, dear reader, is our command. Including an Acorn BSOD. Yup, that Acorn

Microsoft Master File Table bug exploited to BSOD Windows 7, 8.1

The 1990s called: they want their filepath hack back

Going shopping for a BSOD? We've found 'em in store at M&S

PLUS: A reader spots a Timex Sinclair 1000 in the wild

CIOs planning to snub Oracle for other cloudy vendors – analyst

Drop for Big Red shares as biz prepares to announce Q4 financial results

Data shepherd Rubrik herds Microsoft, Oracle users towards its Alta

Now talks to Nutanix AHV, Microsoft Hyper-V and Oracle RMAN

Umm, Oracle – about that patch? It might not be very sticky ...

Security researcher says WebLogic fix can be bypassed, posts proof-of-concept

Oracle launches its very own 'net threat map

Pew! Pew! The whole world is connected, and the Internet is super-dangerous