Disable Driver Signing in x64 Windows Vista

An easier way is to just type "bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS" into vista's search box, and hit enter. It will open up a cmd window and enter it in itself, then close the command window... making it an easy 1 step operation

This doesn't work.
Microsoft has fixed it

I agree there is an actual need to use this. I understand the implied reasoning for not allowing un-certified drivers but there are legitimate drivers and applications that I have used for years and know to be completely safe that just because it is freeware and the authors have not gone through the trouble to have the drivers signed, it simply wont work or install. Also if smart you will use other means of security and not do stuff that would intentionally harm your machine. I am happy that there is a fix for this but as I work on other peoples machines, I wish it weren't so easy to do because some people should leave it as is so my job wont be as hard lol. Thanks for the info though this is a lifesaver!

So erm, bcdedit /set loadoptions ENABLE_INTEGRITY_CHECKS turns it back on ??

To turn it back on use: bcdedit -deletevalue loadoptions

Also, I am told that it is best to run the command prompt as an administrator or it may not work. So, try START >> PROGRAMS >> ASSESSORIES >> Right click the COMMAND PROMPT icon and choose "Run as Administrator". You can paste the text into it there.

Having said all this, it would appear that this may be plugged by Microsft as my Vista Home Premium 64-Bit w/SP1 and all updates on it doesn't work for the driver I had this problem with. I still receive the error message after the driver is installed after I ran the command prompt and restarting.

followed this thread with interest, as I have Monaco's xrite optix xr pro colorimeter and color checker for my monitor, scanner and printer in form of ez color and optix 2.0. It has worked great for me on xp pro platform using pscs4, lr2, and epson R2400. The colorimeter itself is a DTP94. Anyways, a frriend has built up a newer system for me which includes windows vista 64 bit, for which I am told ez color will not work. I was told options were color munki or eyeonedisplay2, until it was suggested that it is possible to disable the 64bit driver (in vista)? and then I would be able to use my ezcolor program. Would anyone care to elaborate what exatly I would have to do to make this happen? And, is it reversible? Thank you very much.

I tried this on my Vista Ultimate 64 and never worked. In order to have access to my sound card driver, i still need to reboot, press F8 and select to disable driver signing each time I do the reboot.
Can anyone help me?
Thanks in advance

thanks everyone for the info above. running the command line works on Vista Premium 64 bit/SP1, but it is reset on your next boot. I just created a bat file to make it easier. This is a really crazy limitation of 64 bit Vista, MS should provide a workaround for known drivers. BTB the driver giving me trouble is for a Novatel wireless card and isn't some hack, and yes I'm pissed at Novatel too.

Hello, I've tried the techniques described here for disabling driver signing. But I still can't use DVD43. I've followed the directions to the letter. I've entered the "bcdedit..." command from a cmd box running as admin and rebooted. That failed. I've rebooted, hit F8, and selected disable driver signing. That also failed. There was mention by "Tim" earlier that Windows might possibly "plug" this and defeat attempts to circumvent driver signing. Has anyone else tried these techniques on Windows Vista Home Premium SP1 - 64 bit and successfully got DVD43 to work?

The problem is still occurring, very frustrating! ive entered the correct code into command promt and it tells me success. i reboot and still the same problem >>

Shouldn't it be: bcdedit /set loadoptions DISABLE_INTEGRITY_CHECKS
without double D.

I had the same problem, and I already did like you write, with double D.But the problem is still occur. Is there another way to disable this?

>bsdedit.exe /set TESTSIGNING ON

This should solve the issue. However - be warned ... this allows all unsigned drivers to load. A better solution is to install the Windows Driver SDK and create a certificate.

However - if you are pressed for time and avoid sites that substitute "s" with a "z" and don't run untrusted setup scripts ... you should be ok.

Our colleagues on the dark side who spend their time writing rootkits will embed this command in any setup script ... to ensure they hijack a system by loading their unsigned drivers. Thus, as a side effect ... most virus checkers may complain about it.

Remember - this is a feature for "testing" and not production. A production system should go through the process of creating a certificate for the driver. This process is outlined in the Driver SDK.