Grargar: Hmm, does it work on Windows 10, too? I thought that the driver was completely removed on Windows 10 and this is only good for Windows Vista, 7 and 8 (where the driver is turned off by default). From
this article:
This will make your Windows PC less secure, and it shouldn’t work on Windows 10, where the driver has been completely removed. Short version, yes, assuming you can get your hands on the secdrv.sys, which I believe should be part of the CD files (not 100% sure about this though).
Long version:
The reason the driver is no longer loaded is because it is not signed. The update doesn't target the specific driver, but it was meant to prevent any unsigned driver from being loaded by the system, to prevent people from using maliciously modified drivers to target computers. Said commands on Win7 and Win8 allow them to start the service, even though the driver is unsigned. Microsoft cannot guarantee that the driver is what it claims to be, so it is possible that it can be replaced with a malicious one that can compromise your machine, thus the warning.
Enter driver signing.
If secdrv.sys is signed with a certificate that is included in your machine, Win10 will happily load it and use it. Problem is though that since there isn't currently a secdrv.sys signed with a certificate that is part of current Windows installation, you'll also need to install the certificate. Since Windows only checks if the certificate used to sign a driver exists in your machine, one certificate can be used to sign multiple drivers, and grabbing a signed copy of secdrv.sys and its certificate from the internet means that the same certificate can be used to sign malware. So you'll have to sign the driver yourself.
For more info, option four in
this article.