Clean Install of Windows 11 Ni Preview Build works with Build 22557, but not with 22563, 22567, 22572, 22581, 22593, 25115

Anonymous
2022-03-11T03:48:13+00:00

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.

Windows Insider program | Windows Insider preview | Install, activate, and Windows update

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.

0 comments

232 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-05-25T06:27:01+00:00

    Have a good night.

    👍have a good one too.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-05-25T06:09:57+00:00

    As I told Johnny on the other thread, it works with official ISO and with .1000 from dump but not with .1010

    Maybe something wrong with the ISO or they added a new block that affects VMware VMs only or my setup.

    Thanks, I know you like to get to the bottom of things but this is not a big deal for me. 😎

    No problem.

    In a day or 2 there will be a new Build to play with. 🤣

    Have a good night.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-05-25T05:55:02+00:00

    As I told Johnny on the other thread, it works with official ISO and with .1000 from dump but not with .1010

    Maybe something wrong with the ISO or they added a new block that affects VMware VMs only or my setup.

    Thanks, I know you like to get to the bottom of things but this is not a big deal for me. 😎

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-05-25T05:40:50+00:00

    By temporarily cutting the network connection to the host.

    Cutting the network to the host may be what causes the difference, perhaps you have to cut the virtual switch to simulate the same situation?

    VM behavior and simulation has too many variables.

    If all you want is to avoid the MSA, you can use the other suggested method with the fake ID.

    Just for curiosity I just tried the other method suggested by SproutTheRobot instead of oobe\bypassnro and it worked.

    But that is without network connection again on a real laptop.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-05-25T04:57:08+00:00

    That looks like one of the errors I got, you can check the screen shots I posted earlier.

    Maybe depending on when you download the files, some may not be ready or being modified and then they cause the errors?

    I don't know how you get to this screen with VM?

    How do you cut the network connection on VM ?

    Anyway, the second method suggested by Neowin while you are connected to the internet still works too.

    IDK what is causing the error/s but if this is MS sabotaging ISO making so be it!

    Don't feel like wasting anymore time on this.

    The process of clean installing on a VMware VM is pretty much the same as on a physical machine. I get to that screen the same way you do.

    By temporarily cutting the network connection to the host.

    Yeah thanks, looks like I will have to use that method on VMs from now on.

    Was this answer helpful?

    0 comments