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.
Hi fg,
From my German site, this gives us something to go on.
Microsoft seems to have changed something. A new installation ends with the error 0xC0000005 immediately after "Install now" and is not possible. Is due to the UXLIB.DLL. (Thanks to DK2000)
Regards,
This maybe the next block on clean install with Build 25145. 😎
I have no problem on the same box using 25140.
Also, had no problem doing upgrade on the same box using the same 25145 ISO.
Good Morning fg,
I got the same error on attempting total clean install in a compliant vm. The ISO image was fine doing an upgrade as you show. Thinking it was a faulty ISO, re-downloaded, created a new ISO, exact same result.
Perhaps MS is in the process of removing "oobe\bypassnro" as this was only temporarily integrated. IDK
Regards,
Good morning Johnny,
Thanks for confirming the same problem.
We'll see what happens with next build.
I did not have this issue with the MS ISO 25140, but fails solid with 25145.
No problem on a fully compliant box with either one.
This maybe the next block on clean install with Build 25145. 😎
I have no problem on the same box using 25140.
Also, had no problem doing upgrade on the same box using the same 25145 ISO.
Good Morning fg,
I got the same error on attempting total clean install in a compliant vm. The ISO image was fine doing an upgrade as you show. Thinking it was a faulty ISO, re-downloaded, created a new ISO, exact same result.
Perhaps MS is in the process of removing "oobe\bypassnro" as this was only temporarily integrated. IDK
Regards,
The ISO looks the same as mine. It worked fine on a fully compliant box, but not on the non compliant.
As you know, my laptop is yellow zone (non-complaint CPU) so another mistery for you to solve. 😁
I'm done for now, good night!
Good night.
The ISO looks the same as mine. It worked fine on a fully compliant box, but not on the non compliant.
As you know, my laptop is yellow zone (non-complaint CPU) so another mistery for you to solve. 😁
I'm done for now, good night!