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...
Windows 10 1809 17763.55 cumulative update BSOD WDF_VIOLATION on HP desktops.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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:
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.
Answer accepted by question author
Anonymous
54 additional answers
Sort by: Newest
-
Anonymous
2018-10-12T12:47:26+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:
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
But how if i in progress downloading the updates and i already pause the update (HP laptop) what should i do?
-
Anonymous
2018-10-12T11:25:15+00:00 I have over a 1000 desktops, that are affected by this issue. I hope that this will get fixed ASAP.
Microsoft need to get their act together and stop releasing buggy updates.
-
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.
-
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