Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

enter image description here

The strange part is, a few months ago, this would application work fine without any issue. Now I get this error.

share|improve this question
Was it possibly Win 7 SP1 that changed this? – music2myear Oct 6 '11 at 15:36
It is possible the driver was signed but not timestamped. If you do that, the driver will be considered unsigned as soon as the signing key expires. Contact the driver supplier for a valid driver. – David Schwartz Oct 6 '11 at 17:26

I'd contact the application developer and make sure this is a legit mistake. Drivers that are all the sudden untrusted are a dead giveaway for malware, specifically rootkits.

If it is a legit mistake, you can reboot and hit F8 while Windows is loading up. There is an option to disable the Integrity Check that will then allow installs of unsigned drivers.

share|improve this answer
I would not suggest turning off Integrity Check. Contact the author of the driver and request a signed driver. – Ramhound Oct 6 '11 at 16:10
@Ramhound: You are just repeating the first part of my answer. . . – surfasb Oct 6 '11 at 16:13
… whilst you in turn are not reading the first part of xyr comment. ☺ – JdeBP Oct 6 '11 at 16:18
@JdeBP: Which I did? F8 + disable is a one time affair. My answer says, contact dev. His is contact dev. Maybe my English is off. . . – surfasb Oct 6 '11 at 16:26
No you clearly didn't if that's what you think xyr comment is. Read it again, starting from the first part. – JdeBP Oct 7 '11 at 5:28

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.