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: 11)

Is there a way to PXE boot computers if their firmware does not support PXE booting from any brand USB-to-Ethernet dongle?

The Microsoft Surface Pro 2 is a good example. It does not have a built-in Ethernet port. I have read that you have to purchase a specific Microsoft branded dongle that's compatible with the Surface's firmware in order to PXE boot. Is there a way to use any USB-to-Ethernet dongle on any computer so that you can PXE boot any computer? I guess I'm thinking along the lines of creating a bootable USB drive, booting to a pre-boot environment from it and then PXE booting from there.

Has anyone been able to accomplish this? If so, please share the steps to do this :-)

Hi,

I am use the auto install kickstart script with RHEL9.0 but will stop to "Welcome to red hat enterprise linux 9.0".

Use iVentoy 1.0.19.

What should I do ? Thank.


   


  ks.cfg.txt (Size: 1.5 KB / Downloads: 5)

Hello everyone,  I have the problem when I want to start a Windows image with iventoy that my display is incorrect. The image is torn into lines and stretched significantly. See pictures..  Ubuntu, however, starts without any problems.  I tested Windows 10 and Windows 11.  Has anyone seen this before? Can anyone help here?

Thank you

Ramset

Attached Files

Thumbnail(s)
           

Hello,

I use ventoy-1.0.97 on Windows 10 22H2 (19045.4170).

I wanted to test the injection plugin in live OS using .wim, namely the Mini_Windows_10_v21.12.wim taken from medicat.

For that, I just used the template from github mentioned here: https://www.ventoy.net/en/doc_inject_autorun.html to create the archive. I didn’t touch or edit any file in it.
Here is the content of the archive:


Then, I added the injection entry point in ventoy.json using VentoyPlugson.exe such as :

Hello,

May I know the details of the theme background image's maximum allowed resolution and size? 
What I've noticed is that if the image doesn't meet the requirements, then it cannot be booted.

Regards