Fix for HP’s 3D Drive Guard-Bug after Microsoft Patchday

[German]Since Microsoft’s September 2017 patch day there is a second problem on HP systems with Windows 10 version 1703 (besides the black screen bug). The HP 3D Drive Guard is no longer running correctly. Here is some information about the problem and a fix.


Advertising


In part 1 (Fix for HP’s patchday login black screen issue) of my two articles series I discussed the fix for the black screen login screen on HP computers after the September 2017 update on Windows 10 V1703. But there is a second issue with HP’s 3D Drive Guard.

HP 3D Drive Guard is broken after Update

HP 3D Drive Guard software is installed on many HP systems. This detects movements of a device, that can be dangerous for the hard disks, and moves the hard disk heads into a parked position if necessary. The Drive Guard protects the hard disk of your computer (only on notebooks).

But HP 3D Drive Guard is a kind of ‘troublemaker’, especially under Windows 10. Within this HP forum thread filter driver hpdskflt.sys is causing a blue screen with stop code 0xc0000428.

HP 3D Drive Guard

Within this HP forum thread a user mentions a missing accelerometer driver in Windows 10 device manager. I found also a German forum post dealing with the fact, that HP 3D DriveGuard was shown as an unknown device in device manager after upgrading from Windows 7/8.to Windows 10.


Advertising

This German HP forum post mentions an issue with 3D Drive Guard after installing Microsoft’s September 2017 update in Windows 10. Windows reports during each system start:

„HP Accelerometer is not supported in this version of Windows. An updated app may be available.“

It seems, that the file accelerometerdll.DLL isn’t found. Uninstalling and re-installing HP 3D Drive Guards doesn’t solved the issue.

A fix from HP

German blog reader Michael Borman (also an external expert in HP’s forum) left this comment within my German blog, linking to HP’s fix sp81920.exe. The fix should solve the HP 3D Drive Guard problem after September 2017 patch day.

I have analyzed the files in the fix (I don’t own an HP computer). The patch includes fixes for Windows 7, Windows 8.0/8.1 and Windows 10, a batch program that checks if 3D Drive Guard is present on the machine and updates the accelerometerdll.DLL file, a sys file of the same name, the HPMDPCoInst.dlls file and a hpdskflt.sys filter driver (all files are from April 28,2017). After installing this fix, HP’s 3D Drive Guard should be working again.

Articles:
Fix for HP’s patchday login black screen issue
Fix for HP’s 3D Drive Guard-Bug after Microsoft Patchday
Windows 10 V1703: Update KB4043292 for black screen bug

Similar articles:
Microsoft Office non-security updates (September 5, 2017)
More Microsoft Updates from 08/29/2017 and 09/05/2017
Microsoft September 2017 Patchday Summary
Patchday September 2017: Updates for Windows 7/8.1
Windows 10 Updates September 12, 2017
Microsoft Office Security Updates (September 12, 2017)
Update to Adobe Flash 27.0.0.130 and more
More Microsoft Updates (September 12, 2017)

 


Advertising


This entry was posted in issue, Update, Windows and tagged , , , , , . Bookmark the permalink.

One Response to Fix for HP’s 3D Drive Guard-Bug after Microsoft Patchday

  1. Mergatroid says:

    I appreciate you attempt to help, and it may be that this fix helped directly after the fall creators update in 2017, but here it is Mar 2018, and I’m doing a clean installation of Windows 10 pro to a formatted hard drive, and this driver still does not work.

    I am working on an HP ProBook 6570b, and I have tried everything to the point I’m about to give up. I have never, in the last 30 years, given anyone, especially a client, a computer with a non-installed driver, but this is going to be the first time.

    I have tried those useless driver updaters (I knew better, but I’m at my wits end), I have read tons of articles on the ‘net, I have tried updated drivers from HP’s FTP site, I have tried the driver on their webpage for this model that they say works, but doesn’t.

    I just downloaded the file you suggested (thank you for the effort), but I get the “This driver cannot be used do to compatibility issues” error after the reboot. I have literally spent about four hours of shop time just trying to find a driver for this piece of hardware, and I just can’t justify continuing on at this point. It’s just costing us too much money.

    Before I go, mind if I rant a bit? I have really had it with companies like Microsoft and HP. I don’t care if they want to blame each other or not. In my opinion, it’s both their faults. HP must have had an advanced copy of this update before Microsoft rolled it out to the public, and I just can’t believe they didn’t notice this driver wasn’t working. And what is it with Microsoft who releases major windows updates that break drivers? What’s the big change that makes all the drivers for this device from the last 10 years fail? Microsoft wants to stop issuing new operating systems every five or so years, but this is the problem that creates. Perfectly good computers starting to fail because their updates break them. We’ve seen this happen with Windows 10 over and over and over, yet they don’t learn a lesson and do something to fix it. Previously, if a new operating system came out and it was not compatible with your hardware, you just didn’t purchase and install it, or the manufacturer would come out with new drivers. In either case, you still had a perfectly good, working computer.
    Now, Microsoft is consistently bricking computers, and causing all sorts of lesser problems, and once again it’s due to a bad decision on their part. Every time they make bad decisions, it takes years for them to finally admit is was a bad decision and correct it, and by then all the damage is already done.

    Well, unfortunately, this client is now getting a partially gimped computer back because of Microsoft and HP’s brilliant decision making skills and programming skills.

    Rant over. I feel a little bit better now….

Leave a Reply

Your email address will not be published. Required fields are marked *