OOBE Update boot loop

Windows 10 User

Active Member
When clean installing Windows 11 Enterprise x64 pt-pt, I'm asked on the OOBE if I want to install updates when I already integrated the latest. If I say so, it restarts with an error screen and asks again if I want to install updates. It stay in this loop forever unless I disconnect the lan cable but then I'm asked if I want to install updates via Wi-Fi and for some reason I'm unable to connect to me network but if I ignore this step and connect the lan cable the install successfully ends and I have internet access. The install takes a lot of time.

Also, after running winver, it states I have the latest build installed but also that I have 21H2 installed when I'm on Windows 11 and not on Windows 10 and there are many things that aren't set when I configured them on NTLite.

I used a 22000.1 Enterprise x64 pt-pt image.
 

Attachments

  • Salvo automaticamente b31d6e78.xml
    30.3 KB
Last edited:

garlin

Active Member
The current releases of W10 and W11 are both "21H2", it's the release date. You can tell the difference by the version:

Windows 10 Enterprise (21H2) x64 - 10.0.19044.1147
Windows 11 Enterprise (21H2) x64 - 10.0.22000.1

OOBE always runs Windows Update now (cannot be skipped) for "critical updates". I wonder if you removing the WinSxS backups in the preset (instead of using DISM cleanup) broke WU. Disabling the network means WU fails and will exit.

I would try again but do not click on WinSxS backups, and restore File Explorer (did you wanted to remove it?).
 
Last edited:

nuhi

