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-13T07:31:07+00:00

    I have the same problem ..  Damned .. I have deleted the file but it still doesnt work... I cant use my computer 😭😭😭 and now it worst i cant go on the desktop for delete the update or something else...and I have an asus...

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-10-12T23:07:25+00:00

    The Microsoft updates released on October 9th, are not the source of the 0x10D WDF_VIOLATION bugchecks on RS4 or RS5. They do not contain or update the driver in question. Instead, affected devices, primarily HP business desktop, are installing a keyboard driver update in close proximity, if not the same reboot cycle to the October 9th, 2018 updates.

    Owners of devices in reboot pending state should follow the guidance in:

    • KB 4468304: HP Devices may experience blue screen error WDF_VIOLATION after installing HP Keyboard driver (11.0.3.1)

    Devices currently experiencing the WDF_VIOLATION Bugcheck should  follow the guidance in:

    • KB 4468372: HP devices may experience blue screen error WDF_VIOLATION after installing HP keyboard driver (version 11.0.3.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-10-12T10:10:12+00:00

    Wasn't this update tested by thousands of Insiders (on machines from many different vendors)? How can they roll it out in this state?

    What I'm not sure about is whether Insiders have any involvement in testing Cumulative Updates and driver updates.  It's possible.  Maybe when they roll out an early insider Win10 build they also bung some beta drivers and updates with it too, through Windows Update ?  I really don't know.  One thing we all do know is Microsoft are no longer testing their software releases properly.  They laid off a lot of testers a few years ago and I think it may be a good idea for them to start head-hunting to get them back.

    If Microsoft don't care about their users, at least they should be concerned about the damage caused to their reputation this month.  October has been an absolute shitshow for Windows 10.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-10-12T10:00:19+00:00

    Hi Mikael

    Thanks for sharing that info. I was able to get several Systems running again by following the steps u described.

    ~Helge

    Was this answer helpful?

    0 comments No comments