Hi!
When i boot from ISO (WinPE) with grub2 or g4d, and try install windows im gettin the error (See screenshots):
Windows cannot be installed to this disk. This computer's hardware may notsupport booting to this disk. Ensure that the disk's controller is enabled in thecomputer's BIOS menu.

But i can boot and install windows form ISO with ventoy without any problem.
how can i know where is the problem or how ventoy bypasses it?

Attached Files

Thumbnail(s)
           

I have a 32bit efi with a 64bit processor. (cherrytrail) I can boot the following os with YUMI--- https://distro.ibiblio.org/fatdog/iso/Fatdog64-721.iso ---
without problems.  when I use ventoy it hangs at the last boot stage  before launching window manager any ideas

I'm seeing many duplicate menu items (ISO's). Any ideas on how I can fix this?

Thanks,
Mike

Hi guys . I need some help. I created my flash drive and when I boot and select to do it by they flash drive with ventoy the pc goes directly to my bios without showing the isos options to boot. When I boot it thinks a little , doesn't show any error and goes to the bios.
It is something with secure boot. If i disable it it boots normally.

I have selected on ventoy's menu Option- secure boot support but it seems  not working.

Any ideia to overpass this problem?

I have a x570 Motherboard.

使用VENTOY启动Gandalf PE之后。并不能自动加载ISO至Y盘。于是写了个批处理。利用Gandalf PE卷标“Win10PESE” 自动加载ISO同时调整至Y盘盘符

批处理需要和ISO放置同一路径。同时需要修改ISO文件名

@echo off & setlocal enabledelayedexpansion


cd /d "%~dp0"
SET CurDir=%CD%

explorer.exe "%CurDir%\Windows_PE_Gandalf_tools.iso"

ping 127.1 -n 5 >nul

for %%i in (Z Y X W V U T S R Q P O N M L K J I H G F E D C) do (
  vol %%i:|findstr "Win10PESE">nul&& set drivername=%%i:\)


mountvol >%CurDir%\volname.txt

for /f "delims=" %%j in ('type "%CurDir%\volname.txt"') do (
set "str=%%j"
>>$ echo,!str: =!
)
move $ "%CurDir%\volname.txt" >nul

for /f "delims=" %%c in (%CurDir%\volname.txt) do if "%%c"=="%drivername%" (set guid=!char! &goto :end) else (set char=%%c)


:end
echo %drivername%
echo %guid%
echo y | del %CurDir%\volname.txt
mountvol %drivername% /D
mountvol Y:\ %guid%
pause >nul

Ventoy persistence backend image files 4.0

https://github.com/ventoy/backend/releases

https://github.com/ventoy/backend/releas...images.zip

看介绍是包含vtoycow格式的文件。

但压缩包内并没有vtoycow格式的持久化文件。

压缩包尺寸与3.0的体积相同。已经重新下载数次测试仍是如此。

• 2021/04/10 -- Ventoy v1.0.40 released
  .
  
  1. persistence support for Fedora series. Notes
     
  2. persistence support for ArchLinux series (Arch/ArchMan/ArchBang/BlackArch...). Notes
     
  3. Fixup a bug when booting special Windows/WinPE ISO file.
     
  4. Add a workaround for #815
     
  5. Support RHEL6/CentOS6 auto install
     
  6. Clear input key before show main menu. (#824)
     
  7. languages.ini update
     

Hello,
In the F6 submenu, I would like that when we click on for example "Boot on linux iso", it boots on the right iso. Is there a grub command that allows you to do this: it's a bit like the menu expiration and autostart.
Thanks in advance

hello everyone,
i just want to say I stumbled across ventoy in a thread and as a former yumi user I'm really impressed.  functions great.  created usb with gpt and exfat.  this allowed me to make a persistence file greater than 4gb for live boot os.  I then realized you can create a single boot .vdi in virtualbox with the "efi os" checked off. so I completed the os install and copied and rename file to lbuntu.vdi.vtoy but have been unsuccessful.  after init boot it stops at (initrfs) prompt.  I did copy ventoy.disk.img, ventnoy_vhdboot.img, and ventoy_wimboot.img file to /dev/part1/ventoy directory I also created an entry for it in /dev/part1/ventoy/ventoy_grub.cfg I know there's alot that can be going wrong and hard to diagnose but is there a combo I'm using incrorectly or something missing?   this stuff is very versatile

Hello
I just set a computer to secure boot mode Since then, I can no longer boot the USB key made by ventoy, the error message is as follows

"Boot stopped: A suitable digital signature was not found. One of the files on the chosen boot device was rejected by the secure boot function "

I tried with the key made in secure boot or not for versions 1.38 and 1.39 Again, I had to use unetbootin to remake installation media!

It's probably one of those files