Windows 10: Microsoft requires the signature of the kernel drivers – Clubic

Update Windows Anniversary 10 introduces an additional safety feature: on new installations of the system, only drivers digitally signed by Microsoft will be allowed access to the kernel

With the release. day Anniversary update of Windows 10, Microsoft will finally implement early restriction for over a year: on fresh installations of the system, only the drivers that have been digitally signed by the tools of editor will be allowed in the kernel memory space. In the name of security, Microsoft validation equipment manufacturers therefore must imperatively go through the process to ensure the proper functioning of their devices to the latest version of Windows 10.

To ensure compatibility with the existing fleet, this restriction will only apply to new installations: machines updated to Windows release in October 1607 (from an earlier version of the system) will continue to accept drivers signed by a third authority. Microsoft also states that previous pilots to 29 July 2015 (Windows 10 release date) will be accepted. The editor also indicates that at this stage it does not yet mean block the boot drivers ( boot drivers ), but the measure is being considered for future versions of the system.

“ in summary, a new installation of Windows 10 in 1607 version with the Secure Boot feature enabled, drivers must be signed by Microsoft or have a third party certificate issued before 29 July 2015 , “says the editor.

for device manufacturers, it will be difficult to overcome this measure. Most of them already certified drivers by Microsoft, but some branches beyond this stage: this is for example the case of some hotfix or drivers in beta, distributed validation to for testing or urgent correction. The side of the end user, it is still possible to disable Secure Boot to install an unsigned driver. – Subject to the availability of equipment for the

Initially decided in April 2015, this restriction was lifted for the launch of Windows 10, but returns to the front of the stage with updating Birthday (expected in the 2nd of August). For Microsoft, this is closer to lock access to the kernel and thus prevent them running malicious code. It complicates the same time the development of pilot kernel that would not have the means or the interest to go through a full certification process.

Edited on 02 / 08/2016 at 10:40 am