Solved 24H2 - Unable to install any UUP/DISM ISOs

BolteWasTaken · Dec 31, 2024

Here is what I normally do.

Every so often I download a fresh and up to date ISO from UUPDump.
I install it into a Hyper-V virtual machine and configure it how I want.
I use DISM to capture-image
I use deployment tools to author an ISO as needed.

I do it this way because I like being able to take snapshots in different states for different customers etc and then export the image.
Usually I end up with an ISO that installs everything unattended/correctly without issues.

Tried it on a recent build of 24H2 and during the installing files screen at roughly 10% or so, I get a Windows installation failed confirmation prompt.

First I thought my USB had gone bad, so I tried the base 24H2 ISO, which worked fine.
It seems any UUP or DISM captured/modified ISO causes this error.

I don't want to have to go through my basic customisations/optimisations from scratch on bare metal.

Part of me thinks it relates to the known issue, part of me thinks maybe some security setting is tripping it up?
Any ideas would be helpful.

FreeBooter · Dec 31, 2024

Can you install Windows 11 24H2 without modification also why are not downloading latest Windows 11 24H2 ISO from Microsoft?

Download Windows 11

BolteWasTaken · Dec 31, 2024

FreeBooter said:
Can you install Windows 11 24H2 without modification also why are not downloading latest Windows 11 24H2 ISO from Microsoft?

Download Windows 11

"First I thought my USB had gone bad, so I tried the base 24H2 ISO, which worked fine."

That was one of my troubleshooting steps. I use UUP because it allows me to create an ISO with updates already included, plus whatever version/language I want.

That works on bare metal, however even if I use that in Hyper-V, and configure an image, it fails with the same error. Which makes me think it might not be relating to the known issue.

pseymour · Dec 31, 2024

Not sure which "known issue" you're referring to. Are you removing the Windows.old folder before capturing the image?

BolteWasTaken · Dec 31, 2024

pseymour said:
Not sure which "known issue" you're referring to. Are you removing the Windows.old folder before capturing the image?

Yes, I put a lot of effort into setting up my base image. So I have cleanmgr sageset all setup to run through and remove all that, plus checking that the folders are gone.

The known issues I'm speaking of are the update issues, can't see how that is related to that though considering the regular unmodified ISO is able to install fine.

I even tried using that, not doing ANY updates, just changed a few things and then captured an image. Got the same error when trying to install the captured/modified ISO.

Could it be some security related thing regarding TPM/Secure boot? I usually get prompted for that when launching the ISO, way before I get to the installing files screens.

To clarify, I have been able to use the same procedure on my Nuc without issue for earlier versions (23H2).
But I am now trying to install 24H2 on a newly rebuilt rig. If I try the 23H2 image on the rebuilt rig that might confirm if it's unique to the hardware.

BolteWasTaken · Dec 31, 2024

Ok. Just done further digging here.
I'm going to re-summarize...

Issues installing 24H2 fresh from ANY modified ISO (UUP/DISM/Rufus) - get installation failed prompt.
Standard 24H2 ISO released from Microsoft installs fine.
Installing 23H2 modified ISO (UUP/DISM/Rufus) installs fine.

I wanted to customise a 24H2 image and capture it via DISM before converting it to an ISO.
Seems this can't be done without the installation error prompt with 24H2 currently.
Other than building custom ISO on 23H2 and then once installed on bare metal, updating it fully to 24H2, I don't know of any alternative courses of action until Microsoft fix this.

It has to be a specific issue with 24H2.

Also new with 24H2, although it's a minor annoyance. When capturing an image with 24H2 it by default gets the drive letters wrong, this doesn't happen in 23H2, I've had to select volume/assign letters in all 24H2 versions I've tried.

pseymour · Dec 31, 2024

hsehestedt or garlin might chime in with something helpful. They do this stuff more than I do, I think. I don't think I have sysprepped anything since the XP era, except to test things for this forum.

garlin · Dec 31, 2024

My suggestion is to confirm your sysprepped image installs fine on Hyper-V. If the custom ISO works under Hyper-V, but not on a physical PC, then you've not generalized it correctly and some HW support is messed up.

BolteWasTaken · Jan 1, 2025

garlin said:
My suggestion is to confirm your sysprepped image installs fine on Hyper-V. If the custom ISO works under Hyper-V, but not on a physical PC, then you've not generalized it correctly and some HW support is messed up.

