Discussion in 'Windows 11' started by spinalGR, Sep 1, 2021.
That is not a mystery since the updates don't check for the minimum requirements.
You need to login to view this posts content.
@IXMas can you run the QT on your host OS too?
That is on a VM too, not the actual hardware?
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.
QT log from Windows 10 Pro ???
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
I have a problem installing it (22000.258) but not (22000.194)
Pristine non fixed 22000.194 UUP dump ISO is being created, will run a test asap
I'm sure you won't succeed
Thanks! Used pisthai's method and had the smoothest windows install ever on my multiboot system.
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.