We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
1.0.99
Yes. I have tried the latest release, but the bug still exist.
Yes. I have tried them, but the bug still exist.
Legacy BIOS Mode
MBR
16GB
DSE
Yes.
No response
This issue is not a bug in Ventoy itself, but in the instructions provided here;
https://ventoy.net/en/doc_start.html
The "For Linux - CLI mode" needs to specify;
sha256sum ventoy-x.x.xx-linux.tar.gz tar xf ventoy-x.x.xx-linux.tar.gz cd ventoy-x.x.xx sudo sh Ventoy2Disk.sh
I only understood the problem created by using the default unzip program because I read this whole forum thread, found via a web search;
https://forums.ventoy.net/showthread.php?tid=2221
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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
Legacy BIOS Mode
Partition Style
MBR
Disk Capacity
16GB
Disk Manufacturer
DSE
Image file checksum (if applicable)
Yes.
Image file download link (if applicable)
No response
What happened?
This issue is not a bug in Ventoy itself, but in the instructions provided here;
https://ventoy.net/en/doc_start.html
The "For Linux - CLI mode" needs to specify;
sha256sum ventoy-x.x.xx-linux.tar.gz
tar xf ventoy-x.x.xx-linux.tar.gz
cd ventoy-x.x.xx
sudo sh Ventoy2Disk.sh
I only understood the problem created by using the default unzip program because I read this whole forum thread, found via a web search;
https://forums.ventoy.net/showthread.php?tid=2221
The text was updated successfully, but these errors were encountered: