UUP Dump 25H2 ISO's installing as 24H2 After MicroWin

[technub1]

Issue Checklist

• I checked for duplicate issues.
• I searched for existing discussions.
• I checked for an existing pull request that addresses this issue.

Provide a clear and concise description of the issue.

Windows 11 25H2 ISO's (mine I specifically downloaded from UUP Dump, but could be from other sources as well) are installing as 24H2 after being run through MicroWin. Issue still exists as of 2/17/2026.

Steps to reproduce the issue.

1. Download Windows 11 25H2 ISO via UUP Dump and their automated scripts
2. Feed the ISO to the MicroWin utility
3. Use the MicroWin-tweaked ISO and install in a VM and it shows 24H2 as the system version

Paste the full error output (if available).

No response

Additional context.

This was an issue that seems to have carried over from the WinUtil integration. The only issue I could find on the WinUtil github mentioned that 24H2 was being hardcoded into some scripts and was forcing Windows to install as 24H2 no matter what. Not sure how accurate that is.

Can anymore insight be provided per the code as to why this is occurring and if it can be fixed?

[Real-MullaC]

Issue Checklist

* [x]  I checked for duplicate issues.[x]  I searched for existing discussions.[x]  I checked for an existing pull request that addresses this issue.

Provide a clear and concise description of the issue.

Windows 11 25H2 ISO's (mine I specifically downloaded from UUP Dump, but could be from other sources as well) are installing as 24H2 after being run through MicroWin. Issue still exists as of 2/17/2026.

Steps to reproduce the issue.

1. Download Windows 11 25H2 ISO via UUP Dump and their automated scripts

2. Feed the ISO to the MicroWin utility

3. Use the MicroWin-tweaked ISO and install in a VM and it shows 24H2 as the system version

Paste the full error output (if available).

No response

Additional context.

This was an issue that seems to have carried over from the WinUtil integration. The only issue I could find on the WinUtil github mentioned that 24H2 was being hardcoded into some scripts and was forcing Windows to install as 24H2 no matter what. Not sure how accurate that is.

Can anymore insight be provided per the code as to why this is occurring and if it can be fixed?

Have you got any pictures of this please? So I can help diagnose this issue.

[technub1]

Have you got any pictures of this please? So I can help diagnose this issue.

I don't know how I could provide enough pictures that would point out the issue. A video would be the best option, but that would be a pretty large video to show the entire process of installing an unmodified 25H2 ISO versus a MicroWin 25H2 ISO.

Or it would have to be a lot of pictures to show the sequence of events.

Are there any logs I could grab from Windows after the MicroWin-modified ISO is installed or something?

[Real-MullaC]

Have you got any pictures of this please? So I can help diagnose this issue.

I don't know how I could provide enough pictures that would point out the issue. A video would be the best option, but that would be a pretty large video to show the entire process of installing an unmodified 25H2 ISO versus a MicroWin 25H2 ISO.

Or it would have to be a lot of pictures to show the sequence of events.

Are there any logs I could grab from Windows after the MicroWin-modified ISO is installed or something?

Can you send me a picture where it shows 24H2 as the system version please.

[technub1]

Can you send me a picture where it shows 24H2 as the system version please.

[seanh1995]

i think this issue is a UUP Dump issue and not a micowin. i think UUP Dump download a 24H2 version off the iso for u instead off the 25H2 iso. u should try downloading the windows iso from ms

[alenbonk]

This used to happen with old microwin too like when it was with winutil
What I suspect is microwin removes the enablement package of 25h2
The security updates are present but enablement is not added
I think u should check this option in iso building from uup "Run component cleanup (Windows converter only)" and try

[technub1]

Yeah, it looks like it's an issue with UUP Dump and how they handle their updates after install, or how WinUtil changes it. I just ran Microwin on an ISO from Microsoft and it installed as 25H2 in Virtualbox. Good to know for the future.

[technub1]

@alenbonk I also make sure to check "Run component cleanup" when downloading each download package. That's not the issue. Something else, but don't know what.

[alenbonk]

What I did was get iso from Microsoft
Then update the iso from WIN10UI by downloading packages from uup then run this iso through microwin this keeps the version intact
Followed this guide

[technub1]

@alenbonk So Microsoft's ISO is pretty up to date already. I think theirs was .7840 when i tested (having it auto-install updates during first boot), and the latest UUP Dump offered was .7921. So not a big difference. Just running the latest Microsoft ISO through Microwin does a good enough job.

And a Microwin ISO seems to do ok in Virtualbox, but i found that there were SATA driver issues installing it on a physical box. But I can make that a different issue.

[zoicware]

ive had users report a similar issue when using a uup dump iso with my tool... i havent really bothered to dive into it but there is some complication with how UUP dump script builds the ISO and then having another tool modify the ISO

by any chance are you customizing the uup dump package (editing the config.ini etc) if you are could you send the options you choose