Driver Signing Changes in Windows 10 Anniversary Update

Posted by on , in Category Windows with Tags
Anand Khanse is the Admin of TheWindowsClub.com, a 10-year Microsoft MVP Awardee in Windows (2006-16) & a Windows Insider MVP. Please read the entire post & the comments first, create a System Restore Point before making any changes to your system & be careful about any 3rd-party offers while installing freeware.

2 Comments

  1. Srikanth

    Hi,
    Thanks for the good info.

    We have a kernel code signing certificate driver from Symantec with validly up to 2018.(This is a NDIS network mini port driver)

    It is working fine with windows-7 Ox64, when I upgraded my PC to windows-10 Ox64 (Windows 10 version 1511) it failed to install same.

    Please suggest what needs to be done so that we can use our Driver in Windows 10 machine.

  2. BFeely

    My suggestion would be to contact a good antitrust lawyer; this is going to the point of Microsoft being a monopoly on the device drivers allowed to be installed.
    The EV requirement sounds like it will deliberately kill off hobbyist developers who like to install modified PC hardware, and unless there is a generic USB driver available, potentially kill off those PS3-to-Xinput drivers floating around.
    Good thing my PC boots in the same way as the very first Kaypro I ever played around with as a kid – that is, legacy boot mode. Of course, one never knows when even in that mode Microsoft will crack down on third-party driver developers.

Leave a Reply

Your email address will not be published. Required fields are marked *


1 + 6 =