I did a test with a non fixed 22000.1 pt-BR ISO i made earlier to test and guess what? It installs too on vmware. Will provide the QT log when it's finished installing. Creating a pristine 22000.258 en-US ISO from UUP dump now.
In this he seeks a solution: When you create *.iso 22000.194 with this update you have no problem. If you do the same with this update then you have a problem installing.
That's what the QT finds on 22000.1, not 11 yet till 22000.51 and up. The VM install is updating as we speak, will re-run the QT when finished
Not to put down, "Win 11 Boot And Upgrade FiX KiT v2.0 tool" which works perfectly. by I just downloaded the latest version in "iso-form" using the link from this site to Microsoft's own media creation tool. I saved the ISO, then opened up RUFUS 3.15 to create a bootable flash installer. I noted an upgrade notification to version 3.16. I downloaded it before finishing as I was at "select iso" and had selected it. Under the Partition scheme, it now has a default option for a Win 11 iso's which has the std. ms OEM security restrictions in place for installation I.E. a pristine iso installer, but you can now Choose to patch out the restriction(s) during the flash creation process in the drop-down, Tested installed and activated using MAS 1.4, although it noted a server connection error in red it still activated 11 flawlessly.