- Thread Author
- #1
Hello,
Running W7, the 64 bit version.
Installed a new HD on my three yr. old HP Desktop Pavillion as old one conked out.
Used the 3 HP System Restore Disks I made when I first got the PC.
All fine after re-install, except that one program will not run now.
Messages kept coming up that a Signed Driver was Required.
Vendor says that it is most definitely a signed Driver with program.
No idea why it worked before, and now, suddenly, decides that it needs a signed driver ?
It must have had one before, I would think ? Or,...?
Have been searching Google, and it seems that this is a fairly common problem.
If I press F8 during starting, and select the option to not require signed drivers, all works fine. But, this has to be done each and every time one starts the PC.
Obviously, one really big pain.
I also did the following that was suggested, but not sure what, if anything, it accomplished.
I still have to go thru the F8 routine each time:
You type in cmd.exe, Run as Administrator, then the DOS like screen appears in which
you type:
bcdedit.exe -set loadoptions DDisable_integrity_checks
and also type in: bcdedit.exe -set testsigning on
Then, an Exit from the DOS screen, and re-start of PC
But, I guess it is only to prevent the message from appearing, not locking in the setting.
At least this seems to be the case. True ?
There are a few programs offered from folks to lock the setting that would allow "un-signed
drivers" to be used, but there are also quite a few Posts re how the use of them caused many (other) problems.
Might anyone have any suggestions as to how could I "lock" the setting that I selected via F8 that is simple to implement (I'm not too sharp with this) and very "safe" ?
Much thanks, appreciate the help,
Bob
Running W7, the 64 bit version.
Installed a new HD on my three yr. old HP Desktop Pavillion as old one conked out.
Used the 3 HP System Restore Disks I made when I first got the PC.
All fine after re-install, except that one program will not run now.
Messages kept coming up that a Signed Driver was Required.
Vendor says that it is most definitely a signed Driver with program.
No idea why it worked before, and now, suddenly, decides that it needs a signed driver ?
It must have had one before, I would think ? Or,...?
Have been searching Google, and it seems that this is a fairly common problem.
If I press F8 during starting, and select the option to not require signed drivers, all works fine. But, this has to be done each and every time one starts the PC.
Obviously, one really big pain.
I also did the following that was suggested, but not sure what, if anything, it accomplished.
I still have to go thru the F8 routine each time:
You type in cmd.exe, Run as Administrator, then the DOS like screen appears in which
you type:
bcdedit.exe -set loadoptions DDisable_integrity_checks
and also type in: bcdedit.exe -set testsigning on
Then, an Exit from the DOS screen, and re-start of PC
But, I guess it is only to prevent the message from appearing, not locking in the setting.
At least this seems to be the case. True ?
There are a few programs offered from folks to lock the setting that would allow "un-signed
drivers" to be used, but there are also quite a few Posts re how the use of them caused many (other) problems.
Might anyone have any suggestions as to how could I "lock" the setting that I selected via F8 that is simple to implement (I'm not too sharp with this) and very "safe" ?
Much thanks, appreciate the help,
Bob