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-17T13:55:48+00:00

    Unfortunately not. I've tried several times and on different machines and keep getting the same error.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2018-10-15T14:37:34+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.

    It is saying I don't have permission to delete the WdBoot.sys or WdFilter.sys and the HpqKbFiltr is not there.

    I'm hearing there may be two drives mapped to System32 in Recovery Console Command Prompt.  You may be on the default one, which sometimes shows as X: and gives access to limited system folders.  Try checking what drive represents your system volume (normally C:) using diskpart by typing list volumes.  You may find another drive which gives you access to all of your system drive and therefore might let you access these files.  Worth a try.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2018-10-11T16:37:19+00:00

    Has anyone heard any official statement from Microsoft regarding this ?  Have any updates been pulled from the Windows Update Catalogue ?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-10-10T21:50:40+00:00

    Thanks Mikael,

    I reported this problem (or at least a very similar one) here too.

    It's either just down to the three October Cumulative Updates (in my case kb4462919 for v1803) as you say, or the keyboard update in my screenshot (doesn't have a ref number) as I suspected.  Or it could be a combination of both.  Your response from Microsoft does add weight to the idea it's the CU.  

    Interestingly, if Microsoft have 'paused' these updates like they told you, they certainly haven't pulled them entirely. They're still listed in the knowledge base with "Microsoft is not currently aware of any issues with this update.", and they're also still in the Microsoft Update Catalogue.

    Thanks for letting us know anyway.  If you hear anything further, please post.

    Edit: I mixed September and October up, sorry 😳

    Was this answer helpful?

    0 comments