Windows installation fails at ~76%

You're not allowed to remove WinRE if installing W11 24H2 or 25H2. It's expected to be there.
 
You're not allowed to remove WinRE if installing W11 24H2 or 25H2. It's expected to be there.
It doesn't let me remove it anyways. It says it's needed for Windows Setup since 24H2+ on NTLite Notes. Unless you mean it's subcomponents too.
 

Attachments

  • Screenshot 2025-10-19 194022.png
    Screenshot 2025-10-19 194022.png
    192.2 KB
I don't remove WinRE, so haven't been keeping up with recent NTLite updates on it. For the longest time, it was simply one WinRE component.

What you can do is boot (in VM) from the ISO, stop and open a CMD window with Shift-F10. You can try looking in the \Windows\Panther folders, and look at the different setuperr.log files. There might be a clue to why while it failed.
 
I don't remove WinRE, so haven't been keeping up with recent NTLite updates on it. For the longest time, it was simply one WinRE component.

What you can do is boot (in VM) from the ISO, stop and open a CMD window with Shift-F10. You can try looking in the \Windows\Panther folders, and look at the different setuperr.log files. There might be a clue to why while it failed.
I checked the Windows RE subcomponent and i still get the same error. No logs as well.
 

Attachments

  • Screenshot 2025-10-19 202312.png
    Screenshot 2025-10-19 202312.png
    46.6 KB
You can only remove WinRE and all components related with 24h2/25h2 if you are using the legacy setup.
Option Boot/Setup - Legacy in Settings of NTLite (for boot.wim, index 2) for example
 
  • Like
Reactions: baz
You can only remove WinRE and all components related with 24h2/25h2 if you are using the legacy setup.
Option Boot/Setup - Legacy in Settings of NTLite (for boot.wim, index 2) for example
I'm sorry but i can't find such setting. And boot.wim is already with flag 2.
 
Change install.esd to install.wim I suspect you have a compression error.
 
I will try it another time but one way to fix this issue is by using the Windows 10 setup files. I replaced install.esd (Win 10) with my NTLite Win 11 install.esd)
That's what I did last year, in May or June, I think, then I modified the boot.wim (I've been using the 24h2 image since then, but it doesn't change much during the installation).

Mais évidemment, je ne devrais pas avoir à faire ça. J’espère qu’ils corrigeront ce bogue.
What's the bug ?
By removing WinRE, an error is normal if you use the new setup (2nd screen)

And try with .wim, maybe .esd is the problem
 
Change install.esd to install.wim I suspect you have a compression error.
If it was a compression error with install.esd, the Win 10 installer would have also failed because the files are corrupted.
 
If it was a compression error with install.esd, the Win 10 installer would have also failed because the files are corrupted.
Why would they be corrupted ?
Boot.wim is only used until the first boot of the installation.
install.wim/.esd for the following of the installation
 
Just getting started with NTLite so probably a Noob question. Can we not use a fresh ISO download from Microsoft as the base? Does it have to be a DISM captured image? I'm trying to use a bare image and the ISO creates without error but always fails at that 76%. When I look at my edit cache Windows RE is not even listed. I am not removing any components at this point just trying to use it to install all my base applications. Any pointers?
 
Just getting started with NTLite so probably a Noob question. Can we not use a fresh ISO download from Microsoft as the base? Does it have to be a DISM captured image?
No problem using an ISO from MS, even better for starting from scratch.
I'm trying to use a bare image and the ISO creates without error but always fails at that 76%. When I look at my edit cache Windows RE is not even listed. I am not removing any components at this point just trying to use it to install all my base applications. Any pointers?
Regarding your problem, does the installation work when testing the MS ISO directly (without modification) ?
It might be missing a driver (RAID/VMD for example) if it's an OEM PC
 
An install media created from the same ISO installs fine. What I notice is that this install includes a recovery partition. The failed install from the NTLite media does not create a recovery partition.
 
You could try the Boot/Setup - Legacy option in the NTLite Settings page.

You can also attach the preset you're using, removing any personal information beforehand, if there is any.
 
Back
Top