I've run I run the IoT version of 10 on everything - laptop, desktop, VM's, etc, it's great because it only does updates 2x/year, no feature updates by default.
Licensing is handled by the scripts from Microsoft. If you're a large enough business, it would be worth the cost of the Enterprise licensing just in reduced support issues.
Basically, it's Windows without the bloat, which seems like a good thing. I can use whatever apps I want for photo viewer, etc, and no garbage on the system.
If anything, it should be optional for personal use, and mandatory for enterprise. Not that they would come to this conclusion either way, granted that half of the workforce is busy putting ads into the start menu, and the other half are probably not doing any work whatsoever
I'm not using disk encryption. It's a desktop and if it's every stolen I've got bigger problems.
Also, I presume that disk encryption makes it so you can't just pop the drive in an adapter and pull stuff off it, which I sometimes need to do with old, retired drives.
veracrypt is a thing, encrypting drives does not need TPM.
Just boot using the good old Master Boot Record for a clean solution (The Veracrypt documentation gives a good overview). Veracrypt works with EFI too, but the EFI partition itself cannot be encrypted. You can even create a hidden OS, if you are forced to give out your password, theres still plausible deniability.
I found it was pretty easy to get rid of the nag. I installed a different OS. For my development stuff that needs windows and I can't run with wine (very few tools) - I have a VM running a windows version with 0 Internet access. Fuck that company sideways.
I'm sure this is a meme, but the trust is proving the OS is not tampered with.
Like, if malware was able to inject a malicious windows update URL into the OS, and inject a malicious certificate that gets the OS to trust the malicious updates by the malicious URL.
The signature of the OS would then differ from what the TPM/CPU recorded during OS boot and what the TPM/CPU has hashed during running. This would indicate that the OS has been tampered with.
So the trust in TPM is that the TPM and CPU are working together correctly (which is certified during manufacturing), so that the TPM can then attest that the OS (or software or whatever) hasn't been tampered with.
So yeh, it's MS (or whatever software company) trusting that the software it is interacting with is running as it is intended
Honestly, the user is the biggest security risk in the first place. People run all kinds of malware and put their passwords into phishing sites all the time. One thing a TPM is used for is secure boot, which prevents malware from inserting its own bootloader to take over the OS.
The user of a hammer is the only one who can destroy the hammer. Humans on the planet's surface are the only ones who can destroy the planet... we should definitely separate the human user from his rights and freedom, shouldn't we?
There’s a registry key (sorry I’m on mobile right now) that you can actually add during a clean setup of current non-LTSC versions that remove the requirement for vTPM and SecureBoot. That install should easily be able to be live migrated. We were doing that when first playing with Windows 11
They are lowering the specs for this one version that's only available to license to Enterprise users because it's meant for Enterprise level IoT use cases, not as a typical desktop.
I knew they'd do it eventually. Use the win11 upgrade to get people to enable tpm and secure boot for like a year or so, but they still want everybody onto win11 eventually so relax he requirement after it has done its job.