NTLite developer
Staff member
Start with a fresh image.
Load your preset.
Remove all those wrong updates, go to Add - Latest Online Updates, OK (don't change or add any other updates for now).
Remove those post-setup commands for activation, it also can have reboots in it, or unsupported behavior.
Apply, process and let us know.
Then you can keep on adding once you have it working, to isolate where the issue is.
 

Windows 10 User

Active Member
The current releases of W10 and W11 are both "21H2", it's the release date. You can tell the difference by the version:

Windows 10 Enterprise (21H2) x64 - 10.0.19044.1147
Windows 11 Enterprise (21H2) x64 - 10.0.22000.1

OOBE always runs Windows Update now (cannot be skipped) for "critical updates". I wonder if you removing the WinSxS backups in the preset (instead of using DISM cleanup) broke WU. Disabling the network means WU fails and will exit.

I would try again but do not click on WinSxS backups, and restore File Explorer (did you wanted to remove it?).

I set File Explorer to be removed on Windows 10 since I think it's a different File Explorer and a File Explorer still works on both Windows 10 and Windows 11. I thought removing WinSxS wouldn't break a thing. But pre-Windows 10 1903 buils didn't have a codename so I don't understand why the first Windows 11 build has one unlike the first Windows 10 builds.

I think we can skip it with unattend xml? can't we?

I don't want to use it.

Start with a fresh image.
Load your preset.
Remove all those wrong updates, go to Add - Latest Online Updates, OK (don't change or add any other updates for now).
Remove those post-setup commands for activation, it also can have reboots in it, or unsupported behavior.
Apply, process and let us know.
Then you can keep on adding once you have it working, to isolate where the issue is.

I always use non-NTLite updates because NTLite not always supports the latest ones and if I use that NTLite setting the CU for .NET Framework 3.5 is missing as well as the DU for SafeOS. By the way, what are PSF files and what's the KB5006118 update? Does one need only the single MSU CU file or both CAB and PSF CU files to have an image with the most recent build?

What about NTLite not removing and configuring some things when I set it to and how to remove Teams?

The post-setup commands supports Windows 11 and it doesn't have reboots in it.

My PC is really slow after installing this OS (and I was hoping installing it would fix this same problem on Windows 10). My PC doesn't support TPM 2.0 and Secure Boot if that matters. This OS is really messed up since after signing into my user account I had a grey screen (the same color as the taskbar's) and even after signing out and signing in I still had this problem. After rebooting the PC and signing into my user account, the taskbar was blinking and I couldn't click its icons since they were disappearing until the taskbar stabilized and I could finally click on them.

If I disable TPM and Secure Boot install requirement while enabling the remove unneeded editions setting and checking boot.wim 2. will I have any problem?
 

garlin

Active Member
There's no need to expand MSU updates, NTLite handles them as-is.

Right now, W11 has no released updates as it shipped this week. Applying W10 packages will only confuse WU, and .NET 4.8 is already there unless you remove it from the image.
 

Windows 10 User

Active Member
There's no need to expand MSU updates, NTLite handles them as-is.

Right now, W11 has no released updates as it shipped this week. Applying W10 packages will only confuse WU, and .NET 4.8 is already there unless you remove it from the image.

KB5004342 is for Windows 11, not Windows 10.
 
Last edited:

garlin

Active Member
KB5004342 is .NET rollup from Aug 2021. RTM doesn't need it, any pre-release updates are already merged into the final image.
 

garlin

Active Member
Any reason you don't use RTM? MCT 11 works for me:
<Version mode="offline">Windows 11 Enterprise (21H2) x64 - 10.0.22000.194 (en-US)</Version>
 

Windows 10 User

Active Member
Any reason you don't use RTM? MCT 11 works for me:
<Version mode="offline">Windows 11 Enterprise (21H2) x64 - 10.0.22000.194 (en-US)</Version>

It's just since I integrate the latest updates it wouldn't make sense not using a .1 build and integrate more than a CU. So you use MCT 11 and not NTLite, after all?
 

garlin

Active Member
MCT is used to download Enterprise builds if you don't have access to the normal channels. You're missing the point.
It's a waste of time updating a pre-release ISO when you can customize the RTM edition in NTLite. RTM is one week old.
 

Windows 10 User

Active Member
MCT is used to download Enterprise builds if you don't have access to the normal channels. You're missing the point.
It's a waste of time updating a pre-release ISO when you can customize the RTM edition in NTLite. RTM is one week old.

I've been advised to always start with the .1 build when integrating updates so in your opinion I should start with the RTM build and integrate the latest CU even if it already has one?
 

garlin

Active Member
Not sure where you've been given this advice. RTM build versions are based on when MSFT picks a RC (release candidate) and blesses it.
The number is entirely arbitrary. It's a build family then increments up RC by RC.

Stop talking CU, there is no W11 CU yet. If you're not convinced by my arguments, figure it out for yourself.

Windows 11 release information

Windows 11 current versions​

(All dates are listed in ISO 8601 format: YYYY-MM-DD)

General Availability Channel​

General Availability Channel

VersionServicing optionAvailability dateLatest revision dateLatest OS buildEnd of service: Home, Pro, Pro Education and Pro for WorkstationsEnd of service: Enterprise, Education and IoT Enterprise
21H2 (original release)
General Availability Channel​
2021-10-042021-10-0422000.1942023-10-102024-10-08
 
Last edited:

Windows 10 User

Active Member
Not sure where you've been given this advice. RTM build versions are based on when MSFT picks a RC (release candidate) and blesses it.
The number is entirely arbitrary. It's a build family then increments up RC by RC.

Stop talking CU, there is no W11 CU yet. If you're not convinced by my arguments, figure it out for yourself.

Windows 11 release information

Windows 11 current versions​

(All dates are listed in ISO 8601 format: YYYY-MM-DD)

General Availability Channel​

General Availability Channel

VersionServicing optionAvailability dateLatest revision dateLatest OS buildEnd of service: Home, Pro, Pro Education and Pro for WorkstationsEnd of service: Enterprise, Education and IoT Enterprise
21H2 (original release)
General Availability Channel​
2021-10-042021-10-0422000.1942023-10-102024-10-08

But if I integrate the latest CUs on the 22000.194 build the image will be bigger than if I do the same thing for the 22000.1 build.
 

Windows 10 User

Active Member
Windows updates roll on Patch Tuesday. Next calendar date is 10/12.

So?

Anyway, I created a new image with NTLite, this time I integrated NTLite's updates (I kept File Explorer, WinSxS backups and the post-setup commands and disabling TPM and Secure Boot install requirement while not enabling the remove unneeded editions setting but checking boot.wim 2) by clicking on "Add", "Latest Online Updates" and the install crashes with an error message while on Hyper-V (it doesn't even reach the stage where it was having the network issue) with a Windows 10 host so should I try clean installing it on the host (like I did before and I had the mentioned network problem)?
 

garlin

Active Member
What you see in NTLite's W11 updates list is bogus.

It wasn't regularly refreshed, unlike the normal W7-W10 lists, because W11 was a moving target before RTM. When Patch Tuesday arrives, nuhi will make the update lists current again.

22000.194 currently has one hotfix for OOBE (KB5007040) as of Sunday night. Just do a clean install, ignore the list.
I have no idea whether the OOBE fix would have helped your first install, but it's more likely from integrating the wrong W10 updates.

MCT->load->NTLite->install->enjoy.

Win7-NTLite-2021-10-10-21-27-39.png
 
Last edited:
Top