Vista Update turned off unsigned drivers

Soldato
Joined
22 Oct 2004
Posts
9,087
Location
Berkland
:mad: Grr at MS. My pc has just auto installed some updates. I then rebooted and the blooming thing wouldnt connect to the internet. It turns out the unsigned drivers that i use for my wireless card wouldnt load because they were unsigned. I had been using my pc for ages running x64 in unsigned mode. Damn the updates, and damn MS for the signed drivers not running WPA! :rolleyes: :mad:
 
Yeah, its a right royal pain. Got the same problem with rivatuner, this no longer works, only workaround at the moment is to press f8 at bootup, but i cant be bothered to do this everytime.
 
The Author of Ati Tool (the popular overclocking program) has just recieved a driver signed certificate and the next version of Ati Tool will work with the new packs as the drivers will be signed :D
 
Gonzo0 said:
The Author of Ati Tool (the popular overclocking program) has just recieved a driver signed certificate and the next version of Ati Tool will work with the new packs as the drivers will be signed :D

great news! bring it on!
 
ScoobyDoo said:
Yeah, its a right royal pain. Got the same problem with rivatuner, this no longer works, only workaround at the moment is to press f8 at bootup, but i cant be bothered to do this everytime.
Just got the update aswell lol.Owell...Least we can use the ATI tool soon :D
 
Code signing is great. Just get the latest versions of your drivers/software and there should rarely be any issues.

There's no point trying to bypass the protection because Microsoft has committed itself to ensuring it is always up to date - much like PatchGuard.

Any outfit advising you to disable code signing at bootup is, in effect, asking their users to disable a firewall - and therefore shouldn't be trusted.
 
NathanE said:
Code signing is great. Just get the latest versions of your drivers/software and there should rarely be any issues.

There's no point trying to bypass the protection because Microsoft has committed itself to ensuring it is always up to date - much like PatchGuard.

Any outfit advising you to disable code signing at bootup is, in effect, asking their users to disable a firewall - and therefore shouldn't be trusted.

No, its not.

When i was running my wifi card in xp i could use WPA. Now the default MS drivers for the card do not allow you to use WPA, only WEP. If you install the unsigned drivers from realtek, then you can use WPA.

Thats crap full stop.
 
This is a bunch of rubbish. I can no longer use rivatuner, and my high overclocks have gone to defaults. I can't use anything else. Way to go Microsoft.
 
KNiVES said:
This is a bunch of rubbish. I can no longer use rivatuner, and my high overclocks have gone to defaults. I can't use anything else. Way to go Microsoft.

Patience, signed drivers for overclocking programs are coming soon. Ati Tool will soon have signed drivers and im sure other programs will follow suit ;)
 
leaskovski said:
No, its not.

When i was running my wifi card in xp i could use WPA. Now the default MS drivers for the card do not allow you to use WPA, only WEP. If you install the unsigned drivers from realtek, then you can use WPA.

Thats crap full stop.
Realtek does have a code signing certificate as my sound drivers work just fine on Vista x64.

Is your driver labelled by them as "Vista compatible"? If not, then there is your problem ;) Just because a driver "works" on the surface doesn't mean there is something critically wrong underneath the surface.

Only install drivers marked as Vista compatible. These will always be code signed.
 
KNiVES said:
This is a bunch of rubbish. I can no longer use rivatuner, and my high overclocks have gone to defaults. I can't use anything else. Way to go Microsoft.
All they've done is updated the protection to prevent known workarounds/hacks of loading non-code signed kernel drivers. This is an integral security measure included in Vista that prevents rootkits and other nasties.

If anything you should be blaming the software vendor that encouraged you to use a workaround in the first place without properly labelling it with a disclaimer/warning message that it could break in any future hot fix or service pack.
 
Back
Top Bottom