MS Update Causing BSOD and Startup Repair Boot Loop on HP Desktops

William Fulks
William Fulks used Ask the Experts™
on
The latest Windows 10 update has bricked a bunch of PC's at my workplace and we are scrambling to figure out the problem. We are an all HP shop and apparently this is hitting HP desktops hard. What's happening is the PC gets stuck in a startup repair loop and nothing seems to fix it. We already wiped and rebuilt 2 machines but we can't keep doing that. We're talking potentially hundreds of users affected.

I found a msg board post saying to delete an hpqKBfiltr.sys file but it does not exist on the PC's we've had problems with. This fix may be specific to certain model HP desktops. I am going to try manually backing out the last couple of updates via command prompt but I am hoping somebody here has run into this and resolved it already. Message boards have been blowing up since yesterday about this.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Distinguished Expert 2018

Commented:
And how did you check the presence of that file hpqKBfiltr.sys to say for sure it's not there?
What's the bluescreen messge before the reboot loop starts?
William FulksSystems Analyst & Webmaster

Author

Commented:
BSOD is giving a WDF_Violation error.

The .sys file is supposed to be under c:\windows\system32\drivers.
Distinguished Expert 2018

Commented:
Let me ask again: how did you verify the presence on your non-booting system? Because the drive letter might be different when seen from WinPE.

WDF-Violation is expected for this HP-exclusive error, so it would fit.
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

William FulksSystems Analyst & Webmaster

Author

Commented:
In the repair command prompt it defaults to X:, so I change it to c: and check the users folder to make sue my user's data is at least still there. Then I go to Windows System32 Drivers and look for the file. Should I be looking elsewhere?
Distinguished Expert 2018

Commented:
How do you do that check exactly? That is a hidden system file.
William FulksSystems Analyst & Webmaster

Author

Commented:
I have run Dir /A:H and other variations to show hidden files, system files, etc. It's not there.

Here's the latest news on this - no fix yet for people who don't have the file - https://www.bleepingcomputer.com/news/microsoft/hp-pcs-getting-wdf-violation-bsod-after-installing-windows-10-updates/
Distinguished Expert 2018

Commented:
Sorry William, I thought it was worth double checking.
Was safe mode tried?
William FulksSystems Analyst & Webmaster

Author

Commented:
Yes and it doesn't work.

Commented:
Are the PCs bricking creating memory dumps?  If so, search for *.DMP files and then open them in BlueScreenView: https://www.nirsoft.net/utils/blue_screen_view.html.  It will unwind the stack and give you a best guess what driver/process caused the crash.
Distinguished Expert 2018

Commented:
That's a good idea.
Additionally, you could take a machine and try an offline repair from the repair environment:
https://www.experts-exchange.com/questions/29061891/windows-10-repair-fails.html#a42330877 describes it. It takes the setup files from a usb stick as source.
JohnBusiness Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018

Commented:
It does not help, but this issue made the news:

https://www.zdnet.com/article/more-windows-10-october-update-woes-hp-users-report-bsod-after-tuesday-patch/?ftag=TRE-03-10aaa6b&bhid=23164040498209351948461508422926

The people in this article had to re-image. Nasty.

Have you gone to HP Support (I assume yes). What do they say?
William FulksSystems Analyst & Webmaster

Author

Commented:
John, I have seen that. News stories are hitting other sites now. HP hasn't offered an official solution yet. We are on standby because I really don't want to have to re-image a dozen machines.
JohnBusiness Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018

Commented:
Yes I understand about the nasty re-imaging issue just for this. I am amazed HP has not offered a solution. I will keep watching
JohnBusiness Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018

Commented:
Here is an HP article that has a number of suggestions, but no outright solution.

https://support.hp.com/us-en/topic/windows-10-support-center-computing

Can you start one of the problem machines with a USB Key or CD and update the BIOS and Chipset. BIOS updates have been needed in 2018 so it is worth a try if you can do the update.
William FulksSystems Analyst & Webmaster

Author

Commented:
Microsoft has put out some patches but there's no way to install them unless you can get into the GUI, which defeats the purpose. I am still in that category of the file not being there. I will wait a couple more days to see if this ever gets fully resolved.

On a side note, we've rebuilt a half dozen PC's before lunch.
JohnBusiness Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018

Commented:
True about the patches.  Did you try BIOS / Chipset updates to see?
Distinguished Expert 2018

Commented:
So far you gave no feedback on my simple instructions for an offline repair - did you try them?
Here again:
you could take a machine and try an offline repair from the repair environment:
https://www.experts-exchange.com/questions/29061891/windows-10-repair-fails.html#a42330877 describes it. It takes the setup files from a usb stick as source.
JohnBusiness Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018

Commented:
Here is a new Article from Microsoft about this. It may be a keyboard driver. I know you cannot start the machines (some of them anyway).  But see if this helps you.

https://www.zdnet.com/article/windows-10-bsod-problems-microsoft-offers-up-driver-fix-for-hp-crashes/?ftag=TRE-03-10aaa6b&bhid=23164040498209351948461508422926
William FulksSystems Analyst & Webmaster

Author

Commented:
McKnife, sorry for not responding but we did try the DISM offline repair and it gave some kind of error. I forget what exactly.

Because of time constraints, we had so many computers down that we stopped searching for solutions and just re-imaged them. That process only took about an hour so we went that way.

As for the solutions from Microsoft, they keep pointing to that .sys file that isn't present on our machines. We fall into that sub-category of this where people are getting wdf_violation but don't see the files TO delete that they say will fix the problem.
Systems Analyst & Webmaster
Commented:
Solution was to re-image the computer to get the user back working, rather than wait on Microsoft/HP to issue a fix. Nothing we tried worked, even official "fixes" from Microsoft. We had more than a dozen computers affected, and of course half of them were department managers and other positions who simply could not go without a PC for more than a day.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial