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

Hi Sibro,

The weird thing about the error 0xc1900401 and the W.U. loop is that when you first reported it and opened a thread on that problem, I was not getting it except in specific cases very intermittently, now you don't see it anymore and instead I see it every time I upgrade with ISO from previous 22H2 build. 😝

Johnny saw it intermittently and suggested to wait 24 hours to see it clearing on its own.

The whole thing doesn't make much sense, but with MS nothing ever does. 🤐

Anyway, I can reproduce the problem consistently on different machines and found a different workaround to clear the error as described in my previous post.

Error 0xc1900401 has several FBH reports which are not specific to this case that started with the Ni builds, but perhaps they are all related, who knows?

It is quite annoying and needs to be fixed in W.U.

https://aka.ms/AAgc8c2

Hi Johnny,

I found another workaround to clear the W.U. loop and error 0xc1900401 without waiting.

I change the time set from automatic to manual, back 2 days on the date and reboot, next W.U. check for update runs clean and also the errors that were logged in update history just disappear.

I then set the date back to automatic and get the correct date and time again and reboot, the loop with W.U. and the errors are magically gone. 🤣🤣🤣🤣🤣

The update to 22610 does not show in the history since it was done with the ISO.

Edition Windows 11 Pro

Version 22H2

Installed on ‎5/‎1/‎2022

OS build 22610.1

Experience Windows Feature Experience Pack 1000.22632.1000.0

....

It sure shows in history on the one that was upgraded by W.U.

It is still an annoying bug; we should not have to wait or use workarounds to fix something they just screwed up with W.U.

We have done updates and upgrades with ISO for years without any of this B.S. 😝

https://aka.ms/AAgc8c2

Reproduced again on a different machine:

Fixed it with the same workaround, putting date back two days reboot check for updates cleared the error, then set date back to automatic, reboot, problem gone, and error cleared from history. 😏🤣

The sign in options were showing before the sign in to MSA screen, now they show after the screen asking to sign in.

To the best of my recollection, it has been the same since build 22563 or thereabouts.

On the same page the choice to sign in with MSA or Sign-in options, then you can select offline account

Perhaps, but there is an extra screen before getting to "Let's add your account"

Previously it was getting to that one directly.

I only see this one below on latest Ni Builds, not on 22000.xxx nor on 22504.1

22504.1 goes directly to this screen without showing the one above.

Also, the wording here was "Let's add you Microsoft account" instead of "Let's add your account"

I did so many clean installs and I just noticed the differences in the flow of the screens without knowing any valid reason for the changes. 🤐

The sign in options were showing before the sign in to MSA screen, now they show after the screen asking to sign in.

To the best of my recollection, it has been the same since build 22563 or thereabouts.

On the same page the choice to sign in with MSA or Sign-in options, then you can select offline account

The loop on W.U. is pretty consistent on all my machines except for the cases I listed.

What can I say? 🤷‍♂️

On clean install the sign-in options to use an offline account has been moved after the Sign in with MSA screen, but it still gives the choice for an offline account.

I don't see that either, looks the same as always to me. 🤷‍♂️

You are probably using a different setup.exe.

The sign in options were showing before the sign in to MSA screen, now they show after the screen asking to sign in.