More Windows 10 October update woes? HP users report BSOD after Tuesday patch

[nir]

Admins struggle with the latest Windows 10 1809 patch on some HP systems.

 

The cumulative update for the few PCs that moved to Windows 10 version 1809 before Microsoft halted its rollout is causing BSOD errors on some HP machines.

 

The suspected cause of blue screen of death, BSOD, errors on numerous HP PCs is the update KB4464330 for Windows 10 version 1809, which fixed an error that deleted user profiles, and carried Microsoft's October Patch Tuesday security updates.

 

Microsoft currently lists no known issues with this build but, as spotted by Windows Latest, several HP users and admins managing HP machines are reporting BSOD problems after installing the update.

 

The affected machines are reporting an error called 'WDF_Violation', referring to the Windows Driver Framework.

 

"KB4462919 BSODs all HP workstations we tested on so far. Can't do system restore, recovery point, etc. Have to reimage. Don't kick this out until it gets revised or you fully test. All BSOD shows Stop Code: WDF VIOLATION," wrote one user on BleepingComputer.

 

Other HP users have reported the same issue on Microsoft's community forum.

 

According to one HP user who claims to have been affected, deleting an HP driver called 'HpqKbFiltr.sys' successfully resolved the WDF Violation.

 

But other HP users on Reddit report that either that driver isn't present on their system, or that deleting it doesn't actually resolve the issue.

 

The BSOD problems don't appear to be widespread but they come as Microsoft faces criticism not just over the botched rollout of Windows 10 version 1809, but also Windows 10 Home users having to contend with major feature rollouts -- and their glitches -- twice a year.

 

"Microsoft needs to step off the new feature train, at least temporarily, and get Windows 10's reliability and fundamentals back on track," writes ZDNet's Mary Jo Foley.

 

Making matters worse, several Windows Insider testers reported the same issue months before the rollout. To minimize the chances of missing low-volume reports, Microsoft this week tweaked its Feedback Hub, so that users can now report the severity of the issue their facing.

 

Source

[steven36]

Only people that have Windows 10 1809  were update seekers and people who installed it themselves ..  And  from what i read at the post at reddit.com  that this is a problem  of HP  and there drivers not Microsoft. witch i'm inclined to believe because  if it were Windows 10 problem it would be happening to more PCs than just  a few kinds of HPs. Sooner or latter if they keep adding new features to Windows 10.. it's going end up like what happen on Mac OS 10 before and most old hardware will become incompatible .

 

Quote

 

R1PLEY 1 point 2 hours ago 

We have manually installed every update except for the HP keyboard driver one without issue. Then when we install the HP driver update and reboot, BSOD. I am fairly confident this one is on HP, not Microsoft. With that said, if you have a way of blocking that update, I'd say go for that. I can't make any guarantees that you will see the same thing we did, but the file never showed up until after install and reboot for us.

 

 

 

Quote

 

R1PLEY 1 point an hour ago 

To be honest I'm not sure if this is affecting HP laptops or just the G3/G4 desktops. It's too new of an issue to have much documentation out there, and I don't understand it will enough myself to give you a confident answer. If it were me, I'd probably block the update for now and email HP support with all of the information you have and your concerns.

 

 

 

 

Quote

 

Molly2925 1 point an hour ago 

Alrighty. If i block the failed driver update, would my laptop be safe to restart & download the Windows update? I'm wondering since, ever since I downloaded the Creators Update, I've had this unsolvable memory issue where the commit slowly goes up regardless of what's running and eventually I'm forced to restart or risk losing data due to memory loss, and that limit is fast approaching. Still, really, thank you for all the help, and just responding to my questions about the issue.

 

 

Quote

 

R1PLEY 1 point an hour ago 

I have not seen any issues with the current MS updates. I would say you are safe, but I do not work for MS or HP. Here are some links discussing the most recent patches:

https://www.bleepingcomputer.com/news/microsoft/windows-10-kb4464330-kb4462919-and-kb4462918-cumulative-updates-released/

https://www.reddit.com/r/sysadmin/comments/9mff3k/patch_tuesday_megathread_20181009/

As for your memory issue - make sure you are on one of the latest Win10 builds if possible. 1803 seems to be stable. Update your drivers. Especially in drivers related to networking (NIC, "bandwidth control", etc.), your chipset/CPU, and SATA controller. If it still does, boot into safe mode and see if it happens. Maybe try an SFC scan and chkdsk. Good luck

 

 

Quote

 

Evernight2021 48 minutes ago 

