http://www.ngohq.com/home.php?page=dseo

Introduction Microsoft did well bringing the 64-bit architecture to Windows Vista but somehow they screwed up. Apparently they f […]
Show full quote

Introduction
Microsoft did well bringing the 64-bit architecture to Windows Vista but somehow they screwed up. Apparently they forgot who their target audience was when they introduced a very restricted module of driver signature enforcement. In laymen’s terms, all drivers and system files must be digitally verified or they cannot run when using the 64-bit version of Vista. In the past it was possible to turn that feature off; but due to new kernel security updates it is impossible to turn it off without degrading security and stability of your operating system.

In order to turn this off it involves uninstalling critical security updates that Microsoft has released to increase system security. Sadly, this feature makes Windows Vista 64-bit into a closed and locked down operation system.

So what’s the problem with digital certificates? Well, the problem is… developers have to pay Microsoft to receive verified certificates, and that makes many applications inaccessible under Windows Vista 64-bit. This driver signature enforcement can be a serious pain to end-users; however it is still possible to turn it off by disabling it up by pressing the F8 function key during system boot up.

Pressing F8 every time on boot up can be a serious pain in the ass and frustrating to those that miss the time window available to press F8 during start up. Others have found workarounds, but most of them are too complicated for the average end user to perform, atleast until now - thanks to our latest tool.

How does it work?
Microsoft is aware that developers can’t submit every beta build they are testing. Microsoft has provided a mode inside Windows Vista that will allow developers to test their software before they submit it to Microsoft’s labs. Unfortunately even in that test mode drivers and system files must have a certificate before they will install.

The good thing is that it doesn’t have to be digitally verified. This means we can load drivers by creating our own unverified certificates. Don’t worry; you don’t have to do anything as our Driver Signature Enforcement Overrider will do everything for you.

Are there any risks involved?
None! there really isn’t any risk. Our small tool will allow you load any system file, driver which driver signature enforcement is preventing us from running, without any security impact (malware cannot sign itself). Unlike other workarounds, you don’t have to mess with your boot files or remove security updates that may degrade security and stability of the Windows Vista operation system.

However, there is only a single annoyance, you will have a “Test mode” and “Windows Vista Build verbose” appears on the desktop. A good thing is that if you happen to be using the classic mode theme, it won’t be there.

So how do I use it?
First and foremost; you’re using this software at your own risk, we do not take responsibility for any damages to your system, but I don’t believe it can harm anyone in anyway. Secondly, User Account Control (UAC) must be disabled in-order to use this tool as well (but you can re-enable it after).

1. Go ahead download and launch the application from the link below. Inside its main menu, press on the “Enable Test Mode” button and follow the instructions on the screen. This will enable TESTSIGNING mode, which allows unverified system files to be loaded.

2. Now all you have to do is to add the unverified signature to the required system files. To do so press on the “Sign a System File” button from the main menu, and enter specific filename including full path. For example: if ATITool64.sys from C:\Windows\System32\drivers refuses to load due to driver signature enforcement, you should type: “C:\Windows\System32\drivers\ATITool64.sys”, and if you would like to sign more than a single file, just repeat this procedure until you’re done, and finally reboot.

After you enabled Test Mode and added signatures to the required system files, they should bypass Vista’s driver signature enforcement and load without any issues. However, if for some reason you’re interested to revert it, you can re-launch the application, and choose “Disable Test Mode” from the main menu, and reboot. If you’re encounter any issues, or having any questions, feel free to post it on our forums.

Note: User Account Control (UAC) must be disabled in-order to use this tool (but you can re-enable it after).