There'southward a rash of WDF_VIOLATION blue screens on Win10 HP computers with an as-yet unknown cause

Fingers indicate to the Patch Tuesday Win10 cumulative updates, a Windows-pushed HP keyboard driver, or a combination of both. A Microsoft agent says that information technology'due south not only on HP machines and that the cumulative updates take been pulled, but there'due south no confirmation. Whodunit?

It'south been a wild Thursday morning in patch country, with lots of BSODs to become around, cumulative updates, keyboard drivers, and a cast of suspects worthy of an Agatha Christie novel.

Start with a comprehensive report on the Microsoft Answers forum , where poster Mikael Sillman says:

Afterward installing KB4464330 (build 17763.55) [on] 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 trouble 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:

MS Agent: Actually HP computers are non the simply product afflicted for this effect other computers too similar DELL etc. That's why for now, nosotros've temporarily paused the update for people who seek to bank check for updates, to investigate an isolated reported issue and will go far 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 also but our college level of support already working on it

To round out the clarification, the reference to Bleepingcomputer points to a serial of comments that first with confuishus:

KB4462919 BSOD's all HP workstations we tested on so far. Cant exercise system restore, recovery point, etc. Have to re-image. Dont kick this out until it gets revised or you fully exam. All BSOD shows Stop Code: WDF VIOLATION.

Followed by this comment from goddo:

Problem fixed for us, we had to delete the HP driver "HpqKbFiltr.sys" in order to avoid the WDF VIOLATION on every kicking. All the machines that were affected are now running fine for us after removing that driver.

And then this, later, from goddo:

It is non the KB4462919 update that is causing this crash at all, it is the failed install of the "HP Development Company, L.P. - Keyboard -seven/11/2018 12:00:00 AM - 11.0.3.one" in Windows update. Before this update the HpqKbFiltr.sys commuter does non exist. So in our scenario it is safe to install KB4462919 on these machines. This may non be the case for all merely I idea I should permit you guys know.

On AskWoody, an anonymous poster says:

I don't think it's KB4464330 doing this, rather I noticed yesterday that Windows Update pushed down a PS/2 keyboard driver to my HP ProBook 430 G4. This includes the HpqKbFiltr.sys file. The device name in Device Director now says "Standard 101/102 Fundamental or Microsoft Natural PS/2 keyboard for HP Hotkey Support". I already had the hotkey commuter installed merely it didn't do this.

Oh the joys of forced driver updates!

From a different anonymous poster:

We have a load of HP 800 EliteDesk G1 and HP 400 ProDesk G2, three and 4, all on win10 edu 1803, showing the wdf bluescreen then going to a winpeshl.ini file error on the second restart. We believe this is due to KB 4462919 (removing this and restarting does not lead to the BSODs)

Windows Latest has links to more reported problems. (Thx, aW.)

Several people, on multiple forums, report that they're hitting blue screens, simply can't observe the referenced file, HpqKbFiltr.sys.

As far as I tin tell, the written report from the Microsoft agent is right in that the problem may involve more than only HP computers. Just if Microsoft has pulled whatever of the Patch Tuesday patches, information technology sure hasn't appear it anywhere. I as well can't find corroboration from any Microsoft source that "HP computers are non the only product affected for this issue other computers every bit well similar DELL etc"

My best gauge: There'south a disharmonize between the new "Standard 101/102 Central or Microsoft Natural PS/2 keyboard for HP Hotkey Support" keyboard driver and both the Win10 1803 and 1809 cumulative updates. Removing either the commuter or the cumulative update resolves the problem. Only that's but a approximate.

Is it Mrs. Hubbard? Linda Arden? Monsieur Bouc? Dr. Constantine? Or are they all conspiring to kill the Win10 Ratchett?

Best to refrain from applying patches — cumulative updates, Windows-pushed drivers, waxed mustaches — until we get a clearer picture show. My little gray cells need a break.

We're still on MS-DEFCON 1 on the AskWoody Lounge .

Copyright © 2022 IDG Communications, Inc.