HI,

Is it possible to add a separator to the menu list ? I would like to separate System images from Tools, something like :

Debian Live
Linux Mint Live
- - - -
GParted
Clonezilla
SystemRescue

Is there a way to add this "- - - -" as a separator in the menu ?

NOTE : I did it creating fake ISO file (with genisoimage sw), then using "menu_alias" and "image_list" plugins, but it is not perfect,as the "- - - -" is selectable as a bootable item, which I would not like...

Thanks.

I'm running on Windows 10 pro 64-bit  fresh install and updated

I've run from a network share and local C: drive

run using admin command prompt

no logfile is generated - it instantly closes - taskmanager briefly flashes a new line then it's gone

Hello Ventoy Community,

i'm a newbie to ventoy and maybe someone can help me after hours of research.

My Hardware

- ACEMAGIC AD03
- BIOS / UEFI / SECURE BOOT
- SSD / GPT
- VENTOY 1.0.97

First Configuration

- 1 SSD as a VENTOY drive / GPT / SECURE BOOT
- 1 VBOX-VDI Image with OpnSense 24 "OPNSENSE.PRIMARY.VDI.VTOY" (32GB)
- 1 VBOX-VDI Image with OpnSense 24 "OPNSENSE.BACKUP.VDI.VTOY" (32GB)
- 1 ISO OpnSense LiveCD
- 1 ISO SystemRescue
- Other Tools
- No USB Drive

When i now want to start the IMAGE, the boot process under OPNSENSE aborts with a MOUNT ERROR ...
Switching from UFS to ZFS and / or MBR / SECURE BOOT disable didn't help.

As far as i can find out, VENTOY doesn't work with FREEBSD as IMAGE.


Second Configuration

- 1 SSD as the primary drive for OPNSENSE
- 1 USB Drive as VENTOY DRIVE
- 1 ISO OpnSense LiveCD on the USB Drive
- 1 ISO SystemRescue on the USB Drive
- Other Tools on the USB Drive

My problem here is that i can't start OPNSENSE on the local drive with VENTOY from USB Drive automatically after 30 seconds.

If i manually go to F4 and select BOOTX64.EFI everything works fine.

I tried F4>BOOT THE 1ST LOCAL DISK ... Here Ventoy tries to start WINDOWS and aborts with an error message.

I tried VTOY_EXIT ... Here Ventoy simply restarts the computer and opens the pc bios.

###

Now i would like to create a grub entry via F6> that simply boots the hard drive after 30 Seconds with "VTOY_DEFAULT_IMAGE": "F6>"

Unfortunately i have no idea about grub / bootloader ... or maybe i'm just doing something wrong.


Many thanks for the help 

Hi,


I created a Ventoy USB with a few ISO and WIM images. Great tool !

A few of them, all windows related, fail to start with the same "Windows Boot Manager" error (see attachement), the file missing is "winload.exe".

ISO :
- All Linux images works.
- Hiren's CD (HBCD_PE_x64.iso) fails to start with the above Windows Boot Manager error.

WIM :
- Mini windows 10 starts successfully.
- Win8, Win10 and Win11 recovery images fails to start with the above Windows Boot Manager error.

Ventoy boot mode is BIOS.

What did I missed ?
Thanks.

• 2023/04/02 --- 1.0.20 release
  

1. Optimization for Windows Driver Missing Error.
   
   
2. Fix the crash when boot some special ISO files.
   
   
3. Bugfix, comments and suggestions are welcome.
   

I've been utilizing Ventoy for an extended period; however, my manager has recently restricted my use of the tool due to concerns with UEFI certification. He claims that Ventoy enrolls a custom certificate and replaces the original UEFI certificate on our client PCs and laptops. Consequently, he is compelling me to revert to using Rufus. Would anyone be able to offer assistance?

PS :why Rufus have no Problem using UEFI ?

Under the plugin for wimboot i see:

Quote:You can customize ventoy_wimboot.img as you need
There are many configurations in bcd file in ventoy_wimboot.img. For example, digital signature, test mode ...
You can customize them if the default template doesn't match your requirement.

Hi,

I am trying to setup iVentoy for our production and I am having issues with the software. The main issue is that I cannot get any computers on the same VLAN as iVentoy to load the bootfile. We are running iVentoy in "External Mode" as we are using our router as the DHCP provider. We do not see iVentoy snooping any DHCP packets. 

We use TP-Link Omada for our network infrastructure (similar to Ubiquiti). I have attached a picture showing how our VLAN and DHCP settings in the router are configured for iVentoy. 

We have been PXE booting for a while now on our network. We know that our current configuration works with Windows Deployment Services (WDS) and also a program similar to iVentoy called Serva. We are looking to try out iVentoy but have run into this problem and need help. We of course disabled our WDS and Serva programs prior to using iVentoy so as to not cause any conflicting errors. 

Any help would be greatly appreciated.

Attached Files

Thumbnail(s)
   

I would like to boot the Windows 10/11 wim files contained in the WinPE 11-10-8 Sergei Strelec (x86/x64/Native x86) 2023.06.25.iso. In Legacy BIOS mode, only the W10 wims boot without issues. The WinPE 11 wim boots and shows the flag, but the rotating wheel under it doesn't appear and the system restarts. Booting the iso and selecting the Win 11 entry boots okay. Anyone know what might be the problem or if there's another way of booting that specific wim directly?

For Legacy BIOS, I had to use CLI to get other files to boot. The W11 wim is the only one that doesn't work there. Everything in UEFI non-CLI mode boots okay.

Hello. I managed to modify the ventoy_vhdboot.img so that it can boot encrypted BitLocker VHDX. However, this currently only works for my VHDX. 
Perhaps you could make this a universal solution!?

What I did:

    I created a Windows To Go (WTG) drive with BitLocker encryption following the instructions provided in the article "To enable BitLocker during provisioning" (https://learn.microsoft.com/en-us/previo...8(v=ws.11)).

    I connected the WTG.vhdx to a Hyper-V virtual machine using Windows 11 and added a boot entry to BCD using the command: "bcdboot W:\windows", where W is the mounted and unlocked WTG.vhdx.

    After that, I merged and cleaned up the BCD in the ventoy_vhdboot.img.

    I also updated the bootx64.efi in the efi.img using the one from Windows 11. Without this step, it prompted for a password but decryption didn't occur.

If you're interested, I can send you my ventoy_vhdboot.img via email or another method. I can't upload it here due to its size.

Attached Files

  bcd.zip (Size: 7.47 KB / Downloads: 16)