search

ventoy / Ventoy

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

Faulty Operational Process #2769

Open westlake-san opened 8 months ago

westlake-san commented 8 months ago

Official FAQ

Ventoy Version

1.0.97

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

32GB, 128GB, 1TB (not relevant)

Disk Manufacturer

Kingston, Silicon Power (not relevant)

Image file checksum (if applicable)

None

Image file download link (if applicable)

https://uupdump.net/

What happened?

As of Windows Insider (Canary Channel) version 26040.1000, the installation interface is (partially) new. With this new installation interface, the installer does not work, because the part where you can manage the data stores is no longer displayed correctly (error code: 0x80070001 - 0x4002F). Logically, it does not work with the newer versions (26052.1000, 26058.1000, 26063.1). With the latest available version (26063.1), you can no longer even start the ISO in normal mode, only with wimboot. Client and server versions of the same version do not work. However, the same thing mentioned before (storage management window) does not work with wimboot. I know that Rufus does the boot partition differently, but when I do the installer with it, everything works normally. As far as I can tell, it has nothing to do with what file system the storage is on (NTFS, or exFAT). With Rufus it works with NTFS and FAT32 (large mode).

In case the above part is not clear:

26040.1000 normal mode -> boot ok, storage management window error 26052.1000 normal mode -> boot ok, storage management window error 26058.1000 normal mode -> boot ok, storage management window error 26063.1 normal mode -> boot error 26063.1 wimboot mode -> boot ok, storage management window error

I tried with several pendrives and several machines.

!Works fine in legacy mode (MBR)!

Infraded commented 8 months ago

I'm also seeing this on Windows 11 Insider Build 26058. Ventoy 1.0.97 UEFI/GPT/normal mode boots fine, but fails with error code 0x80070001 - 0x4002F prior to displaying storage configuration. No issues with the iso written directly to a USB drive.

westlake-san commented 8 months ago

With 26080.1 (Server & Client) it works fine (again). Could it not be the Ventoy's fault?!

hexd0t commented 8 months ago

With 26085 (Current Server vNext / 2025 Preview), the Installer starts in both normal and wimboot mode for me, but I also get the storage management window error.

westlake-san commented 8 months ago

With 26085 (Current Server vNext / 2025 Preview), the Installer starts in both normal and wimboot mode for me, but I also get the storage management window error.

I think the cause of your problem will be different. I have all builds (Canary) newer than 26063 [26080 (S&C), 26085 (S&C), 26090 (C)] working normally.

westlake-san commented 8 months ago

With 26085 (Current Server vNext / 2025 Preview), the Installer starts in both normal and wimboot mode for me, but I also get the storage management window error.

I think the cause of your problem will be different. I have all builds (Canary) newer than 26063 [26080 (S&C), 26085 (S&C), 26090 (C)] working normally.

Also 26100 works fine.

Aaron2550 commented 6 months ago

Also 26100 works fine.

I am getting this error on build 26100.268

meluvalli commented 6 months ago

I also am getting 0x80070001 - 0x4002F with latest build (26217.5000). I have tried both WIM and normal boot modes. I did notice that once in Windows Setup, after you select Language and Keyboard Settings, on the bottom of the screen, there is an option for "Previous Version of Setup". If you click that, it'll go back to the old style of setup and allow it to install fine.

westlake-san commented 6 months ago

I can say what I have written before. For those who have problems with builds after 26063, something local is preventing normal operation. For me all the newer Client and Server builds work fine (26063+).

Schrotty74 commented 6 months ago

Its not a local issues lol. I have the sme on 26100.712. With latest Rufus its work and now? Its only a Ventoy problem!

westlake-san commented 6 months ago

Upload an ISO that doesn't work for you. I don't think there is any significance to the Ventoy version, as I for one am not using the latest one.

Schrotty74 commented 6 months ago

Download on MS or other source.

westlake-san commented 6 months ago

I obviously asked for a reason. I have ISOs too, I didn't ask for them because I don't have them. It's hard to find out why it doesn't work for you if it works for me, isn't it?

westlake-san commented 5 months ago

@ventoy

I tried again with the latest 24H2 builds (26120.751, 26231.5000) and everything works as it should. Well, almost, but I don't think that's Ventoy's fault. If the installer media is formatted to exFAT, the newer installer always stalls (error code: 0x80070001 - 0x4002F). The old version works, but there has never been a problem with that either. If it is formatted to NTFS, everything works perfectly. I wrote earlier that ISOs that don't work with Ventoy work fine with Rufus. Of course, since Rufus always formats the storage to NTFS, exFAT is not an option there. And with Ventoy, exFAT is the default, maybe this should be changed to NTFS, because of the above mentioned problem. My advice is: you should use NTFS partition too. I know that exFAT is newer (more advanced), but that's the way it is. There is nothing wrong with NTFS either. I don't want to try older ISOs anymore, it doesn't matter if it works normally or not.

