3 ms·
It's not as much "doesn't exist" but rather "hasn't been turned on". We can speculate/disagree on the future plans of course, but in general the whole process a
by viraptor 5y ago
It's not as much "doesn't exist" but rather "hasn't been turned on". We can speculate/disagree on the future plans of course, but in general the whole process as described in the previous comment is in place. Enabling you to lock down the whole boot process is the goal of SecureBoot. Right now Windows is not preventing you from modifying the startup binaries and system permissions, but they could easily do that. Apple already partially did that with the forced encryption and T2.
These are not "massive changes to the system". Probably still a lot of effort, but closer to "MS now owns the ActualAdmin user who is the owner of system files; you get Administrator who can't touch them".
On Linux you can already prepare system like that fairly easily, with Arch wiki describing most of the steps.