[Kururin]

This statement is factually incorrect! It has been proven otherwise from the times of the Windows 11 Dev leak and the release of its requirements. The modification of the ISO is just one way to achieve it. The ISO modification is nothing special. There are guides that provide clear and simple instructions to do so. The other very easy way would be to simple use the Windows 10 installer structure with the Windows 11 install.wim file that contains the actual Windows 11 OS. It's just as easy as replacing two files.

Yes I was incorrect about the not being able to bypass at all but my point still stands you need to modify the installation some way to have it install in your machine, which can be turned off any time. You say its "Clear and simple instructions" but you can to mess with the registry settings and frankly that is for advance users, so much so that its not found in the home edition and specifically for "Pro" user. Many users will have problem installing it and might frankly mess up leaving their install broken. And yes the ISO way can be simple at this time but the compatibility can break at any moment.

That would be another way to bypass some of the requirements and with this statement of yours you just disproved yourself and your previous statement. However, this statement is also so so. The registry hack is not finicky at all. The installer is the active part that so far performs the requirement check and the two registry entries disable the requirement check for TPM 2.0 and Secure Boot. Since the registry hack works it does it's job. If it would be unsupported it wouldn't work.

Again yes that was a mistake on my part for saying its the only way, but again my point above stands as registry is something that is not for normal users. You claim yourself to be a tech expert and you should know this as regular less tech savy people will have a hard time following the instructions (mess up even), and some might not even try so because its messing with important system definitions. Unsupported means Microsoft does not want you to use the registry hack to install Windows 11, does not mean that it does not work. It is currently working on the dev build but in future--we don't  know.

Did you even try it yourself? I did. It's part of my job to test new things in the interest of the company I work for and my own curiosity. Even more funny is that I could install Windows 11 in a VM without TPM (no TPM at all) and no Secure Boot without any hacks. Moreover the VM host had a unsupported old Intel Core 6000 CPU and it had no supported GPU. The Insider Preview installed instantly without any issues and that even on an MBR partition with legacy mode (the VM software only supports legacy mode). It also installed fine on a older Surface without Secure Boot and other things disabled / unsupported... without any hacks again at all.

Yes, I fully tried installing it myself. I run a MacBook Pro 16" BootCamp installation with Windows 10 on external drive. I had to modify the ISO via replacing the wim and then mess with the registry to Windows 11 play nice with my MacBook. But as expected many things do not work until Apple will provide updated drivers themselves even though Windows 11 is just a reskinned Windows 10. VM is a different thing that normal operating system, you should know this as well. What works on VM does not mean it will be same for a normal installation of Windows 11. Unless you are running Surface Studio 2 you can run any Windows 11 instillation, not sure as what's your version but I think your case is it being one of the Surface that is supported.

Thank you for telling the obvious. If you mess up... you messed up. And that a messed up installation might be broken is also outright obvious. That it is on you... well, on who else would it be?

Yes, I am being obvious by telling that people might mess up, its is human to make mistakes and its on them but if they did not try installing Windows 11 the wrong way they wouldn't been in this situation but here you go telling people its so easy to install Windows 11 and pin the blame on them when they mess up.

Thank you for repeating what I already said in my post (pretty much at the end).

You contradict yourself, you say what is the outcry is about and how easy it is to install with the bypasses (where serious mess up can occur) then go on to say what I said about privacy. Does not matter if its repeated--it is the truth.

My initial installation was also Windows 11 Home and I also couldn't bypass the Microsoft account requirement at first. That was with the latest Inside Preview. However, a colleague who was also playing around with Windows 11 bypassed it easily and I was amazed how. He simply entered trash information at the login window which somehow allowed him to create a local account by unlocking the option to do so.
And here is a guide to just do that: https://winaero.com/how-to-install-windo...l-account/
However if Microsoft pulls through with their always online enforcement in Windows 11 Home they might actually fix that in future Insider Previews and the final version.

You say that yourself that its a temporary fix as its a Dev build, if Microsoft ups their game you cannot simply bypass and It will be a privacy nightmare, does not matter if you friend bypassed it in some dev build with fake info as it does not reflect the final version and the final version can make you verify with a legit Microsoft account.

Anyway. Just stay with Windows 10 until the end of its support in 2025 (if extended somehow even longer). After that the only real option is probably Linux or you simply pirate Windows 11 Enterprise and use heavy duty debloater tools with things like simplewall or other way more effective firewalls.

This just proves my point and I agree.