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-04T03:07:14+00:00

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2022-05-03T23:14:15+00:00

    Hi fg,

    This does not work at all in VMware. I retried several times to no avail, even changing date on the Host system in case that was a concern. Please note the different error code as well. This was on my Beta vm from 22598 to ISO of 22610.

    Image

    FBH: https://aka.ms/AAgugg3

    Regards,

    Hi Johnny,

    Weird that it gets an error with all zeros in VM instead of the 0xc1900401. 😎

    This was my original FBH report about the issue, it already happened with the 1st MS official ISO 22579 and also with 22598 when upgrading from a previous Ni 22H2 Build, I could never get the error when upgrading from 19044.xxxx or 22000.xxx or an update repair in place from the same build that was previously Upgraded with W.U.

    https://aka.ms/AAgc8c2

    I can now reproduce the problem consistently.

    The workaround of setting the date back fixed the problem on 2 different machines.

    P.S.

    Weird that Sibro is not seeing this W.U. loop problem anymore, he is also running VMware. 🤷‍♂️

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Johnny55 5,155 Reputation points Volunteer Moderator
    2022-05-03T22:11:05+00:00

    Hi fg,

    This does not work at all in VMware. I retried several times to no avail, even changing date on the Host system in case that was a concern. Please note the different error code as well. This was on my Beta vm from 22598 to ISO of 22610.

    FBH: https://aka.ms/AAgugg3

    Regards,

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2022-04-07T02:31:01+00:00

    Hi Sibro,

    Looks like with build 22593.1 there is no more delay on mounting an ISO file with File Explorer.

    That's great. I avoided that delay by mounting the ISO in another file manager, I use total commander, and it would instantly open the image in file explorer all the time to run setup. I do recall the long delay, at times over 5 min on my old non-compliant device.

    @Johnny_55,

    They had fixed this before, I think they forget previous fixes when they change Builds.

    Usually, it is one step forward and 2 backward. 🤣

    Maybe I should go watch TV too, enough for today. 🙃

    Still cannot build proper ISO directly from SoftwareDistribution\Download.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2022-04-04T21:31:59+00:00

    Found the link to install Web Experience pack and got the latest level.

    That fixed the Widgets, after a reboot it was working properly.

    Detective fg2001 strikes again! 👏👏👏

    @Sibro.o,

    Another difference, between Dev and Beta, even if they are at the same Build level 22581.200 right now, they have 2 different versions for the WebExperience Pack:

    Dev:

    MicrosoftWindows.Client.WebExperience_521.20060.315.0_x64__cw5n1h2txyewy

    Beta:

    MicrosoftWindows.Client.WebExperience_521.20060.135.0_x64__cw5n1h2txyewy

    This below is the old one that does not work and is installed with the uupdump ISO:

    MicrosoftWindows.Client.WebExperience_421.20050.505.0_x64__cw5n1h2txyewy

    What makes it even more puzzling is that the same level App is installed with MS official ISO 22579.1, but in that case Widgets work right away after the upgrade.

    Hard to say what else is different that prevents Widgets from working in one case, but not the other?

    Also, the WebExperience is at the same level on a clean install and it works fine in that case. 🤷‍♂️

    Perhaps because it gets updated right away to this one, before the final update?

    MicrosoftWindows.Client.WebExperience_421.20070.95.0_x64__cw5n1h2txyewy

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments