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

Hi Johnny,

The Apps folder is copied in here C:\Windows\SoftwareDistribution\Download\96f67d863d4234d4823cdee8752abeee

As I said earlier, some basic windows Apps are not updated from the MS Store, so if I use the Apps folder downloaded from a previous build I may end up with an old version of some Apps.

If I use the Apps folder from this Build 22610 to create the ISO with the next download, I will have to verify if SecHealthUI gets updated or if it stays at 22610. 😎

Adding Apps . . .

Microsoft.NET.Native.Framework.x64.1.3

Microsoft.NET.Native.Framework.x64.1.7

Microsoft.NET.Native.Framework.x64.2.2

Microsoft.NET.Native.Runtime.x64.1.4

Microsoft.NET.Native.Runtime.x64.1.7

Microsoft.NET.Native.Runtime.x64.2.2

Microsoft.UI.Xaml.x64.2.1

Microsoft.UI.Xaml.x64.2.3

Microsoft.UI.Xaml.x64.2.4

Microsoft.UI.Xaml.x64.2.7

Microsoft.VCLibs.x64.14.00

Microsoft.VCLibs.x64.14.00.Desktop

Microsoft.WindowsStore_8wekyb3d8bbwe

Microsoft.StorePurchaseApp_8wekyb3d8bbwe

microsoft.windowscommunicationsapps_8wekyb3d8bbwe

Microsoft.People_8wekyb3d8bbwe

Microsoft.BingNews_8wekyb3d8bbwe

Microsoft.BingWeather_8wekyb3d8bbwe

Microsoft.MicrosoftSolitaireCollection_8wekyb3d8bbwe

Microsoft.ZuneMusic_8wekyb3d8bbwe

Microsoft.ZuneVideo_8wekyb3d8bbwe

Microsoft.WindowsAlarms_8wekyb3d8bbwe

Microsoft.WindowsCalculator_8wekyb3d8bbwe

Microsoft.WindowsNotepad_8wekyb3d8bbwe

Microsoft.WindowsTerminal_8wekyb3d8bbwe

Microsoft.WindowsFeedbackHub_8wekyb3d8bbwe

Microsoft.GetHelp_8wekyb3d8bbwe

Microsoft.WindowsSoundRecorder_8wekyb3d8bbwe

Microsoft.MicrosoftOfficeHub_8wekyb3d8bbwe

Microsoft.ScreenSketch_8wekyb3d8bbwe

Microsoft.MicrosoftStickyNotes_8wekyb3d8bbwe

Microsoft.Todos_8wekyb3d8bbwe

Microsoft.XboxSpeechToTextOverlay_8wekyb3d8bbwe

Microsoft.GamingApp_8wekyb3d8bbwe

Microsoft.XboxGameOverlay_8wekyb3d8bbwe

Microsoft.XboxGamingOverlay_8wekyb3d8bbwe

Microsoft.XboxIdentityProvider_8wekyb3d8bbwe

Microsoft.Xbox.TCUI_8wekyb3d8bbwe

Microsoft.Getstarted_8wekyb3d8bbwe

Microsoft.Windows.Photos_8wekyb3d8bbwe

Microsoft.WindowsMaps_8wekyb3d8bbwe

Microsoft.PowerAutomateDesktop_8wekyb3d8bbwe

Microsoft.WindowsCamera_8wekyb3d8bbwe

Microsoft.DesktopAppInstaller_8wekyb3d8bbwe

Microsoft.Paint_8wekyb3d8bbwe

Microsoft.WebMediaExtensions_8wekyb3d8bbwe

Microsoft.RawImageExtension_8wekyb3d8bbwe

Microsoft.HEIFImageExtension_8wekyb3d8bbwe

Microsoft.HEVCVideoExtension_8wekyb3d8bbwe

Microsoft.VP9VideoExtensions_8wekyb3d8bbwe

Microsoft.WebpImageExtension_8wekyb3d8bbwe

MicrosoftWindows.Client.WebExperience_cw5n1h2txyewy

Microsoft.SecHealthUI_8wekyb3d8bbwe

Clipchamp.Clipchamp_yxz26nhyzhsrt

MicrosoftCorporationII.QuickAssist_8wekyb3d8bbwe

Microsoft.YourPhone_8wekyb3d8bbwe

Microsoft.549981C3F5F10_8wekyb3d8bbwe

MicrosoftCorporationII.MicrosoftFamily_8wekyb3d8bbwe

Deployment Image Servicing and Management tool

Version: 10.0.22598.1

See the size difference below for Windows 11 Pro 22610 ISO files.

1st file was a download from uup-dump, second one was created with converter 79f from

C:\Windows\SoftwareDistribution\Download\96f67d863d4234d4823cdee8752abeee

with the Apps folder added in.

Second file worked on clean install, will see on next build if I keep the same Apps folder of 22610.

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. 😝

Weird indeed, but with so many variables, nobody else interested and silence from MS,

we'll never get to the bottom of it.

We need upvotes on the feedback reports.

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. 😝

Weird indeed, but with so many variables, nobody else interested and silence from MS,

we'll never get to the bottom of it.

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. 😏🤣