Windows 10: Windows 10 1809 17763.55 cumulative update BSOD WDF_VIOLATION on HP desktops.

After installing KB4464330 (build 17763.55) my HP EliteDesk 800 G3 the machine refuses to boot, ending with BSOD WPF_VIOLATION.

I was able to get the PC working again using an earlier restore point.

It seems that this problem at least HP machines:

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


I contacted MS support and was told that:

Actually HP computers are not the only product affected for this issue other computers as well like DELL etc. That's why for now, we’ve temporarily paused the update for people who seek to check for updates, to investigate an isolated reported issue and will make it available for download again once ready.
Me

Ok, so this is known issue for 17763.55 cumulative update?​

Agent
That's correct and other issue has been reported as well but our higher level of support already working on it

:)

 

Windows 10’s October 2018 Update (version 1809) Update Stuck at 42%

Windows 10 1809 is just a day old. My suggestion is to hold on till the first cumulative updates arrive.

 

Cumulative Update for Windows 10 for x64-based Systems (KB3156387) will not install

Anyone else having problems getting the Cumulative Update for Windows 10 for x64-based Systems (KB3156387) installed? This update has been failing for me & doing a failed to update after downloading & reboot, then rebooting & removing the update.

V 10.0 build 10240

 

Windows 10 Update

Well just noticed a pretty large one pop up coming in at 914MB, seems it makes some pretty serous updates.

KB3172985
https://support.microsoft.com/en-us/kb/3172985

This security update includes improvements and fixes in the functionality of Windows 10 Version 1511 and Windows Server 2016 Technical Preview 4. It also resolves the following vulnerabilities in Windows:

• 3175677 MS16-094: Security update for secure boot: July 12, 2016
• 3174060 MS16-093: Security update for Adobe Flash Player: July 12, 2016
• 3171910 MS16-092: Security update for Windows Kernel: July 12, 2016
• 3170048 MS16-091: Security update for .Net Framework: July 12, 2016
• 3171481 MS16-090: Security update for Kernel Mode Drivers: July 12, 2016
• 3170050 MS16-089: Security update for Windows secure kernel mode: July 12, 2016
• 3170005 MS16-087: Security update for the Microsoft Print Spooler: July 12, 2016
• 3169999 MS16-085: Cumulative security update for Microsoft Edge: July 12, 2016
• 3169991 MS16-084: Cumulative security update for Internet Explorer: July 12, 2016

 

Hi Mikael,

Have you any news from Microsoft?

Thanks,
Tovich

EDIT:
"goddo" has found a fix (I have not tested it yet):
Problem fixed for us, we had to delete the HP driver "HpqKbFiltr.sys" in order to avoid the WDF VIOLATION on every boot. All the machines that were affected are now running fine for us after removing that driver.
(https://www.bleepingcomputer.com/ne...4462918-cumulative-updates-released/#cid10040)

 

I can say that today 10th October two HP with W10Pro 1803 failed to boot with BSOD WDF_VIOLATION .
Seems to be something about the KB4462919, deleting HpqKbFiltr.sys doesn't fix cause this file doesn't even exist.
I'm trying to re-apply the cumulative patch of 700MB from
http://www.catalog.update.microsoft.com/Search.aspx?q=KB4462919

 

According to "goddo", the problem would not come from the update "KB4462919" but from the update "HP Development Company, L.P. - Keyboard -7/11/2018 12:00:00:00 AM - 11.0.3.1" (which causes an error when installing it).
https://www.bleepingcomputer.com/ne...4462918-cumulative-updates-released/#cid10059

 

Hello i have probably working solution, we have 150 computers with Win 10 and Model HP 600 G2.
Problem is caused by KB4462919 - not all computers are affected after this update.
And solution with deleting file: "HpqKbFiltr.sys" helped
BUT
if you open CMD from recovery or some how you have probably this path
X:\Windows\System32\
a from this path you can not see the file
now type "d:" and hit enter, you should be on drive D
now you can type
"cd Windows"
"cd System32"
"cd Drivers"
and you can rename affected file
"ren HpqKbFiltr.sys HpqKbFiltrBAD.sys"
now you exit cmd and you will TURN OFF computer, after you can turn it on and it should boot to windows normally
I dont understand why i have to use drive "D:" beacause our system is drive with letter "C:"
and maybe you have to user lowwer case