This "security" feature confuses the hell out of me. HOW in the sam hill are they going to prove every process running with privileges is in a "secure" state, how can that be possible? Even with constant wasteful memory scans there could be data files that evade micro-brother. So what if it booted in an authentic manner, the user could have tampered with any number of privileged processes, and the second they opened one of THREE web browser engines and ran some unknown 3'rd party advertisement code all bets are off. Not even going to get into malicious firmware/drivers that microsoft will happily sign (see: lenovo superfish, or razer driver menu privilege escalation for recent examples). This is more security theatrics from the same old players, when will it stop? When will all you supporters see what is happening? This is more about operational control than security; it makes me sick to see so-called hackers supporting such an obvious trap. Yall need to dump your shares and join the right side of history because it only gets worse until the weight of oppression ignites a revolution. If you're still holding, think about what is the next "security" frontier after you let them have this? Require every program on the OS, and then every website to sign javascript with cryptographic keys they don't have root control over? GTFO board room members, you're drunk. You want to throw out our freedoms just because microsoft and intel designed a garbage (UEFI) spec that doesn't have a way to physically prevent writes, and damn near requires you to use an ancient FAT filesystem? WHY WOULD YOU TRUST THEM NOT TO BOTCH THIS ONE TOO?