|
|
|
jbullard
Jason Bullard |
Posted:
Fri Aug 31, 2007 5:30 am |
|
|
|
Vice President Software
Joined: 06 Jun 2004
Posts: 3233
Location: Utah
|
|
Unfortunately our attempts have been unsuccessful. Microsoft did release a message saying that they were going to be removing the ability to do this within the Windows environment. This means that the only way to have this feature is either not to install those updates or restart and click on F8 and disable it there.
We will continue to look for options but as of right now it doesn't look like it is going to be possible.
HTH
|
|
|
|
|
|
|
|
Back to top
|
|
|
|
VEKARA
|
Posted:
Tue Sep 04, 2007 6:28 am |
|
|
|
PRO New Member
Joined: 30 Aug 2007
Posts: 4
|
|
What is the reason why Microsoft is doing this way.
Does this improve security on Vista or does microsoft get money this way.
Fastly thinking it might be more benefical to not have this requirement on
Vista X64 since it has much greater need for good drivers.
|
|
|
|
|
|
|
|
Back to top
|
|
|
|
JabbaPapa
Julian Lord |
Posted:
Tue Sep 04, 2007 10:17 am |
|
|
|
Respected Member of PROnetworks
Joined: 22 Feb 2004
Posts: 14272
Location: Monte-Carlo
|
The purpose here is to protect the Windows kernel from malware, to combat the recent proliferation of software drivers (that add unpredictable instability problems to Windows), and also to add an extra level of protection against small operators interfering with the Microsoft business model 
|
|
|
|
|
|
|
|
Back to top
|
|
|
|
VEKARA
|
Posted:
Wed Sep 12, 2007 9:56 am |
|
|
|
PRO New Member
Joined: 30 Aug 2007
Posts: 4
|
Okey. But why just Vista X64 bit. I have alredy sent angry feedback to  Microsoft (like that would help) but it seems that it's impossible to me to get over this.
Edit by NT50
|
|
|
|
|
|
|
|
Back to top
|
|
|
|
JabbaPapa
Julian Lord |
Posted:
Fri Sep 14, 2007 12:12 pm |
|
|
|
Respected Member of PROnetworks
Joined: 22 Feb 2004
Posts: 14272
Location: Monte-Carlo
|
|
IMO Microsoft has gone too far here, the move from 32- to 64- bit is hard enough to swallow withouit all this extra digital signature cr*ap-ola ...
|
|
|
|
|
|
|
|
Back to top
|
|
|
|
Omego2K
|
Posted:
Thu Oct 11, 2007 11:18 pm |
|
|
|
PRO Level 2
Joined: 10 Feb 2007
Posts: 11
|
|
It's pretty obvious why they are doing this. It's to let the music labels and DVD publishers to disable or manipulate drivers in case a pirated copy is attempted to be use without hackers/crackers distributing modded drivers to stop them.
|
|
|
|
|
|
|
|
Back to top
|
|
|
|
kataklysm01
|
Posted:
Fri Jan 11, 2008 7:37 pm |
|
|
|
PRO New Member
Joined: 11 Jan 2008
Posts: 1
|
|
Same problem here with Mirror raid. I also have SP1 for Vista x64 installed. I have uninstalled the two KB mentionned earlier in this thread.
Still can't disable driver signing. This feature is really a pain. I'm almost regretting using x64.
|
|
|
|
|
|
|
|
Back to top
|
|
|
|
ace-a-rue
|
Posted:
Thu Mar 06, 2008 12:58 pm |
|
|
|
PRO Level 2
Joined: 06 Mar 2008
Posts: 10
|
|
i installed boot pro last night in addition to doing a fresh install for vista64 in the 1st 80G partition and then XP-SP2 in a 2nd 80G partition (on a Areca Raid PCIe card).
i did not do any microsoft update downloads...i then opened boot pro and checked mark the disable vista driver signature check box.
i rebooted and opened coretemp 0.96 program which i know was not compatible with vista64...coretemp worked perfectly!
on a prior install of vista64 with MS updates installed, i tried disabling vista driver signature in boot pro but it would not work even though i uninstalled those two updates noted on page one of this thread: KB932596 & KB938979
i subsequently read (not here) that these two additional updates had to be removed in order to disable the driver signature for vista64: KB941649 & KB943078...uninstalling these updates did not permit boot pro to disable the vista driver signature either.
So..it appears, at least, once the first two updates (and possibly the other two) are downloaded and applied, you can not use boot pro to disable vista driver signature...on the other hand, F8 selection at the OS selection screen in DOS will still allow the user to disable vista driver signature, with all updates installed.
i also heard a rumor that SP1 will disable anyone from disabling driver signature even via the use of the F8 key.
i hope this helps the developers to come up with a fix for boot pro to disable vista driver signature even after installing/uninstalling those updates.
|
|
|
|
|
|
|
|
Back to top
|
|
|
|
JabbaPapa
Julian Lord |
Posted:
Thu Mar 06, 2008 1:03 pm |
|
|
|
Respected Member of PROnetworks
Joined: 22 Feb 2004
Posts: 14272
Location: Monte-Carlo
|
| ace-a-rue wrote: |
| I also heard a rumor that SP1 will disable anyone from disabling driver signature even via the use of the F8 key. |
This is NOT true
---
From a purely personal POV, I have had no issues since my last hardware upgrades with installing unsigned 64-bit hardware drivers from various sources, but of course people needing to use older unsigned software drivers and/or older x64-capable hardware might well have some remaining issues...
|
|
|
|
|
|
|
|
Back to top
|
|
|
|
ace-a-rue
|
Posted:
Thu Mar 06, 2008 4:30 pm |
|
|
|
PRO Level 2
Joined: 06 Mar 2008
Posts: 10
|
| JabbaPapa wrote: |
| ace-a-rue wrote: |
| I also heard a rumor that SP1 will disable anyone from disabling driver signature even via the use of the F8 key. |
This is NOT true
---
From a purely personal POV, I have had no issues since my last hardware upgrades with installing unsigned 64-bit hardware drivers from various sources, but of course people needing to use older unsigned software drivers and/or older x64-capable hardware might well have some remaining issues... |
glad to hear that SP1 upgrade won't put a cabash on the driver signature disabling thingy
i do have a lot of older stuff that i would LOVE to use in vista64. 
|
|
|
|
|
|
|
|
Back to top
|
|
|
|
|
Back to top |
|
|
|
|
|