Botched feature update, botched cumulative update

Oct 12, 2018 04:29 GMT  ·  By  ·  Comment  · 
Share:             
Patch Tuesday updates causing BSODs on HP systems
   Patch Tuesday updates causing BSODs on HP systems

UPDATE, October 13: Microsoft confirmed the bug in Windows 10 version 1803 and 1809, and the company also provided a fix. Original story below.

The nightmare never ends: after releasing and pulling Windows 10 October 2018 Update (version 1809) due to critical bugs, Microsoft has now shipped a cumulative update that causes BSODs on specific computers.

Windows 10 cumulative update KB4464330 for version 1809, as well as cumulative update KB4462919 for the April Update (version 1803), are both pushing a number of HP systems into a BSOD loop, with no easy method to go back to a functional desktop.

Microsoft has already acknowledged the bug and said it is working with HP on delivering a fix, but oddly enough, the KB pages of the two updates haven’t been updated with information on this issue.

Both KB4464330 and KB4462919 are said to cause no issues on Windows 10 devices, according to Microsoft’s official update pages, though it’s pretty clear this is not the case.

Also hitting April 2018 Update

Users who posted in this Microsoft Community forums thread claim many of their HP systems have been impacted by the issue after installing the October 2018 Patch Tuesday updates.

“I wonder how many sysadmins and tech support folks are wasting hours dealing with this issue. I've got over 100 HP machines and I've been spending the last two days dealing with this. Maybe we should be thinking about sending MS the bill!” one user posted on the forums.

While only a limited number of Windows 10 version 1809 are likely affected by the problem, mostly because this particular OS version has been pulled shortly after its launch, the bug also exists on April 2018 Update, which right now runs on nearly 90 percent of all Windows 10 devices out there.

Microsoft hasn’t provided any other information on a potential fix and an ETA isn’t available, though it goes without saying the company should be working around the clock to ship it as soon as possible. For the time being, removing the botched updates seems to be the only way to go.

Via BC

  Click to load comments
This enables Disqus, Inc. to process some of your data. Disqus privacy policy

Related Stories

Fresh Reviews

Latest News