Ventoy is a super tool,

but how can I search with version 1.0.67
search a hard disk if it is encrypted with Bitlocker?

• 2022/02/14 --- 1.0.67 release
  

1. Support F2 to browse and boot ISO/WIM/IMG/VHD(x)/EFI files in local disk. Notes
   
   
2. Move the reboot/halt menu from F2 to F5 Tools/Power
   
3. Change default menu display mode back to ListView mode. (Powerful habit )
   
4. Fix the bug when booting SystemRescue 8.X/9.X
   
5. Fix the bug in VentoyVlnk.sh when create vlnk file for files in a NTFS partition. (#1430)
   
6. Fix the bug that the 1st menu item is not always selected when switching between submenus.
   
7. Fix the bug that file injection does not take effect for windows.(introduced in 1.0.66).
   

(https://sourceforge.net/projects/systemr...o/download)

I've been using SystemRescue since version 8. To make it work, I had to provide additional parameters to the boot-command -
for the 32 bit-version it is img_label=VolumeName and img_loop=path_to_iso
and
for the 64 bit version only the img_loop parameter.
I've done this with the Boot Conf Replace Plugin and a modified grubsrcd.cfg and sysresccd_sys.cfg file.

This worked until the version 9.01 of SystemRescue. With 9.01 it only works with the 32 bit-version, but not with the 64 bit-version, that ends the bootprocess with an error-message that it can not find the init-files.

If I start the 64 bit-version and then press Tab, I can see that the additional parameter is been provided, but it does not work. When I select in ventoy the compatible mode by pressing Ctrl-i, then start the 64 bit-version and hit Tab, I see the original boot-command without the img_loop parameter, if I then provide the img_loop-parameter manually it starts without error, so I presume that it is an error in the plugin. I now switched back to version 9.00 for the 64 bit-version and that is working again

• 2022/02/13 --- 1.0.66 发布
  

1. Experimental support to boot ISO/WIM/IMG/VHD(x)/EFI files in local disk. Notes
   
   
2. Change the default menu display mode to TreeView mode.
   
   
3. Fix a bug when booting the latest recalbox-x86_64.img. (#1423)
   
   
4. Fix a bug about the CGI tool after boot WePE.
   
   
5. Support /dev/disk/by-id/xxx format input in Ventoy2Disk.sh (#1422)
   
   
6. languages.json update
   

双击没反应，工具是用PECMD加载的
用wepe安装器直接安装到U盘就能打开，用ventoy加载ISO就打不开
试过WePE版本2.0-2.2
试过多个U盘，两台不同的电脑,开关memdisk
Ventoy+WePE里面其他软件都能打开，自己的CGI绿色版也能开
WePE里面双击CGI图标会在程序目录下创建一个ventoy文件夹，里面有WinLogin.exe，说明这个问题跟ventoy环境还是有一定关系

In the early stages of Windows Setup, press Shift+F10 to go to the cmd window.

At this time ...
Drive X: is small.

I want to get more capacity.

Can I modify the controls in Ventoy?

Is there a way to have a Windows VHD that is fully encrypted using Veracrypt. Veracrypt is a free, open source disk encryption software which you can use to encrypt your Windows installation. It is an FOSS alternative BitLocker.

I tried two different approaches and neither worked. I first tried to boot up the Windows VHD in Ventoy and install Veracrypt and encrypt the system. Before Veracrypt encrypts the system drive, it will do a test to ensure it will work by rebooting Windows and ensuring your prompted with the Veracrypt password page. I was not prompted with the password page, no matter how I setup the system drive encryption.

I also tried booting up the Windows VHD in VirtualBox and installed Veracrypt and encrypted the system. It worked in Virtualbox but when I copied that Windows VHD file onto my Ventoy drive and booted it up, I get a Windows bootloader error and I am unable to boot into Windows since it is unable to prompt me the Veracrypt boot loader to decrypt the system.

Any help will be most appreciated!

I think there is a bug. 
I use pCloud and the pcloud tool mounts the cloud storage as removable media P:

When I connect now an USB device it is mounted e.g. with H:

When I start now Ventoy it lists my USB device, but with drive letter combination "H: P:" and when I click on "install" it removes also the pcloud drive. After restart the pcloud drive is again available (and luckily not formated) but I think Ventoy should not "combine" both drives and remove P: during installation/formatting of H:, right?

When I connect a second USB device it is listed separetely.

Hi, could I add support for ReactOS ISO?

After mounting the iso image...

x:\source>

x: can you control space with ventoy?

I want more space.