Appreciate the advice, thanks.
The custom ISOs all work in Hyper-V, and all custom ISOs work prior to building an image with 24H2.

I'm not saying you are wrong, but across multiple machines I've never had an issue with this process, except for at the very beginning before I discovered Hyper-V when I was using Virtualbox (that would BSOD if I still had guest additions installed, so I uninstalled it prior to making an image, which then worked).

I've never needed to enter audit mode and sysprep that way.
The outcome after capturing an image with DISM is all Windows settings, customisations, apps etc all installed the same as the VM, with an unattended installation - working on bare metal.

garlin · Jan 3, 2025

I will assume you're technical enough to try this:

1. 24H2 WinPE Setup isn't really the same client as before, but you can try forcing WinPE to use the legacy Setup.
2. Make a backup copy of your ISO's boot.wim.

3. Mount boot.wim, and modify the SYSTEM registry.

Code:

DISM /Mount-Wim /WimFile:E:\sources\boot.wim /Index:2 /MountDir:C:\Mount

reg load HKLM\TEMP C:\Mount\Windows\System32\config\SYSTEM
reg add HKLM\TEMP\Setup /v CmdLine /t REG_SZ /d "cmd /c start /min wpeinit && \sources\setup" /f
reg unload HKLM\TEMP

DISM /Unmount-Wim /MountDir:C:\Mount /Commit

4. Now boot from the ISO, it should be running the old Setup. If that doesn't work, revert to the backup copy of boot.wim.

BolteWasTaken · Jan 3, 2025

garlin said:
I will assume you're technical enough to try this:

1. 24H2 WinPE Setup isn't really the same client as before, but you can try forcing WinPE to use the legacy Setup.
2. Make a backup copy of your ISO's boot.wim.

3. Mount boot.wim, and modify the SYSTEM registry.

Code:

DISM /Mount-Wim /WimFile:E:\sources\boot.wim /Index:2 /MountDir:C:\Mount reg load HKLM\TEMP C:\Mount\Windows\System32\config\SYSTEM reg add HKLM\TEMP\Setup /v CmdLine /t REG_SZ /d "cmd /c start /min wpeinit && \sources\setup" /f reg unload HKLM\TEMP DISM /Unmount-Wim /MountDir:C:\Mount /Commit

4. Now boot from the ISO, it should be running the old Setup. If that doesn't work, revert to the backup copy of boot.wim.

Yep, I'm technical enough for that.
I'm almost done re-doing a 23H2 image. After a snapshot I'm going to then update it to 24H2.

I was considering using the 23H2 DISM to capture the image, and then use OSC to author the ISO.

This is also another option I can try, I didn't think of replacing the boot.wim. Thanks!

garlin · Jan 3, 2025

Technically you're not replacing boot.wim, but updating the CmdLine reg key that winpeshl.exe checks for. Some users have claimed the new client breaks whatever they were doing before.

BolteWasTaken · Jan 3, 2025

garlin said:
Technically you're not replacing boot.wim, but updating the CmdLine reg key that winpeshl.exe checks for. Some users have claimed the new client breaks whatever they were doing before.

Interesting. I will give that a shot. That's potentially the reason I get installation failed error prompt at around 10% in on the new client.

BolteWasTaken · Jan 5, 2025

Ok.

I have done some experimentation, my findings are:

1. I can use DISM from the 23H2 WinPE, this installs correctly, however because it's an outdated UEFI bootloader it requires Secure Boot to be disabled (at least that's what Rufus complains of).
2. I can use DISM from the 24H2 WinPE (ISO from UUP Dump) and by using the reg tweaks to the Boot.wim, can confirm the legacy WinPE client is indeed loaded.

I just have final touches to make to my proper ISO, and I will be able to test on bare metal and make a final confirmation of resolution.

BolteWasTaken · Jan 7, 2025

@garlin

Thank you, that all works fine now with the old client.

Solved 24H2 - Unable to install any UUP/DISM ISOs

Member

My Computers

Well-known member

My Computer

Member

My Computers

Windows developer and admіn

My Computers

Member

My Computers

Member

My Computers

Windows developer and admіn

My Computers

Well-known member

My Computer

Member

My Computers

Well-known member

My Computer

Member

My Computers

Well-known member

My Computer

Member

My Computers

Member

My Computers

Member

My Computers

Similar threads