-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ISSUE] Win11 24H2 installation encountered an unexpected error error code 0x80070001-0x4002f #2887
Comments
Hi @ventoy |
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 |
@catherinedoyel 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.
@ElectroPerf |
Yes that's what i am talking about. |
@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 |
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. |
@zept888 |
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? |
After select language…. Just click on the blue letters “Use old installation program” |
Worked with MBR. |
That worked for me! Thank you. |
Worked for me, thanks! |
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! |
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
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.
The text was updated successfully, but these errors were encountered: