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 No comments

232 answers

Sort by: Newest
  1. Anonymous
    2022-04-11T00:25:58+00:00

    I also used the same ISO to upgrade from 22000.593 -> 22593 on a VM and didn't get the loop.

    IDK what's going on but definitively a bug.

    btw, on April 4th, MS released an update using a previous KB number (KB4023057) which is supposed to upgrade 22000.593 to 22000.647 but WU doesn't find it, do you know anything about this?

    Image

    I think kb4023057 is always reused when they want to cleanup space for the next build it is not changing the build number.

    KB4023057: Update for Windows Update Service components (microsoft.com)

    As for 22000.647 was found referenced in some server, but not a released update. Maybe next Tuesday there will be the build update?

    Windows 11 build 22000.647 - BetaWiki

    This seems to be a mistake:

    Select language for Update for Windows 11 - KB4023057 (22000.647) amd64 - UUP dump

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-04-10T23:54:11+00:00

    Used the same ISO to do upgrade from 22581 -> 22593 on 3 machines and got the W.U. loop after that.

    They definitely have a bug with the way they check for updates.

    I also used the same ISO to upgrade from 22000.593 -> 22593 on a VM and didn't get the loop.

    IDK what's going on but definitively a bug.

    btw, on April 4th, MS released an update using a previous KB number (KB4023057) which is supposed to upgrade 22000.593 to 22000.647 but WU doesn't find it, do you know anything about this?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-04-10T22:38:09+00:00

    I did two in-place repairs 593 > 593 (laptop & VM), both were clean installs and I didn't get the loop.

    Hi Sibro,

    The same here, clean install 22593 and in-place repair to 22593 did not cause the loop on W.U. afterward.

    Used the same ISO to do upgrade from 22581 -> 22593 on 3 machines and got the W.U. loop after that.

    They definitely have a bug with the way they check for updates.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-04-08T05:22:51+00:00

    Hi Sibro,

    Perhaps the loop on Download and Install has something to do with the update history?

    Hi fg,

    IDK, possibly.

    I did two in-place repairs 593 > 593 (laptop & VM), both were clean installs and I didn't get the loop.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-04-08T04:28:19+00:00

    Hi Sibro,

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

    I did an upgrade from 19044.1620 to 22593.1 using a uupdump created ISO and everything worked fine this time

    Back with the Download & Install loop again

    Hi fg,

    Indeed, the delay is gone again, lets see how long it will last this time.😁

    The ISO worked for me as well.

    I haven't tried an upgrade yet but I'm sure you're correct. 😎

    Hi Sibro,

    Perhaps the loop on Download and Install has something to do with the update history?

    I don't have the problem if I do an update/repair with ISO from 22593.1 to 22593,1 on a system that was already previously updated with W.U.

    I noticed that when I upgrade with ISO from a previous Build (22581.200) there is nothing in the history showing that 22593 was installed.

    They should not rely on the update history to make the decision about downloading and installing again.

    We have done that for years without problems, they only started this mess with Nickel Builds. 😡

    Was this answer helpful?

    0 comments No comments