search

ventoy / Ventoy

A new bootable USB solution.
https://www.ventoy.net
GNU General Public License v3.0
62.78k stars 4.09k forks source link

[ISSUE] Win11 24H2 installation encountered an unexpected error error code 0x80070001-0x4002f #2887

Open SM-03 opened 4 months ago

SM-03 commented 4 months ago

Official FAQ

Ventoy Version

1.0.99

What about latest release

Yes. I have tried the latest release, but the bug still exist.

Try alternative boot mode

Yes. I have tried them, but the bug still exist.

BIOS Mode

UEFI Mode

Partition Style

GPT

Disk Capacity

16GB

Disk Manufacturer

SanDisk

Image file checksum (if applicable)

None

Image file download link (if applicable)

https://uupdump.net/

What happened?

Problem with the new Windows 11 24H2 installer with Ventoy

I tried latest ventoy 1.0.99 with FAT, Ex-FAT & NTFS formatted. Secure boot enabled, partition style GPT, while trying to clean install Windows 11 Pro 26100.863 24H2 x64, it gave me this error while processing to the disk selection screen

Windows installation encountered an unexpected error error code 0x80070001-0x4002f

Image here

Then I read some discussion here in this thread & select the MBR partition in ventoy & re-format the pen drive, then this issue doesn't occur & the installer processed further to the next disk selection screen

Then I tried Rufus' latest version v4.5 & using the default Rufus combination (GPT+UEFI+NTFS) to make the SAME PD bootable with the same ISO I tried earlier, & with Rufus, there's absolutely no issue with GPT partitioning.

Now I can't use MBR as all of my disks are GPT formatted & I don't wanna convert/change them to the old MBR style & the problem is, I can't use Rufus either, as the only reason I use Ventoy, is the ability to handle/retain multiple ISOs at the same time

therefore, I opened this issue here & requesting to solve it ASAP. TIA.

SM-03 commented 4 months ago

Hi @ventoy is there any fix coming for this?

catherinedoyel commented 4 months ago

Until 24H2 goes gold I am not sure if it can be solved as a change might be implemented, but then Microsoft may change again. The way ISO is made on UUPdump is not the same as the one Microsoft puts on their website. The current release you get from Microsoft website is Win11_23H2_English_x64v2.iso from December 2023, does this cause the problem too?

ElectroPerf commented 4 months ago

Until 24H2 goes gold I am not sure if it can be solved as a change might be implemented, but then Microsoft may change again. The way ISO is made on UUPdump is not the same as the one Microsoft puts on their website. The current release you get from Microsoft website is Win11_23H2_English_x64v2.iso from December 2023, does this cause the problem too?

well the same issue is present in window11 iot ltsc. basically with any windows 11 iso that has the new installation UI is suffering

SM-03 commented 4 months ago

Until 24H2 goes gold I am not sure if it can be solved as a change might be implemented, but then Microsoft may change again. The way ISO is made on UUPdump is not the same as the one Microsoft puts on their website. The current release you get from Microsoft website is Win11_23H2_English_x64v2.iso from December 2023, does this cause the problem too?

@catherinedoyel 24H2 is already released internally via the release preview channel & the same will be the GA (formerly called RTM) on Sep/Pct later this year, I don't really think that MSFT gonna change anything on their end.

And UUP-made ISO is the same/identical like the MSFT official release ISO as UUP downloads all the resources from the MSFT server so internally every file will be the same. No difference. UUP give you more freedom to customise the ISO as per your own choice & preferences.

And at the end, like I wrote, in Rufus, there's no problem with this new 24H2 installer with GPT formatted USB driver but it's causing the issue with ventoy only so there must be a way to solve this.

Until 24H2 goes gold I am not sure if it can be solved as a change might be implemented, but then Microsoft may change again. The way ISO is made on UUPdump is not the same as the one Microsoft puts on their website. The current release you get from Microsoft website is Win11_23H2_English_x64v2.iso from December 2023, does this cause the problem too?

well the same issue is present in window11 iot ltsc. basically with any windows 11 iso that has the new installation UI is suffering

@ElectroPerf you must be talking about 24H2 W11 IoT ISO, right?

ElectroPerf commented 4 months ago

Until 24H2 goes gold I am not sure if it can be solved as a change might be implemented, but then Microsoft may change again. The way ISO is made on UUPdump is not the same as the one Microsoft puts on their website. The current release you get from Microsoft website is Win11_23H2_English_x64v2.iso from December 2023, does this cause the problem too?

@catherinedoyel 24H2 is already released internally via the release preview channel & the same will be the GA (formerly called RTM) on Sep/Pct later this year, I don't really think that MSFT gonna change anything on their end.

