Server Fault is a question and answer site for system and network administrators. 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

I'm running Windows Server 2008 R2 x64 and I have a driver that isn't signed so the Device Manager displays the following message:

"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"

I know that I can disable driver signing enforcement per-boot by using F8 but I'd like something more permanent, or I'd like a way to sign this driver myself and allow Windows to accept it.

share|improve this question

Microsoft has some information on Signing Drivers during Development and Test (Windows Vista and Later). Self-signing the driver would be preferred to disabling signature verification globally.

share|improve this answer

I had to upgrade an N54L BCM,

Driver Signature Enforcement Overrider 1.3b

share|improve this answer

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.