•     2021/04/27 -- Ventoy 1.0.42 released
  
  
  1.     Add * fuzzy matching for menu_alias/image_list/auto_install/persistence ... plugins. Notes
     
  2.     Add parent option in menu_class plugin. Notes
     
  3.     Add F4boot F5tool builtin class in menu_class plugin.
     
  4.     By default the submenu will use its parent's class in F4 boot and F5 tool menu.
     

• 2021/05/08 -- Ventoy v1.0.43 -- released
  
  
  1.     Change the UTF-16 languages.ini to UTF-8 languages.json
     
  2.     The update button is available even if data corrupted in VTOYEFI partition.
     
  3.     Set the default focus to No when you click Install button in Ventoy2Disk.exe.
     
  4.     Fix a BUG when booting Windows VHD(x) with the latest ventoy_vhdboot.img.
     
  5.     Support boot Windows VHD(x) files at local disk. Notes
     

• 2021/05/15 -- Ventoy v1.0.44 -- released
  
  
  1.     Add WIMBOOT Mode. Notes
     
  2.     Fix issue when install Fedora Server Edition
     
  3.     Add -o option in CreatePersistentImg.sh (#903)
     
  4.     Add parent/isopwd/wimpwd/imgpwd/efipwd/vhdpwd/vtoypwd options in password plugin. Notes
     
  5.     Fix a bug about unaligned read in UEFI mode.
     

I have been trying to follow the setup detailed in https://www.ventoy.net/en/plugin_vtoyboot.html, but I always get stuck with the same errors.





I've been mostly trying this to setup 'linuxmint-20-mate-64bit.iso' and have tried booting the vdi.toy created with VirtualBox in Ventoy v1.0.41, v1.0.32, etc.

I have working VHDs with Windows in the same locations that boot alright before that -- i.e., when I get such errors, nothing boots anymore and I have to reboot.

What am I doing wrong?

• VoidLinux doesn't work
  

• Fedora (Rawhide) doesn't work
  

• Solus doesn't work
  

• Obarun (Arch_based_with_S6_init) doesn't work
  

Many thousands of people have no problem - so maybe you should check the checksum (CRC32\SHA1) of the ISO file that is on your USB drive? Otherwise, give exact details of which ISO you are using.

I have a USB device build with UFS chip and SM3350 controller. Thus only have a partition and can't rewrite its partition table. What should I do to install Ventoy on it? Or could u offer a optional program to solve this question?

Hello, is it possible to know which function or file searches for images and folders on the key? Who creates the menu entries for each folder in treetview mode?

What are the different shortcuts in Ventoy?
Example :
- C: Enter terminal mode
- E: See which command is behind this button
- Ctrl-alt-suppr: Restart
- Ctrl+i: Compatible mode

What does compatible mode mean?

What code in grub.cfg is loaded in gui mode for the theme?

Thanks for your work!

I am trying to use Ventoy for deploying images and when i boot to the USB SSD drive and select my ISO image i want to deploy the PC tries loading into it and then just display a blue screen saying "PC has encountered an error" and then it just reboots.  I know the image works if i boot it from just a regular USB stick.  Any ideas as to why this would be happening?

• 2021/04/21 -- Ventoy v1.0.41 released
  
  
  1.     Add support for OpenWrt IMG file. Notes
     
  2.     Add support for MidnightBSD 2.x release
     
  3.     Add support for new GhostBSD release
     
  4.     Fix a bug about source media missing when boot openEuler
     
  5.     Fix a bug about source media missing when boot CentOS 8
     
  6.     languages.ini update
     
  7.     New image support (total 700+):
     • openwrt-19.07.7-x86-64-combined-ext4.img (Legacy + UEFI)
       
     • openwrt-19.07.7-x86-64-combined-squashfs.img (Legacy + UEFI)
       
     • openwrt-19.07.7-x86-generic-combined-ext4.img (Legacy)
       
     • openwrt-19.07.7-x86-generic-combined-squashfs.img (Legacy)
       
     • GhostBSD-13-21.04.16.iso (Legacy + UEFI)
       
     • MidnightBSD-2.0.6--amd64-disc1.iso (Legacy + UEFI)
       
     • MidnightBSD-2.0.6--i386-disc1.iso (Legacy)
       
     • redos-MUROM-7.3-20210201-Everything-x86_64-DVD1.iso (Legacy + UEFI)