Windows 10: SIGVERIF un-signed digital drivers.

Hello,i need some help with these 3 .dll files.I cant manage to get them signed and verified no matter what i do. I uninstalled every version of Visual C++ c++ redistributable and sony studio, reinstalled them, restarted my pc but no matter what i try i still cant manage to get them signed. Any help regarding this issue please? windows is up to date i think

:)

 

Getting "a digitally signed driver is required"

Hi Thomas,

This error can occur if there is a driver attempting to be installed on the system that was not signed by Microsoft digitally. Driver digital signatures help verify the integrity of the driver packages. To avoid this error, you need to disable the driver
signature enforcement. Follow the steps below:

• Press and hold the Shift key then click Restart button.
• Choose Troubleshoot, then select Advanced options.
  
• Select Startup Settings and click Restart.
  
• Once the computer restarts, you'll see a list of options. Press F7 to select
  Disable driver signature.
• Computer will now restart. Once done, check if the same error will occur.

Let us know the outcome so we can provide further assistance.

 

Drivers Not Digitally Signed After Latest Windows 7 Update

It's easy to see signed Windows Drivers/WHQL stamp,simply go to run,type: SigVerif

run the utility....

 

HxTsr.exe without any digital signature ???? really .. an official Microsoft tool part of the Office365 suite

hello Smittychat,

Thanks for taking the time to reply.

While your are offering steps i do not believe those are relevant. Indeed you are pointing at issues with 'drivers' being digitally signed and showing as not signed:https://support.microsoft.com/en-us...itally-signed-device-manager-displays-a-not-d

While my problem is rather with a application file: HxTsr.exe ...not a driver; or not as far as i can tell anyways.

i have ran sigverif anyways and HxTsr.exe is not showing in the list so it does not appear to be either a driver or a system file with an expected digital signature which is exactly my issue. MSFT support states this is a file that is needed for the Office365
suite to run yet it is not digitally signed... which brings me back to fileless threats through process hollowing/zombifying.

Any core applications files on such a popular OS and set of applications that is known from such a large company should be digitally signed in this era. Any less and it is just plain carelessness and disregard for the end users that we are.