I'm ever so glad that my Windows machines are still running Win 7 with auto updates nuked.
That's the way it'll remain until the hardware fails. Of course, newer hardware runs Linux and replacements will also run Linux.
Microsoft Windows is now so out of kilter with users' actual realworld needs that I don't fully understand why people haven't migrated away from it droves.
Hopefully I don't use windows, but it is incredible that it does not piss off more people that you can't use an entire OS just because of a hw module required only for a small feature used by a minority of users. Mostly corporate.
But if you think long term, it makes sense for Microsoft:
They dream about having the same control as apple and Google have on their devices. The problem is that nothing prevent users to be the master of their machine and doing whatever they want with it. With the tpm module, they can start to restrict some things to you on your own computer, controlled by the tpm, and as an user you will have not way to do anything about it. Like copy your data to another computer.
My life is no longer compatible with Windows.
Does TPM pass though mean that the virtualized OS knows the identity of the host hardware?
I've used the below tool (W11 Boot and Upgrade FiX KiT v2.0) to resolve this on an old VMware host.
Password MDL2021
Simple to do, works fine for me. I built the original image using uudump.net
Im not the creator or author of either tool just a satisfied user.
Is there a way around this restriction? Does the registry hack that floated around when the first beta came out still work?
I always preferred VMWare workstation anyway. The downside is its harder to install a small easy VM on work PCs.
What does this do for the end user?
How come I currently have an instance of Windows 11 working just fine under VirtualBox?
Until VirtualBox implements TPM 2.0 pass through, which they've already started working on: https://www.virtualbox.org/changeset/90946/vbox
Qemu already supports TPM pass through and secure boot.