This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
The sign in options were showing before the sign in to MSA screen, now they show after the screen asking to sign in.
To the best of my recollection, it has been the same since build 22563 or thereabouts.
On the same page the choice to sign in with MSA or Sign-in options, then you can select offline account
The sign in options were showing before the sign in to MSA screen, now they show after the screen asking to sign in.
To the best of my recollection, it has been the same since build 22563 or thereabouts.
On the same page the choice to sign in with MSA or Sign-in options, then you can select offline account
Perhaps, but there is an extra screen before getting to "Let's add your account"
Previously it was getting to that one directly.
I only see this one below on latest Ni Builds, not on 22000.xxx nor on 22504.1
22504.1 goes directly to this screen without showing the one above.
Also, the wording here was "Let's add you Microsoft account" instead of "Let's add your account"
I did so many clean installs and I just noticed the differences in the flow of the screens without knowing any valid reason for the changes. 🤐
Hi Johnny,
I found another workaround to clear the W.U. loop and error 0xc1900401 without waiting.
I change the time set from automatic to manual, back 2 days on the date and reboot, next W.U. check for update runs clean and also the errors that were logged in update history just disappear.
I then set the date back to automatic and get the correct date and time again and reboot, the loop with W.U. and the errors are magically gone. 🤣🤣🤣🤣🤣
The update to 22610 does not show in the history since it was done with the ISO.
Edition Windows 11 Pro
Version 22H2
Installed on 5/1/2022
OS build 22610.1
Experience Windows Feature Experience Pack 1000.22632.1000.0
....
It sure shows in history on the one that was upgraded by W.U.
It is still an annoying bug; we should not have to wait or use workarounds to fix something they just screwed up with W.U.
We have done updates and upgrades with ISO for years without any of this B.S. 😝
Reproduced again on a different machine:
Fixed it with the same workaround, putting date back two days reboot check for updates cleared the error, then set date back to automatic, reboot, problem gone, and error cleared from history. 😏🤣
Hi Sibro,
The weird thing about the error 0xc1900401 and the W.U. loop is that when you first reported it and opened a thread on that problem, I was not getting it except in specific cases very intermittently, now you don't see it anymore and instead I see it every time I upgrade with ISO from previous 22H2 build. 😝
Johnny saw it intermittently and suggested to wait 24 hours to see it clearing on its own.
The whole thing doesn't make much sense, but with MS nothing ever does. 🤐
Anyway, I can reproduce the problem consistently on different machines and found a different workaround to clear the error as described in my previous post.
Error 0xc1900401 has several FBH reports which are not specific to this case that started with the Ni builds, but perhaps they are all related, who knows?
It is quite annoying and needs to be fixed in W.U.
The weird thing about the error 0xc1900401 and the W.U. loop is that when you first reported it and opened a thread on that problem, I was not getting it except in specific cases very intermittently, now you don't see it anymore and instead I see it every time I upgrade with ISO from previous 22H2 build. 😝
Weird indeed, but with so many variables, nobody else interested and silence from MS,
we'll never get to the bottom of it.