Nothing to do with the internet, I bet if you go back to your whole log you will find errors during download.
Seems to be building this time regardless of the download errors.
I'll stick to the one created yesterday without any errors. π€£π€£π€£
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I created all 5 installation ISO files for all 5 Builds, but only 22557 contains all the system Apps required for a full clean install, the other 4 are missing all the basic Windows and System Apps needed for a functional system. Also, the App required for opening Windows Security (Microsoft.SecHeatlthUI) is missing, all this makes the resulting system unusable.
Last one on 22557.
Microsoft.SecHealthUI Microsoft.SecHealthUI_1000.22557.1.0_x64__8wekyb3d8bbwe
I noticed another issue common to all the Ni builds, if they are used for an upgrade or in-place they may only work correctly if they are done online allowing the check for updates.
If I use the option "Change how Setup download updates" to "Not right now", the upgrade or update in place still completes, but it creates a problem on subsequent W.U.
In this case W.U. goes in a loop trying to Download and Install the same Build over and over. Error 0xc1900401 is logged in that case.
I could not find a way out of that loop.
If I do the same upgrade or update in place online letting the Setup check for updates, as recommended, the process may complete correctly without subsequent W.U. loop issues, but the behavior is inconsistent depending on how the previous update was done.
The official MS Insider ISO 22579 includes all the required Apps and the Microsoft.SecHealthUI which is needed for opening Security.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
@Sibro.o,
I tried a clean install and all the Apps are there.
One very unusual thing I was surprised to see.
I did not encounter any of the checks for Windows 11 requirements on a clean install.
I can do a clean install on a completely unsupported device without using any hacks. π€£π€£π€£π€£
Something definitely different from the official MS ISO or even the ones created from uup-dump.
Looks like that is intentional, the size of the appraiserres.dll is only 86 KB, compared to the normal one that is 165 KB. Sneaky! See the difference below.π
Modified file by AdGuard
This is on 25136 from uup-dump same size as the official MS file.
This is on 25120 MS Insider ISO, 165 KB.
Same behavior with Update in place using the same ISO while connected to the nettwork and checking for updates.
Went through the update all the way on an unsupported legacy BIOS device. π€£π€£π€£
Another reason this is no good for testing the real thing.
One very unusual thing I was surprised to see.
I did not encounter any of the checks for Windows 11 requirements on a clean install.
Another reason this is no good for testing the real thing.
Remember what I said on my original post?
"For those who need unblocking, WIM splitting, etc."
If you had option F turned ON (remove installation restrictions), those are the intended results. π
Turn it OFF for testing if you must.
One very unusual thing I was surprised to see.
I did not encounter any of the checks for Windows 11 requirements on a clean install.
Another reason this is no good for testing the real thing.
Remember what I said on my original post?
"For those who need unblocking, WIM splitting, etc."
If you had option F turned ON (remove installation restrictions), those are the intended results. π
Turn it OFF for testing if you must.
Have fun with it, I really don't have any use for it especially when I see errors.
I was just curious to see what they were doing different.
Seems even slower than the other one.
I miss how much easier and faster I could make the ISO before all these damn changes. π€£π€£π€£π€£