There is no win 11 that doesn't require the tpm requirement. It will probably have the same tpm requirement when released.
Are these bypass tools legit? Any issues after the installation + updates within the OS (Microsoft Updates) ? What's better, Windows 10 LTSC (latest edition) or the latest Windows 11 with the bypass tool for non TPM users ?
From MSFT pov, no. Since the simple hotfixes don't check the requirements and the existence of 16 months now, with no problems with updates reported, it's safe to use. The 2 mentioned OS's are not comparable, personal needs, usage and preferences are the deciding factors.
I like Windows 10 LTSC . May have to check out Windows 11. final question, any bloatware removal apps once i install windows 11?
I use Multi-OEM/Retail Project {MRP} - Mk3 for apps removal and some cosmetic tweaks during installation of the OS.
is edge boost working for you guys? mines loading like its been fully closed everytime? Also ..dont run superseeded cleanup folks, some updates call up old installs and will fail if they cant ping them running the default disk cleanup is fine
At .674/.675 LCU, the 22621 component of microsoft-product-data stays at 22621.608, while the 22622.22621 component continues to be updated, which may mean that the 22622 will still be pushed. amd64_microsoft-product-data_31bf3856ad364e35_10.22622.22621.675_none_58e761a889465cc8.manifest
Who said you need to activate in the temporary machine? In such case it's just a step needed to do an in place upgrade (w/o touching the installer) , just activate after W11 is in it's final place. Still a corner case given Rufus and alike do nothing to the OS itself, they just patch the installer, and 99% of people are fine using them. After all W11 is just a solution looking for a problem, so they created a problem artificially.
No, not hypothetical. What I wrote works. Deploying works. No matter if on old school partition or in the way everyone should use in 2022 (native vhds). Moving an installed system from a physical PC to another or from VM to physical PC (and viceversa) works as well, unless the machine has an uncommon HDD controller (something different from NVME/AHCI/IDE). Booting a native VHD(x) inside Hyper-V/VMware/Vbox works, booting a vhd(x) created by Hyper-V/VMware/Vbox works as well. In short, what I mean is that in 2022 installing from a usb key should be the very last resort, but practically is the only way known by the herd. That makes the obvious ways listed above a corner case, in practice. Corner case but not hypothetical. Very practical.
Like I said it works if donating and receiving machines are using the most common options like AHCI. It doesn't work if one of the donating/receiving machines uses a old controller which doesn't support AHCI or a new controller set to a more exotic mode (Amd RAID/Intel Rapid storage and alike or an uncommon SCSI controller...) In that case you need to Sysprep/generalize before moving across machines. I'm not used to write spooning tutorials, I like to trigger curiosity about things that one have possibly never heard of. I put the spark but the reader must bring the fuel to get a fire. That said I mentioned many things in my message above, explaining all of them extensively would require four pages of text. So, please, ask more precise questions, about what is not clear for you, I'll be glad to help, as always. Hint, you can start practicing moving a virtual HDD from hyper-V to vmware, or from VMware to Virtualbox, or a combination of them. You will face the same scenario as moving from two different physical PCs, w/o risking to mess anything and w/o any downtime on the PC you use.