Yes. I have tried the latest release, but the bug still exist.
Try alternative boot mode
No. I didn't try these alternative boot modes.
BIOS Mode
Legacy BIOS Mode
Partition Style
MBR
Disk Capacity
1 TB
Disk Manufacturer
Kingston
Image file checksum (if applicable)
None
Image file download link (if applicable)
No response
What happened?
When I try to boot from my NVME USB 3 drive on my ancient Dell Latitude E5500 (Core2Duo, 4 GB, 500GB SATA SSD internals), I get a message about unable to find /ventoy/ventoy.cpio on VTOYEFI partition. I have checked on a linux system, and the file IS present in the specified location. There is no initial menu, due to that error. I am connected to the NVME via a known working USB A to USB C file. I can copy multi-GB files from Windows to that drive with the same cable, so it's not the cable.
However, I'm not sure how to check if the file might be corrupt? I don't have any newer systems to re-test/double-check with right now.
I'll try comparing with a working Ventoy install, and see if the size & sha256sums match.
2 Other Ventoy USB drives both boot fine. One USB 2 native drive, and one USB 3 native drive.
Official FAQ
Ventoy Version
1.0.94
What about latest release
Yes. I have tried the latest release, but the bug still exist.
Try alternative boot mode
No. I didn't try these alternative boot modes.
BIOS Mode
Legacy BIOS Mode
Partition Style
MBR
Disk Capacity
1 TB
Disk Manufacturer
Kingston
Image file checksum (if applicable)
None
Image file download link (if applicable)
No response
What happened?
When I try to boot from my NVME USB 3 drive on my ancient Dell Latitude E5500 (Core2Duo, 4 GB, 500GB SATA SSD internals), I get a message about unable to find /ventoy/ventoy.cpio on VTOYEFI partition. I have checked on a linux system, and the file IS present in the specified location. There is no initial menu, due to that error. I am connected to the NVME via a known working USB A to USB C file. I can copy multi-GB files from Windows to that drive with the same cable, so it's not the cable.
However, I'm not sure how to check if the file might be corrupt? I don't have any newer systems to re-test/double-check with right now.
I'll try comparing with a working Ventoy install, and see if the size & sha256sums match.
2 Other Ventoy USB drives both boot fine. One USB 2 native drive, and one USB 3 native drive.