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-06-23T19:27:19+00:00

Hi guys,

I tried replacing "Uxlib.dll" from previous build 25140 into 25145 and got same error. Looks like we wait till next week's build. No issue using ISO for doing upgrades, only on clean installs.

Regards,

Yes, I tried the same with the same results.

Thanks.
Was this answer helpful?

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

2022-06-23T19:24:08+00:00

Hi guys,

I tried replacing "Uxlib.dll" from previous build 25140 into 25145 and got same error. Looks like we wait till next weeks build. No issue using ISO for doing upgrades, only on clean installs.

Regards,
Was this answer helpful?

0 comments No comments
Anonymous

2022-06-23T19:20:06+00:00

@Sibro.o, @Johnny_55,

F.Y.I.

I tried to do a clean install on my Lenovo Yoga 920 which meets all the windows 11 requirements, and I got the same error.

So, it not just on non-compliant boxes, they clearly screwed up something that is affecting also fully compliant machines.

It works fine on my Dell XPS 8930 and XPS 8940 desktops but fails solid on the Lenovo Yoga 920 Laptop which I use regularly with Build 22000.739.

Sound like the typical MS inconsistency. 🤣🤣

https://aka.ms/AAhbcsh
Was this answer helpful?

0 comments No comments
Anonymous

2022-06-23T19:17:58+00:00

Thanks,

Good to know that I'm not alone, looks like the Germans got that problem too.

YW

I wish I had a fully compliant device to test this.

As it is, I'm the one alone here, not getting the error on a non-compliant laptop. 🤷‍♂️
Was this answer helpful?

0 comments No comments
Anonymous

2022-06-23T18:24:39+00:00

I tried on a VM which obviously has the same non-compliant CPU as the laptop and got the error.

Then I tried one more time on the laptop and didn't get it. The only difference between the two is that the laptop has hardware TPM 2.0 but the VM uses soft TPM (managedvm.autoAddVTPM="software").

No hacks were used on the laptop except for oobe\bypassnro but that is after installation.

Thanks,

Good to know that I'm not alone, looks like the Germans got that problem too.
Was this answer helpful?

0 comments No comments