And UUP-made ISO is the same/identical like the MSFT official release ISO as UUP downloads all the resources from the MSFT server so internally every file will be the same. No difference. UUP give you more freedom to customise the ISO as per your own choice & preferences.

And at the end, like I wrote, in Rufus, there's no problem with this new 24H2 installer with GPT formatted USB driver but it's causing the issue with ventoy only so there must be a way to solve this.

Until 24H2 goes gold I am not sure if it can be solved as a change might be implemented, but then Microsoft may change again. The way ISO is made on UUPdump is not the same as the one Microsoft puts on their website. The current release you get from Microsoft website is Win11_23H2_English_x64v2.iso from December 2023, does this cause the problem too?

well the same issue is present in window11 iot ltsc. basically with any windows 11 iso that has the new installation UI is suffering

@ElectroPerf you must be talking about 24H2 W11 IoT ISO, right?

Yes that's what i am talking about.

ElectroPerf commented 4 months ago

@ventoy you must either try out the release preview builds or the win11 iot ltsc builds if you wanna go with untouched iso from Microsoft's side, but also with uup dump iso, it's the same issue

zept888 commented 4 months ago

I was installing one of the win11 lstc ISOs and can confirm on this issue.

switching from GPT to MBR solved the issue for me. if what @SM-03 says is true about Rufus having no problems installing ISO with GPT, ventoy has some fault on its side.

SM-03 commented 4 months ago

@zept888 Whatever I said about Rufus is true indeed. You can try it for yourself.

TheColin21 commented 4 months ago

Issue occurs for me too on a 256GB Kingston stick with two different Win 11 24H2 ISOs

SM-03 commented 3 months ago

Issue occurs for me too on a 256GB Kingston stick with two different Win 11 24H2 ISOs

so, what workaround did you try? Formatting with MBR worked with ventoy or you used Rufus for 24H2?

KCHARRO commented 2 months ago

After select language….

Just click on the blue letters “Use old installation program”

telmob commented 2 months ago

Issue occurs for me too on a 256GB Kingston stick with two different Win 11 24H2 ISOs

so, what workaround did you try? Formatting with MBR worked with ventoy or you used Rufus for 24H2?

Worked with MBR.

Z0ink5 commented 1 month ago

After select language….

Just click on the blue letters “Use old installation program”

That worked for me! Thank you.

tstolik commented 1 month ago

After select language….

Just click on the blue letters “Use old installation program”

Worked for me, thanks! Waiting for new update of Ventoy

meesterexx commented 1 month ago

After select language…. Just click on the blue letters “Use old installation program”

Worked for me, thanks! Waiting for new update of Ventoy

Worked for me as well on intel 12th gen mini-pc that previously never had a problem installing Win11 via Ventoy up through 23H2 but was getting this exact error on 24H2. Thank you very much!

eugenesan commented 1 month ago

+1 on the new installer in Windows 11 24H2.

Tested on real hardware and Virtualbox. Both machines worked just fine with other methods of booting Windows setup from USB.

Seems to be failing during disks scan but I found nothing suspicious when inspecting disks inside WinRE. Using scripted partitioning (autounattend.xml) doesn't help.

P.S. Switching to legacy installer option is no longer available in final 24H2 release.

SleepyAlpha commented 1 month ago

+1 on the new installer in Windows 11 24H2.

Tested on real hardware and Virtualbox. Both machines worked just fine with other methods of booting Windows setup from USB.

Seems to be failing during disks scan but I found nothing suspicious when inspecting disks inside WinRE. Using scripted partitioning (autounattend.xml) doesn't help.

P.S. Switching to legacy installer option is no longer available in final 24H2 release.

It is still available on final release, right after choosing the keyboard layout and yes it still bypasses the new installer issue.

eugenesan commented 1 month ago

+1 on the new installer in Windows 11 24H2. Tested on real hardware and Virtualbox. Both machines worked just fine with other methods of booting Windows setup from USB. Seems to be failing during disks scan but I found nothing suspicious when inspecting disks inside WinRE. Using scripted partitioning (autounattend.xml) doesn't help. P.S. Switching to legacy installer option is no longer available in final 24H2 release.

It is still available on final release, right after choosing the keyboard layout and yes it still bypasses the new installer issue.

Thanks. I just check again on new VM and you are correct.

asheroto commented 3 weeks ago

I was holding off to test this until the official Microsoft release came out, because on occasion I've had some glitches when using the UUPDump method. Now that the official Microsoft ISO has been released for 24H2, I performed some tests and wanted to share what I found...

Ventoy via Virtual Machine

I tested out the latest version available from Microsoft which has 24H2 in the filename. First thing I noticed is that the installer looks much different than before. They redesigned it...

image

I was able to find the disks without error...

image

And Windows began installing fine...

image

Install also looks different...

image

Booted into Windows without problem.

image

Ventoy on Physical Machine 1

Ventoy does load, but Windows 11 setup does not. Although this is a semi-old computer.

When loading 24H2 on a Dell OptiPlex 990, I just get a cursor...

KVM screenshot: image

Ventoy on Physical Machine 2

When loading 24H2 on a Dell OptiPlex 9020, it loads but then I get this error, as others have mentioned...

KVM screenshot: image

Workaround: Click Previous Version of Setup

Clicking "Previous Version of Setup" works...

image

KVM screenshot: image

winver: image

If you're using autounattend.xml, you might encounter some compatibility issues with the new installer. If you click "Previous Version of Setup" and the autounattend.xml file doesn't work, or if you're attempting a fully automated installation with autounattend.xml, you may need to use a 23H2 ISO and replace the sources\install.wim file with the 24H2 version. The install.wim file contains all the necessary components for installing Windows; the difference lies in the installation method.

Summary

Ventoy installs Windows 11 24H2 just fine on virtual machines, but fails on physical machines. This issue has been reported several times in the Ventoy issues and forums.

eugenesan commented 3 weeks ago

You don't have to modify ISOs, you can choose "Previous setup version" or perform manual install.

Someone on a different issue, suggested using NTFS for Ventoy main partition, it didn't help.

P.S. Not directly related, but the new installer is not compatible with auto-install Ventoy plugin.

asheroto commented 3 weeks ago

You don't have to modify ISOs, you can choose "Previous setup version" or perform manual install.

Doh! 😵 Thanks. Updated my post.

eugenesan commented 3 weeks ago

You don't have to modify ISOs, you can choose "Previous setup version" or perform manual install.

Doh! 😵 Thanks. Updated my post.

BTW, here are instructions for using unattend.xml with old setup: https://schneegans.de/windows/no-8.3/#setup

kemzops commented 3 weeks ago

You don't have to modify ISOs, you can choose "Previous setup version" or perform manual install.

Doh! 😵 Thanks. Updated my post.

Thank you both for your efforts, After I lost hope it worked for me! #7

kjkent commented 1 week ago

Similar issue on a T480s and latest 24H2 iso. There's also a problem in recognising the resolution, so the UI is huge and cut off (there's a few reports of this. In my case, playing with the ventoy settings didn't help).

Install seems to complete ok until it gets to the point of restarting, then a dialog pops up saying "Windows install failed"

photon92 commented 1 week ago

I too would like to add my name to the list of users having this issue. For me though, it's a little harder to bypass as I am using a custom ISO with the unattend file embedded so I can't do the previously mentioned "Previous Version of Setup", I'm just stuck at the error screen. I'm going to see if my image works through Rufus to try to isolate where the problem is.

asheroto commented 1 week ago

@photon92 as an alternative, you can use the 23H2 installer and swap out the source\install.wim file with the 24H2 version. That way it's using the setup from 23H2 but actually installing 24H2. That method has worked for me when using custom ISOs.

I use MagicISO but there are several types of ISO editors.

SM-03 commented 1 week ago

It's very disappointing to see that even after four months, Ventoy still not addressed this issue by releasing an updated version whereas Rufus did the workaround since June 2024, the time we started noticing it & posted here since.

eugenesan commented 1 week ago

It's very disappointing to see that even after four months, Ventoy still not addressed this issue by releasing an updated version whereas Rufus did the workaround since June 2024, the time we started noticing it & posted here since.

While I am not happy about lack of response from the developers as you are, it's not fair to compare Ventoy to Rufus. Rufus is just a fancy disk format and file copy tool. It is possible to replicate Rufus actions in a few terminal commands. Ventoy on the other hand has to implement boot and runtime code to emulate media volumes and use nontrivial and frequently undocumented methods to "trick" Windows Setup into working.

Windows PE/Setup changed it's behavior quite a bit in 24H2 and it's not even clear if the fix will be possible at all. Let's hope someone will be able to find a way to fix this issue.

m2288 commented 1 week ago

After select language….

Just click on the blue letters “Use old installation program”

God bless you, man 🙌

photon92 commented 6 days ago

@photon92 as an alternative, you can use the 23H2 installer and swap out the source\install.wim file with the 24H2 version. That way it's using the setup from 23H2 but actually installing 24H2. That method has worked for me when using custom ISOs.

I use MagicISO but there are several types of ISO editors.

That's a great idea, thanks. Since I'm the one making the ISOs it's easy for me to make a new one.

Still super annoying I need to do this though...