Anyone experienced any recent issue with W11 24H ISO's not installing after integrating updates?

[tired-it]

I downloaded a genuine Windows ISO that was updated by Microsoft to the October cumulative update. I recently decided to update some current test ISOs by starting with that October ISO and letting NTLite integrate December updates. Everything seemingly completed fine. Installing the ISO completed up to the point it was about to restart to continue, then it gave this error: 0x80070570.

The error code seemed to suggest that some installation files may have been corrupt so I redid the ISO from the beginning. Same error came out. I tried installing the ISO without integrated updates and it worked fine. So every time I integrate updates through NTLite, the installation of the ISO errors out. I am on the latest version of NTLite.

Extra info: The ISO used was a Windows 11 23H2 "Consumer" ISO.

 

[nuhi]

Hi,

that should not happen.
Please attach the preset (auto saved xml from the resulting updated ISO) to double-check on my side.
Make sure to suspend any antiviruses that might interfere with the process, rarely it happens that they block the mounted directory during image saving.

Also make sure your disk and computer in general are stable.

 

[tired-it]

Hi,

that should not happen.
Please attach the preset (auto saved xml from the resulting updated ISO) to double-check on my side.
Make sure to suspend any antiviruses that might interfere with the process, rarely it happens that they block the mounted directory during image saving.

Also make sure your disk and computer in general are stable.

I only have the preset from when I changed settings after the fact. I'll remake the ISO with updates and post that in a bit to confirm again.

I have Defender off and the Host PC has been fairly stable for months. It's on Windows 11 23H2 too. I refuse to upgrade to 24H2 because of bugs haha.

 

[nuhi]

I only have the preset from when I changed settings after the fact. I'll remake the ISO with updates and post that in a bit to confirm again.

Just curious, why modify twice if it was corrupted?
Or, is this a case of configuring twice in a row, for example first removing something, then integrating updates or similar?
That would also explain it - best is to do all at once, or removals last.

edit: got the preset, removed it from public as it had user/password in it, just in case.
Let me know if you get the issue again, with all presets to replicate the situation.

 

[tired-it]

Just curious, why modify twice if it was corrupted?
Or, is this a case of configuring twice in a row, for example first removing something, then integrating updates or similar?
That would also explain it - best is to do all at once, or removals last.

edit: got the preset, removed it from public as it had user/password in it, just in case.
Let me know if you get the issue again, with all presets to replicate the situation.

Oh whoops. Forgot about that lol. Just been hastile churning out test ISOs for a few days now.

As for the initial question, I originally did not think it was an update issue. Standard process was to start with an untouched ISO, update it, process it and then make changes/tweaks/etc and process that a final time. So I worked backwards and tried undoing some changes.

Usually, when an install errors out, it's an issue with Post-Setup or the Unattended file, but I had no Post-Setup and the Unattended page was the same one used for several months. So... yeah. Eventually got to the updates and realized it installed fine without them.

 

[tired-it]

Hi,

that should not happen.
Please attach the preset (auto saved xml from the resulting updated ISO) to double-check on my side.
Make sure to suspend any antiviruses that might interfere with the process, rarely it happens that they block the mounted directory during image saving.

Also make sure your disk and computer in general are stable.

Alright round 3.. or something. Preset and log attached. Still got the error after attempting install.

 

[lemegapro]

Hello, I have also encountered this error several times. I resolved this error by restarting vmware to reinstall the iso or by just redoing the iso with Ntlite.
I still haven't understood why I had this error, even though I cut the antivirus.
If this can help to move forward on a solution.

 

[tired-it]

I will add that this error only started happening recently as just last month I updated the same ISO to the November cumulative update and installed that fine.

 

[garlin]

Known issue reported on W11 24H2:
Issues might occur with media which installs the October or November update

Workaround: Move ahead to Dec 2024 or later. Gripe if you've already installed a previous Oct 2024 or Nov 2024 image.

When using media to install Windows 11, version 24H2, the device might remain in a state where it cannot accept further Windows security updates. This occurs only when the media is created to include the October 2024, or November 2024, security updates as part of the installation (these updates were released between October 8, 2024 and November 12, 2024).

Please note, this only occurs when utilizing media - such as CD and USB flash drives - to install Windows 11, version 24H2. This issue does not occur for devices where the October 2024 security update or the November 2024 security updates are installed via Windows Update or the Microsoft Update Catalog website.

Workaround: To prevent issues, do not install Windows 11, version 24H2 which installs the October 2024 or November 2024 security updates. Instead, ensure that media used to install Windows 11, version 24H2, includes the December 2024 monthly security update (released December 10, 2024), or later.

Next steps: We are working on a resolution and will provide more information when it is available.

Affected platforms:

Client: Windows 11, version 24H2
Server: None