Schrotty74 commented 5 months ago

Ye with NTFS works with Ventoy too.

meluvalli commented 5 months ago

Hmm. I formatted the USB as NTFS and still got the error. So, I wonder what is different? I used GPT instead of MBR. Is that the same as what you used? Maybe I need to try MBR?

On Thu, Jun 6, 2024 at 8:38 PM westlake-san @.***> wrote:

@ventoy https://github.com/ventoy

I tried again with the latest 24H2 builds (26120.751, 26231.5000) and everything works as it should. Well, almost, but I don't think that's Ventoy's fault. If the installer media is formatted to exFAT, the newer installer always stalls (error code: 0x80070001 - 0x4002F). The old version works, but there has never been a problem with that either. If it is formatted to NTFS, everything works perfectly. I wrote earlier that ISOs that don't work with Ventoy work fine with Rufus. Of course, since Rufus always formats the storage to NTFS, exFAT is not an option there. And with Ventoy, exFAT is the default, maybe this should be changed to NTFS, because of the above mentioned problem. My advice is: you should use NTFS partition too. I know that exFAT is newer (more advanced), but that's the way it is. There is nothing wrong with NTFS either. I don't want to try older ISOs anymore, it doesn't matter if it works normally or not.

— Reply to this email directly, view it on GitHub https://github.com/ventoy/Ventoy/issues/2769#issuecomment-2153790944, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCTHBHWBB4TPE6G7ZWQTMDZGETKXAVCNFSM6AAAAABEN4QH5SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJTG44TAOJUGQ . You are receiving this because you commented.Message ID: @.***>

westlake-san commented 5 months ago

This error (error code: 0x80070001 - 0x4002F) could be caused by other things, not just exFAT. This is what the installer tells you even if, for example, there is no suitable driver for a particular datastore.

meluvalli commented 5 months ago

I can confirm MBR solved the problem! So format as NTFS and use MBR and all is good!

SM-03 commented 5 months ago

I reported (& explained) this issue here . Hope they'll fix this at the earliest.

And one more thing I'd like to know, no matter in what I format the PD, Ex-FAT, FAT or NTFS, why copy speed is always slow & capped within 15-20MB while copying the ISO even using with Gen 3.1 3.2 USB slot? Is there any solution to this?

TheColin21 commented 4 months ago

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

Daniel224455 commented 4 months ago

Well, seems like the new windows setup (ge_prerelease and higher) doesn't seem to like exFAT. To fix this issue, try to get to the menu where "Previous Version of Setup", and then try to continue installing (THIS WORKED FOR ME!) If that does not work, then try to reformat the Ventoy drive with NTFS

freeyoung commented 4 months ago

To fix this issue, try to get to the menu where "Previous Version of Setup", and then try to continue installing (THIS WORKED FOR ME!)

Worked for me as well, thank you!

TheColin21 commented 3 months ago

It's still not acceptable behavior, even with this workaround...

DiegcD commented 2 months ago

Same issue using windows 11 iot Enterprise and this .iso doesn't have the use "previous version of setup" as someone pointed out in another comment.

Using Rufus fixed the issue

fMagVen commented 1 month ago

I also am getting 0x80070001 - 0x4002F with latest build (26217.5000). I have tried both WIM and normal boot modes. I did notice that once in Windows Setup, after you select Language and Keyboard Settings, on the bottom of the screen, there is an option for "Previous Version of Setup". If you click that, it'll go back to the old style of setup and allow it to install fine.

spot on, mate, thank you

mstrewe commented 1 month ago

previus version of setup fixed it for me too.

Current windows 11 version with extFat

alionur54 commented 3 weeks ago

The "Previous Version of Setup" option solved my problem. I didn't try the NTFS thing. Actually, Rufus solved it too, but Ventoy is a great blessing for an IT person like me. However, I saw that in the disk partitioning section with the "New Version Setup" in the installation I made with Rufus, the installation flash memory partitions that were not visible in the "Previous Version of Setup" installation were also visible. It is obvious from here that there are some changes. In fact, if Microsoft fixes it twice, it will break it once. I don't think we should look for errors in Ventoy.