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. Johnny55 5,155 Reputation points Volunteer Moderator
    2022-05-05T23:47:37+00:00

    Yes, we are screwed on which way to go right now. I put up another FBH regarding the loop: Hehe, never mind, see you already upvoted, I got yours as well.

    https://aka.ms/AAgugg3

    Regards,

    I just saw a comment on the FBH report saying that pausing the update and then resuming it gets rid of the loop.

    We can try that too to see if it does the trick. 🙃

    Hi fg,

    I did try pause the updates with 22616, rebooted then resumed. It did get rid of the loop. That trick is working. Wasn't sure if the reboot was necessary, will try on one of the other vm's. Not thinking clearly tonight 🤣

    Regards,

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-05-04T19:44:10+00:00

    Hi Johnny,

    I just verified the suggested workaround from Dream W, not sure if it will work on your VM, but it worked perfectly on the real machine.

    I reproduced the problem again with the error 0xc1900401 and then clicked on Pause Updates with default (Pause for 1 week) and resumed right after.

    That took care of the W.U. loop and the error disappeared from the update history too. 😉

    Unfortunately, 2 other updates for Intel that were pending to download and install disappeared too. 🤣

    Image

    Image

    Image

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-05-04T17:37:40+00:00

    Yes, we are screwed on which way to go right now. I put up another FBH regarding the loop: Hehe, never mind, see you already upvoted, I got yours as well.

    https://aka.ms/AAgugg3

    Regards,

    I just saw a comment on the FBH report saying that pausing the update and then resuming it gets rid of the loop.

    We can try that too to see if it does the trick. 🙃

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-05-04T17:07:18+00:00

    Good morning fg,

    I just read that reply. We already knew that WU only downloads any new versions. I would think his only alternative is to include the first script from the dump that downloads all the Apps as we currently have, prior to using wimlib. Currently the Apps Integrator is part of wimlib now. You can also get the Integrator on abbodi's script page.

    You might as well use the uup files from the dump. You are going to be in the same boat with the extra downloads of Apps. Thanks to MS I don't see any way around this.

    Regards,

    Hi Johnny,

    I may as well download the whole thing from uupdump for every build, but I was trying to avoid the multiple downloads from W.U. and then from dump to build the ISO.

    Also, there is the other bug with the W.U. loop after upgrading with ISO which was forcing me to use W.U. on every damn machine.

    With so many different downloads I end up going over the data limit set by the ISP. I don't need an extra monthly charge for the amount of data downloaded.

    MS needs to fix the stupid W.U. loop after an ISO upgrade. 😝

    Till then I'll use the workaround with the date change, assuming that it will still work on the next build. 🤐

    Was this answer helpful?

    0 comments
  5. Johnny55 5,155 Reputation points Volunteer Moderator
    2022-05-04T16:41:37+00:00

    Good morning fg,

    I just read that reply. We already knew that WU only downloads any new versions. I would think his only alternative is to include the first script from the dump that downloads all the Apps as we currently have, prior to using wimlib. Currently the Apps Integrator is part of wimlib now. You can also get the Integrator on abbodi's script page.

    You might as well use the uup files from the dump. You are going to be in the same boat with the extra downloads of Apps. Thanks to MS I don't see any way around this.

    Regards,

    Was this answer helpful?

    0 comments