Windows 10 will be available in all great ice cream parlors this summer. It will bring a number of notable improvements, notably affecting its interface and its functionalities. In the lot, it will also be necessary to reckon with two or three less visible changes, but just as important. Changes related to Secure Boot, or secure boot.
Contrary to what one might think, Secure Boot has no direct link with Microsoft products. In reality, it is a function built into UEFI, or the successor to BIOS.
Basically and as its name suggests rather well, secure boot is only intended to protect our computers from rootkits by securing the boot chain.
OEMs will be able to enable Secure Boot, and lock it
Its operation is quite simple. When the machine starts up, the UEFI will verify that the installed operating system contains a valid and authentic signature. If so, then the upload will continue. Otherwise, the system will not start.
It's more of a salesperson on paper, but in reality the situation is quite different. Secure Boot can effectively prevent the installation of certain operating systems, such as older versions of Windows or even Linux distributions. Note all the same that a lot of solutions have been found on this side, thanks to the Linux Foundation.
The case had caused a lot of noise when Windows 8 was released. To calm the situation, Microsoft had also demanded that OEMs set up a command accessible to the user, to allow him to easily deactivate the function. .
Unfortunately, this will not be the case with Windows 10. While browsing through the presentation broadcast on the occasion of WinHEC last week, Ars Technica actually came across a slide referring to this function. A slide indicating that OEMs will necessarily have to activate Secure Boot on their new machines, and that they will also have the right to lock it if they wish.
Note, however, that nothing is yet done. Windows 10 won't hit the market for months on end, anyway, and a lot can still change until then.