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

Anonymous
2018-10-10T05:20:44+00:00

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 for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2018-10-11T18:47:25+00:00

Update 10/12/18

Please see this article.

In another article, we have resolution steps if you still experience the Blue Screen.

We’re aware of the issue and working with HP to investigate.

Paul...

Was this answer helpful?

6 people found this answer helpful.
0 comments

54 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-10-15T19:39:02+00:00

    Thanks for the help!  I started cmd with administrator rights and it took me to the sytem32 folder.  I tried seeing other volumes that might fit that description, but C: looks like it is it.  I installed that kb4462919 update last night and this morning I can't stay logged in more than a minute or so before it gives me a BSOD with a Stop Memory Management error and reboots again.  All attempts to get it to restart in safe mode or revert to an earlier date, etc. have failed.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-10-15T13:34:22+00:00

    To all of you who experienced this problem recently, did you run Windows Update and experience this BSOD problem after Friday, when Microsoft published these articles coming clean about the problem and offering a potential fix ?

    I'm under pressure to roll out Windows Updates to our HP servers and SCCM refuses to push last month's updates, which I'd like to have done considering the monumental mess Microsoft have made of October's updates.  So I'm thinking of going ahead with the October updates, but only if I'm confident that this issue no longer happens to people since Friday's changes on Windows Update.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-10-15T10:52:43+00:00

    For me, only one of four HP computers (490 series) have this file - HpqKbFiltr. And windows on start enter to recovery procedure after every reboot. sfc, dism from command promt not help there. Then after some research i made solution for me. Here is it!

    First, enter to command promt in windows RE. Then rewrite boot loader of windows, e.g. bcdboot c:\windows (where c: is your system disk, of course). Now you remove enernal cycle of  automatic repair on every boot. So we need to go deeper. Remove HpqKbFiltr if you find it. And remove in c:\windows\system32\drivers\wd two files - WdBoot.sys and WdFilter.sys. Thats all. Reboot.

    After that, then you boot to windows, you can start dism /Online /cleanup-image /restoreheath and then you can install updates and other what you want to do. 

    Hope this helps.

    Thanks Roman.  Will pass the word on as this looks like it could be very helpful.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-10-15T10:46:08+00:00

    PaulSey, Lonnie_L, Mikael Sillman, it seems that using DISM and REN in the Recovery Console is only a partial fix.  Some people are saying this isn't working for them and they may not have this keyboard driver file.  Therefore, could you please remove 'marked as answer' from PaulSey's post ?  There are signs this is not a complete solution and there may be other drivers or updates involved in the same issue.

    Was this answer helpful?

    0 comments