MageJubi Posted October 8, 2009 Share Posted October 8, 2009 BT848.sys is a widely used video capture driver that's not signed, and disliked by Win7 x64. Having no interest in doing the F8 routine, I decided to sign it using SDK 6.1 for Win 7. Now, the driver says it's signed, and the certificate says "digital signature ok". I used a command line "cmd.exe /c certutil -p mypassword -importpfx codesigner.pfx" to make things more automated, but when the driver wasn't accepted, I ran the .pfx file manually to import info to the Trusted Root Certification Authorities/Registry, and it's says "import successful". With all that looking ok, Win 7 still won't accept the driver. (and, yes, I did use search, but may've missed something). BTW, I tried ReadyDriverPlus (which works fine on Vista), and Driver Signature Enforcement Overrider, and both resulted in permanent BSOD's, even in safe mode. I'm sure something has been overlooked, but what? Any ideas what may be tried next? Thanks. Link to comment Share on other sites More sharing options...
karyonix Posted October 10, 2009 Share Posted October 10, 2009 - press F8, disable driver signature enforcement, boot into Windows- bcdedit /set {current} testsigning on- make sure your .sys is signed Link to comment Share on other sites More sharing options...
cluberti Posted October 10, 2009 Share Posted October 10, 2009 The previous poster is correct - to run self-signed drivers, you must be in testsigning mode. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now