Clean Install of Windows 11 Ni Preview Build works with Build 22557, but not with 22563, 22567, 22572, 22581, 22593, 25115

Anonymous

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.

0 comments

232 answers

Anonymous

2022-05-08T04:46:15+00:00

Hi again,

Here is the update history for the old Legacy Bios XPS 8300 from 22581 to 22616 all done with W.U. still working fine. 😉
Was this answer helpful?

0 comments No comments
Anonymous

2022-05-07T19:41:43+00:00
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\PCHC]

"UpgradeEligibility"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig]

"BypassTPMCheck"=dword:00000001

"BypassSecureBootCheck"=dword:00000001

"BypassRAMCheck"=dword:00000001

"BypassStorageCheck"=dword:00000001

"BypassCPUCheck"=dword:00000001

"BypassDiskCheck"=dword:00000001

Hope you get this sorted. I have used WU to upgrade non-compliant devices as well.

Regards,

Hi Johnny,

I did not know about PCHC. 😎 It doesn't seem to make a difference if I leave it set to 0.

I was using a slightly different method with my Legacy Bios boxes depending on what Build I'm updating from.

I use the LabConfig only when I do a clean install, only first 2 lines needed in my case.

"BypassTPMCheck"=dword:00000001

"BypassSecureBootCheck"=dword:00000001

For update/upgrade in place I just hide AppraiserRes.dll renaming it AppraiserRes.dll.bak and replace Appreiser.dll with the old one from 22504.

That does it if I start with a system already in an insider channel.

(IE: 19044.1682 in R.P., 22000.652 in R.P. or a previous Build already in Dev channel)

I use the same method with W.U. When it stops with the error message after downloading about 8% I just change the same 2 files in C:$Windows.~BT\sources and then hit fix or just retry and the download takes off again, W.U. upgrade completes normally after that.

The problem I have with the latest 2 Builds is switching to Dev channel after clean install, because the default clean install is no longer setup for insider, there are too many entries to change in WindowsSelfHost.

Also, I could never switch to Beta with an unsupported box, because it reverts back to R.P. 🤷‍♂️

(Had to use the OfflineInsiderEnroll script for that, but I try to avoid it if I can)

No problem going from R.P. to Dev without using the script.

Edit:

Tried again upgrade with W.U. from 22610 to 22616 on a red zone Legacy Bios box, I verified that I can get the same result, by leaving the appraiser.dll alone in C:$Windows.~BT\sources and instead just replacing AppraiserRes.dll with an empty one made as you suggested.

After that I just hit Fix and the operation resumes with the message below.

I can just close it or wait till it is closes automatically after 2 minutes, the download and upgrade proceed normally.
```
[![Image](https://learn-attachment.microsoft.com/api/attachments/ba0617fe-2091-48dd-a807-4113274f7a0c?platform=QnA
```
I don't need any of the Registry changes for the upgrade via W.U. either.

And this message is from 19044.1682 R.P. to 22616.1 With ISO on a red zone box:

Again with 25126. 🤣
Was this answer helpful?

0 comments No comments
Anonymous

2022-05-07T16:58:00+00:00

Hi Johnny,

Yeah thanks, I know how to bypass the blocks but didn't have to use them.

I can update using WU as well, but I can't do an in-place as I used to until this build.
Was this answer helpful?

0 comments No comments
Johnny55 5,155 Reputation points Volunteer Moderator

2022-05-07T16:42:45+00:00

btw, I just found out that starting with this build I cannot update/repair in-place anymore (yellow zone). 😒

Hi Sibro,

All my non-compliant vm's and spare old laptop all upgraded without issue. For the "AppraiserRes.dll" file, I used a blank txt file and renamed it to AppraiserRes.dll in Sources. My bypass.reg file:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\PCHC]

"UpgradeEligibility"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig]

"BypassTPMCheck"=dword:00000001

"BypassSecureBootCheck"=dword:00000001

"BypassRAMCheck"=dword:00000001

"BypassStorageCheck"=dword:00000001

"BypassCPUCheck"=dword:00000001

"BypassDiskCheck"=dword:00000001

Hope you get this sorted. I have used WU to upgrade non-compliant devices as well.

Regards,
Was this answer helpful?

0 comments No comments
Anonymous

2022-05-07T15:44:51+00:00

MS never went down that path, probably because it would require some extra testing on their part. 🤐

Correct but they used to release ISOs more often, at least once a month during the W10 early days.

I don't think it is because of extra testing but rather their need for collecting data during WU updates.

btw, I just found out that starting with this build I cannot update/repair in-place anymore (yellow zone). 😒
Was this answer helpful?

0 comments No comments