Blocking it won't do much good if it's already pending install. If you get the BSOD and rename the file so the update doesn't reinstall itself afterwards.

 

https://old.reddit.com/r/Windows10/comments/9n0bkw/one_of_these_quality_updates_can_cause_an/e7kjogn/

This seems to to be a botched driver update from HP .. bad drivers by vendors have haunted  Windows 10 since it was 1st released in 2015 TH1 on My AMD PC  they gave me a bad driver and I had to fix it myself by installing some beta drivers and  it didn't get fixed tell TH2.

 

You can disable driver updates in Windows 10  as i use to have to do it.  the best would be  disable the driver updates  and reset windows updates so the update would no longer be pending. 👽

 

Quote

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

 

(create WindowsUpdate key if it doesn't exist by right-clicking Windows -> New -> Key), create new DWORD value ExcludeWUDriversInQualityUpdate and set it to 1. 

 

O&O Shutup  can do this for you even.

 

How to Reset Windows Update in Windows 10

https://www.tenforums.com/tutorials/24742-reset-windows-update-windows-10-a.html

 

You can also use  wushowhide.cab and  hide any pending update before you reset updates

https://support.microsoft.com/en-us/kb/3073930

 

 

As far as if you already installed the driver ,  if Restore don't work . you need to remove the update from device manger and it should be a generic one there you can add or a older one.

[Karlston]

Woody's take...

 

There’s a rash of WDF_VIOLATION blue screens on Win10 HP computers with an as-yet unknown cause (Computerworld - Woody Leonhard)

[banned]

Windows 10 does not get the honor of the term Blue Screen of Death. It is more like Fuzzy Playtoy of Unhappiness. Show me memory addresses, don't give me frowny faces and tell me to do a google search...

[neeraj]

On 10/12/2018 at 2:34 AM, banned said:

Windows 10 does not get the honor of the term Blue Screen of Death. It is more like Fuzzy Playtoy of Unhappiness. Show me memory addresses, don't give me frowny faces and tell me to do a google search...

And this! 😂

[steven36]

So far there is been no bug been found  in the  cumulative update , its all been separate 3 party driver updates that caused  it  ,Microsoft has a fix for both drivers and there no longer on Windows updates . Once you get your drivers working on Windows 10 its best to disable 3rd party driver updates when you 1st set it up and only use 3rd party drivers you downloaded  and tested  to work . 

 

Like my AMD PC  I use to have a problem with Windows 10  with the display driver and I had use a beta driver , they fixed that in TH2  ..But now if i install Windows 8.1 they give me the wrong  display driver before they fixed in it in Windows 10 it worked in Windows 8.1 before now it don't .. I guess they broke it so people would install windows 10, . So i I have to  hide it  and use older drivers  that i downloaded.   Now I just use Linux on  that PC .

 

i got tired of having to use outdated drivers because of vendors  dropping support for PCs right after Windows 10 came out  . My display driver for Linux is built in the Linux  kernel and gets updated with that. Even the fixed Windows 10  ones for my PC that is on Windows updates has not been updated since 2015.  Vendors drop support for PCs  and cause Windows to more of  a security risk than it  all ready is and Microsoft pushes these outdated drivers on auto updates.

 

My AMD PC came with Windows 8 and  AMD drop updates for it as soon as they got it working  for Windows 10 in 2015 and Broke it on Windows 8.1 tell this day.  It took AMD a year to get good open source drivers in the Linux Kernel so i could use the latest version of Ubuntu Linux . I was stuck on Linux Mint 17.3 and Manjaro  Linux  with closed source  AMD drivers tell Ubuntu 16.04.4  came out that was like a whole year . No way i would use Manjaro now every time  i read about it and update has broke someones PC.  its like using Windows 10.. 

 

Now my Intel PC still get driver updates on Widows but I have to be careful not  to install a bad one and Windows update will force install them so I don't use that.

[erp-ster0]

5 hours ago, neeraj said:

And this! 😂

 

that was removed before 1809 was RTMed

https://news.softpedia.com/news/microsoft-pulls-notification-warning-against-google-chrome-installation-522700.shtml

[neeraj]

2 hours ago, erp-ster0 said:

 

that was removed before 1809 was RTMed

https://news.softpedia.com/news/microsoft-pulls-notification-warning-against-google-chrome-installation-522700.shtml

This was not the specific warning that caused quite a stir in 1809 beta. The above screenshot is from my own Windows 10 installation last year around same time!!!. This was displayed on the browser itself as "Ads by microsoft".