You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
512GB
Disk Manufacturer
Corsair
Image file checksum (if applicable)
None
Image file download link (if applicable)
No response
What happened?
If you run an image via RAMDISK and it boots you back to Ventoy (because it is incompatible or whatever reason), if you try to do it again you will instead receive an error in the RAMDISK loader advising that there isn't enough memory. Only if you reboot can you try again.
The text was updated successfully, but these errors were encountered:
sounds like an issue with not having enough RAM to fit the image. try it on an iso that can fit in RAM and still have enough memory to run it normally. ramdisk works fine for me
Thanks - Not that at all. 128GB. It's plenty. Ramdisk works fine. THE FIRST TIME. If the image is such that Ventoy fails to successfully deploy it, and you get dumped back into Ventoy, you will fail if you try again. You would need to reboot to try again.
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
512GB
Disk Manufacturer
Corsair
Image file checksum (if applicable)
None
Image file download link (if applicable)
No response
What happened?
If you run an image via RAMDISK and it boots you back to Ventoy (because it is incompatible or whatever reason), if you try to do it again you will instead receive an error in the RAMDISK loader advising that there isn't enough memory. Only if you reboot can you try again.
The text was updated successfully, but these errors were encountered: