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 No 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 No comments

54 additional answers

Sort by: Most helpful
  1. Anonymous
    2018-10-11T04:12:10+00:00

    Hi Huddie!

    Yeah, on our case the HP keyboard driver seems to be the case. I was able to get the machines working again by:

    In recovery screen

    Advanced recovery options -> troubleshoot -> command prompt

    c:

    cd c:\windows\system32\drivers

    ren HpqKbFiltr.sys HpqKbFiltr.sys_old

    After this the machines boot normally.

    Was this answer helpful?

    50+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-10-11T15:44:00+00:00

    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

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-10-11T16:46:05+00:00

    I wonder how many sysadmins and tech support folks are wasting hours dealing with this issue.  I've got over 100 HP machines and I've been spending the last two days dealing with this.  Maybe we should be thinking about sending MS the bill!

    Was this answer helpful?

    10 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-10-12T02:35:24+00:00

    Hi Huddie!

    Yeah, on our case the HP keyboard driver seems to be the case. I was able to get the machines working again by:

    In recovery screen

    Advanced recovery options -> troubleshoot -> command prompt

    c:

    cd c:\windows\system32\drivers

    ren HpqKbFiltr.sys HpqKbFiltr.sys_old

    After this the machines boot normally.

    Hi

    I was able to use this to fix one of our HPs but the second one does not have HpqKbFiltr.sys in the C:\windows\system32\drivers directory.  Any idea if there is another file I will have to rename?

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments No comments