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.
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?
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?
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
As for 22000.647 was found referenced in some server, but not a released update. Maybe next Tuesday there will be the build update?
This seems to be a mistake:
Select language for Update for Windows 11 - KB4023057 (22000.647) amd64 - UUP dump
That's where I took the previous pic from, doesn't seem like a mistake, more like MS aborted the updates.
Thanks, we'll see what happens Tuesday. 👍
As for 22000.647 was found referenced in some server, but not a released update. Maybe next Tuesday there will be the build update?
This seems to be a mistake:
Select language for Update for Windows 11 - KB4023057 (22000.647) amd64 - UUP dump
That's where I took the previous pic from, doesn't seem like a mistake, more like MS aborted the updates.
Thanks, we'll see what happens Tuesday. 👍
kb4023057 is not tied to a specific build, it is just a cleanup preparing for next update.
It is reused over and over. Looks like the same kb# is reused every month. 🙃
I got that kb4023057 with W.U. on all the public builds a few days ago. Windows 10 and Windows 11 got the same kb#.
Came down on the same date in 19044.1620 and 22000.593.
I got that kb4023057 with W.U. on all the public builds a few days ago. Windows 10 and Windows 11 got the same kb#.
I'm not getting it on 22000.593 hence my original question but thanks for the explanation anyway. 👍