Closed GoogleCodeExporter closed 9 years ago
Hi,
this annoyance is caused by changes in ntoskrnl.exe which have found their way
into
your system through windows update. The switch described in the FAQ doesn't
work
anymore to the effect that there's no way to permanently disable the enforced
driver
signing.
There are sadly only two ways out of the misery:
1. Either enough customers complain about this at Microsoft's service and they
decide to re-enable the switch,
2. or someone buckles up a larger sum of money for a certificate and signs this
driver.
The strict enforcement of driver signing doesn't inherently create better
drivers or
a more secure system, so I fail to see the necessity of it.
Thanks for the link to the Diablotek card, I'll add it to the list of supported
devices.
Original comment by dogb...@gmail.com
on 11 Feb 2008 at 6:28
Original issue reported on code.google.com by
jst...@gmail.com
on 10 Feb 2008 at 8:10