-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Archived Topics
- Unanswered Topics - Notebook
- HP Protect DLL unsigned? (virtualbox hardening issue)

Create an account on the HP Community to personalize your profile and ask a question

10-14-2020 09:18 AM
I had installed VirtualBox which was working fine. Then installed HP security tools. VBox now refuses to start with the following message in its VBoxHardening.log
2160.4ab4: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -23021 (0xffffa613)) on \Device\HarddiskVolume3\Program Files\HP\HP ProtectTools Security Manager\Bin\DpOFeedb.dll [lacks WinVerifyTrust]
2160.4ab4: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -23021 (0xffffa613)) on \Device\HarddiskVolume3\Program Files\HP\HP ProtectTools Security Manager\Bin\DpOFeedb.dll [lacks WinVerifyTrust]
2160.4ab4: Error (rc=0):
2160.4ab4: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -23021 (0xffffa613) fImage=1 fProtect=0x0 fAccess=0x0 cHits=128 \Device\HarddiskVolume3\Program Files\HP\HP ProtectTools Security Manager\Bin\DpOFeedb.dll
2160.4ab4: Error (rc=0):
2160.4ab4: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files\HP\HP ProtectTools Security Manager\Bin\DpoFeedb.dll' (C:\Program Files\HP\HP ProtectTools Security Manager\Bin\DpoFeedb.dll): rcNt=0xc0000190
2160.4ab4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\Program Files\HP\HP ProtectTools Security Manager\Bin\DpoFeedb.dll'
2160.4ab4: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -23021 (0xffffa613)) on \Device\HarddiskVolume3\Program Files\HP\HP ProtectTools Security Manager\Bin\DpOFeedb.dll [lacks WinVerifyTrust]
t]
More info on the hardening process is at https://forums.virtualbox.org/viewtopic.php?f=25&t=82106. It seems to imply VBox thinks that this DLL isn't signed properly. This would be quite weird for a security tool of course.
I probably will need to remove the HP ProtectTools, but that doesn't seem to be trivial (and is also a pity). Anyone knows more about this?
