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.
Good Morning fg,
The SV2 line is only used on Dev channel, so not sure now that it has moved to Beta how that will play out. The SV1 line is used on RP versions, eventually making its way to Release I would assume.
Regards,
SVI is used for 22000.588
SV2 is used for 22581.1
But in both cases they show the watermark notification just while in R.P. 🤷♂️
Good Morning fg,
The SV2 line is only used on Dev channel, so not sure now that it has moved to Beta how that will play out. The SV1 line is used on RP versions, eventually making its way to Release I would assume.
Regards,
Hi Johnny,
After a clean install of 22581 on this laptop.
Here is that watermark notification that I was getting in Release Preview, after I switched to Dev it went away without changing SV2 to 0.
Looks like those SV1 and SV2 DWORDS are only affecting R.P. 😎
Release Preview Channel:
Dev Channel:
Hi Johnny,
I just did an upgrade from 19044.1620 to 22581.1 using that ISO that I downloaded earlier.
Everything worked fine.
Next check with W.U. downloaded these updates below.
No loop on W.U, nor error 0xc1900401. 👍
The list of installed Apps is quite extensive and includes the updated SecHealthUI. 😉
Microsoft.SecHealthUI Microsoft.SecHealthUI_1000.22581.1.0_x64__8wekyb3d8bbwe
Probably your original PC had the Home Edition saved in the BIOS.
I can easily extract just the install.wim for Pro and make and ISO or an installation USB with just Pro.
Exactly, it came pre-loaded with Home Edition Single Language from Lenovo.
Good for you! IDK how to do that and not really in the mood to learn yet another procedure. 😉