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)
Split from this thread.
@Sibro,
The install.wim in the MS ISO is too big to fit on a FAT32, so I will have to convert it to install.esd. ��♂️
Above the FAT32 limit of 4,294,967,296
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 Sibro,
Reproduced this error again using MS ISO to upgrade from 22572 to 22579, used the recommended way, letting it check for updates normally.
It still ended up with the W.U. loop and error 0Xc1900401.
I submitted a FBH report with recording.
Needs upvotes. 😉
Build 22579+, W.U. gets error 0Xc1900401 after Upgrading from 22572 to 22579 using MS official ISO, the error keeps repeating on every retry.
Must be the .Ni builds, didn't we established that already?Never anything established with MS, don't you know that? 🤣🤣🤣🤣🤣
Inconsistency seems to be the norm.
Touché!
Because when I did 22572 to 22579 it got the same bug even allowing to check for updates.
So, it is not just when refusing the updates, something else is causing the same issue.
Must be the .Ni builds, didn't we established that already?
Never anything established with MS, don't you know that? 🤣🤣🤣🤣🤣
Inconsistency seems to be the norm.
So? what's the problem? do you need/want a password?
That's how I do clean installs, I don't need a password, at least not at first.
Then when I need to add an MS account, be it Mail or the WIP, I chose for 'apps only'
Yes, I want the password for the offline account, always done it that way it is different than the one used for the MS account.
The behavior changed because they just did not even ask as they always did before. 🤣
It is the same as always.
If you type a password you get the questions (something I've never done), if you click next with the box empty, it means you don't want a password and setup continues without asking.
Yes, I just repeated with the same installation media and this time it worked normally.
No idea why yesterday it skipped asking for the password and then it was stuck for minutes, I saw it working on the disk and nothing happened for several minutes.
When I did it just now it worked normally and no delays just the normal behavior.
Because when I did 22572 to 22579 it got the same bug even allowing to check for updates.
So, it is not just when refusing the updates, something else is causing the same issue.
Must be the .Ni builds, didn't we established that already?