OOBE Update boot loop

W

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 stays 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 said:
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.

View attachment 5683
Click to expand...

That's what I thought, hence integrating my own updates.

I'm using UUP Dimp to get the ISOs but I think not integrating files won't fix all the issues I'm having.
 
There's two release tracks for Windows images: RTM and interim builds from Insider or MSDN.

The interim builds are official, but already have been updated by MSFT with integrated patches. They are provided to VARs and developers for software testing and not for image customizations. When a new build arrives, testers re-install from scratch.

UUP recreates this process, it's intended to re-assemble any one of the interim builds. It's not ideal for downloading RTM.
Using a non-RTM image will cause NTLite headaches. UUP is for sneaking early access, W11 is now out.
 
garlin said:
There's two release tracks for Windows images: RTM and interim builds from Insider or MSDN.

The interim builds are official, but already have been updated by MSFT with integrated patches. They are provided to VARs and developers for software testing and not for image customizations. When a new build arrives, testers re-install from scratch.

UUP recreates this process, it's intended to re-assemble any one of the interim builds. It's not ideal for downloading RTM.
Using a non-RTM image will cause NTLite headaches. UUP is for sneaking early access, W11 is now out.
Click to expand...

Ok, but I think I'll have some of these problems even with an official untouched RTM image because my PC doesn't fulfill some requirements.
 
Some of the bypasses didn't work for my VM setup, this did:

1. Save your final W11 image, but don't make an ISO.
2. Extract W10 ISO to a folder, replace the sources\install.wim with your W11 version and copy over autounattend.xml to the top folder.
3. Make a new ISO from the W10 folder.

W10 doesn't have any checks, and it works as long as the image format is compatible. My VM has 4GB, no TPM or SecureBoot.
This is no different from other folks who use W10 WinPE to install W7 - W10 images.
 
garlin said:
Some of the bypasses didn't work for my VM setup, this did:

1. Save your final W11 image, but don't make an ISO.
2. Extract W10 ISO to a folder, replace the sources\install.wim with your W11 version and copy over autounattend.xml to the top folder.
3. Make a new ISO from the W10 folder.

W10 doesn't have any checks, and it works as long as the image format is compatible. My VM has 4GB, no TPM or SecureBoot.
This is no different from other folks who use W10 WinPE to install W7 - W10 images.
Click to expand...

Should I use a custom made Windows 10 ISO or an untouched one, and if so, which one (which build, etc.)? I don't have an autounattend.xml file.

I don't know about the latter. I just know that I can't properly use Win10XPE with a Windows 10 ISO on YUMI on the same USB device.
 
Any W10 ISO will do since you're replacing the install.wim, but a clean one is zero risks. If you added drivers to your W11, then integrate the same drivers to W10 boot.wim. autounattend file is optional, but some people forget to copy it.

Think of it as a virus. You flashed a W10 ISO with a replaced W11 payload.
 
garlin said:
Any W10 ISO will do since you're replacing the install.wim, but a clean one is zero risks. If you added drivers to your W11, then integrate the same drivers to W10 boot.wim. autounattend file is optional, but some people forget to copy it.

Think of it as a virus. You flashed a W10 ISO with a replaced W11 payload.
Click to expand...

Even if it works it doesn't make sense having to do this every time I want to install Windows 11 and I may even have problems after doing this, even though I may not have this specific OOBE problem.
 
No more excuses. Latest NTLite supports the TPM bypass directly in Settings. WU has pushed the first CU to W11, and the updates list is now ready to download. This is as push-button as it gets.
 
You must log in or register to reply here.
Back
Top