AutoUnattend.xml, Bypass the All Windows 11 installation restrictions

Stop pulling things like this out of your ass when you, again, have no idea what you're talking about.
I can make an actually accurate list of that tomorrow.

As for the registry checks, this is as simple as it gets:


So for the last time, BypassCPUCheck and BypassStorageCheck do not exist to the installer and your fake list doesn't have anything to do with it no matter how much you want it. You can't make a registry key work with sheer will..

 

Your method is not used for upgrades, only clean installs, and none of that or that applies to those at all.

 

Whoa, calm down gentlemen. Had I known this was a little hornet nest with you two arguing like that I might have stayed out of the discussion.

In my case the end result was that a clean installation was performed on top of an existing W10, not an upgrade, the system drive was deleted in the process, despite the theoretical CPU incompatibility. If you want me to do some checks and post additional information I will be happy to do that.

Considering the result I am inclined to believe that the hardware checks on a clean W11 installation may not be as thorough as most of us first assumed. I was surprised as well, since the initial MS PC Health checks done on that machine clearly indicated problems.

Oh, and I like Rufus, used it for years, seen no issues so far.

 

sen-pai, review mine next!

Universal MediaCreationTool wrapper script - get Windows 11 with automatic bypass

While we should all agree that the sharpest bypass atm is using <INSTALLATIONTYPE>Server on the install image, automatic for both upgrades and clean install - or /Product Server option via a batch for upgrades,
People do not like at all that the label during setup is Installing Windows Server... had the same complains while I was using 10 MCT to setup 11 before official release.
Form over function - coincidentally that's 11's motto
Sure, there are some non-cosmetic drawbacks (like not finding DU for sources updates as it is searching with the wrong server guids, probably more) but on the grand scheme it just works great.
Setup is also launching a little faster (due to the drawback mentioned).
Then again, that freaking label is causing concerns even to more tech-savvy people, so I went back to my initial winsetup.dll patching (for boot bypass) + a crazy file deny on the media (for upgrade bypass).
So that gives default 11 Setup label to make people happy, works with setup.exe (no need to use included auto.cmd), works with or without Dynamic Update checked, and there's no appraiserres.dll deleting anymore.

What about the method in this thread? I've played with it.
It works with standard hardware and you can do extra customization stuff as a bonus.
It definitely does not work with VirtualBox 5.x, and pretty much any other blacklisted hardware ignoring official bypass registry keys.
And now for the elephant in the room: out of all the methods so far, this can be the most destructive, because the presence of AutoUnattend.xml triggers autorun of sources\setup.exe (winpe) instead of sources\setupprep.exe (windows)!
Destructive why? sources\setup.exe runs under windows but can only do clean installs, and features re-partitioning just like a normal clean install from boot!
There is a high chance non tech-savvy users might do something they are gonna regret (there are already many reports), so imho, this is too risky for the convenience of adding just a text file to the media and be done with it.
While this particular drawback can be alleviated by inserting the file in boot.wim instead (I'm doing just that in MCT script just to auto-enable local accounts on 11 Home editions),
it would lose all it's convenience advantage and would join the pack of cumbersome solutions like the Boot And Upgrade FiX KiT.
Compared with Quick_11_iso_esd_wim_TPM_toggle.cmd, specially when used with business (enterprise) media that already has an ei.cfg to skip asking for key - there's simply no contest.

 

I'm obviously aware of such file denies. But speaking of less effort, did you know that all you had to do was create a zero-byte file i.e. cmd /c "cd.>appraiserres.dll"
instead of needlessly butchering the dll file, uploading it somewhere and sharing a link to it? same compat result </HardwareItem></Hardware>
I only touch the executables / libraries when absolutely necessary, and when I do, it's just small same-size hex replacements (and when safe, for example the winsetup.dll in boot.wim only loads under PE, does not get scanned),
while your file is simply invalid PE that AV's might scream at.

 

I'm just saying that's not a targeted intervention at all, that's butchering a binary file turning it invalid, so it works exactly the same as the zero byte file.
Any modifications no matter how small would invalidate it's digital signature and hash anyway, but the file you've malformed has no value, really.
Microsoft might enforce validation for it at any time, that's why I prefer to target the alternative text file for now.

 

then stop sharing malformed binaries and just ... cmd /c "cd.>appraiserres.dll"
trust me, it's literally the same (from setup's PoV), but safer. and easier to deploy / share / whatever

 

humor me and run fc.exe "original.dll" "patched.dll"
i'm just gonna stop now I don't want to get infuriated like awuctl

 

All this fuss over a file that if you rename it or delete it will pass the install anyway

 

You need to login to view this posts content.