• 2023/03/26 --- 1.0.90 release
  

1. Fix the issue that VTOY_LINUX_REMOUNT option can not work for (Kernel 5.18+) + (Intel Gen11+ CPU).
   
   
2. Support LibreELEC 11.0+. (#2281)
   
3. Fix the issue that Fedora Rawhide install media not detected. (#2283)
   
4. Add support for chimera linux. (#2309)
   
5. Optimization for Fedora boot process.
   
6. languages.json update.
   
7. New iso support. (Total 1100+)
   

Hi,

Maybe a bit of a niche question, but I've started using Ventoy at work to easily switch between diagnostic and various OS ISOs for client hardware, and one thing that's been floating in the back of my mind is,

"If a Windows ISO can boot fine, and an Ubuntu ISO can boot fine, how come I need to register Ventoy's certificate?"

I really don't know too much when it comes to exactly how secure boot works. I figured maybe it's a Microsoft thing where OEMs ship with private keys that only handshake with Windows, but my Ubuntu USBs will boot on these systems with no Mokmanager prompt as well.

In that case, is it possible to take the certificate from Ubuntu or Windows and "transplant" it onto my VTOYEFI partition? Or perhaps there's a tool I can use to enroll my Ventoy .cer with the private keys the UEFIs expect, or something?

Like I said, I'm not too sure how secure boot works on anything beyond a basic conceptual level, but if anyone could help me make it so I can boot my Ventoy USBs on new machines without enrolling the key or disabling secure boot every time, I'd be very appreciative

I have Ventoy Installed on a USB3 Portable SSD 500gb.
There is Plenty of Space left , only 50% occupied.
This drive has Ventoy installed as GPT and Formatted to NTFS with a \Ventoy Partition.
I have all my ISO's in \Ventoy.
Everything Works just Fine from here.
I have Created a Linux Persistence File here ( WindowsFx ) and it Works, and Saves between Restart.
However shortly after a restart of WindowsFx a message Popped Up Saying I have Run out of Space on The Drive.
At that point I have Hardly Installed much at all.
Any help would be appreciated.

1. 设备：

• 佳翼I9GTR硬盘盒+梵想固态硬盘
  

• ventoy：安装到移动硬盘，并放入VHD的img插件，支持VHD启动
  
• wtg：win创建VHD，WTGA安装，ventoy进wtg成功
  
• ltg：VirtualBox创建虚拟机(固定+efi)，加载Ubuntu-22.04.2-full.iso安装完成，安装vtoyboot插件，改名为vdi.vtoy
  

• ThinkPad T480: 启动进ubuntu系统, ok
  
• 拯救者R9000x: 启动失败，错误提示后黑屏, fail
  
• 后来测了CentOS7和8，问题一样，报错都差不多 
  

• T480s：独立NVIDIA MX150，内存40G，硬盘m.2 pcie3 三星固态 500G
  
• R9000x：集显+独立NVIDIA gtx1650ti(混合模式)，内存40G，硬盘梵想S500pro 2TB+三星980 1TB
  

Attached Files

Thumbnail(s)
       

这个工具很好，经常推荐给完全小白的人使用，但是也很频繁会碰到他们用的U盘是虚标容量的情况，启动后只能进入grub命令行界面，然后就要手把手教他们怎么在 U盘手动建目录然后复制压缩包内的 ventoy.disk.img.xz，非常麻烦，个别人甚至直接就放弃了。所以，能否在 UI 上加个单选框之类的，在制作启动盘时候直接就采用将压缩包放在可见区方案？

I created a Ventoy USB stick, worked great, I needed more room on the VENTOY 1st partition for more ISO files, so I used MiniTool Partition Wizard to shrink a 3rd partition I had after the EFI partition, move the VTOYEFI and increase the size of the VENTOY partition.

Attempting to boot to it threw an error that is was not a standard Ventoy installation and it failed. It was a simple enough fix, I simply deleted the VTOYEFI partition (I used MiniTool again) and then did a Non Destructive Install using the Ventoy2Disk.exe. After this it worked again. 

Why is Ventoy so picky about moving the EFI partition? I've moved around an EFI partition for other boot tools, like AGFM / Easy3Boot without issue.  I also notice that you can't increase the size of the EFI partition either.

Curious as to why this is like this.

Hello to everyone

***
First of all, I would like to congratulate the whole team for such a wonderful application...
With my USB and Ventoy key, everything works perfectly, I am a linuxian and on this type of systems, your key... it's just happiness...
It touches the extraordinary... a thousand thanks and low hat!
... I'm French... I was speaking English as a Spanish cow, so I'm using online translation...
***

We're coming to the "little worry"...

Having children with windows, I prefer to have a win base so that I can try to fix a problem (very common at win... sic!), all my other isos are Linux...
But on a "old" portable pc, Samsung N145 plus with 2GB of Ram, impossible to install windows (xp, seven, win 10 & win 11)?
With regard to the installation of multiple Linux systems, no worries, but for windows, the systems are recognized, but during the boot, in normal boot, "small shot at the top left of the screen", all the time, no other possibility?
The hard drive is an AHCI, can be where the problem would be?
Installation with iso on dvd, nickel!
I don't see where the worries can be?
Thanks for the help to come and good day to all and all

And again all my congratulations on your magic key...

************************
Bonjour à toutes et tous

***
Tout d'abord, je tiens à féliciter toute l'équipe pour une si magnifique application...
Avec ma clé USB et Ventoy, tout fonctionne parfaitement, je suis un linuxien et sur ce type de systèmes, votre clé... c'est que du bonheur...
Cela touche l'extraordinaire... Mille mercis et chapeau bas !
... Je suis français..., je parlais l'anglais comme une vache espagnole, donc j'utilise la traduction en ligne...
***

On arrive au "petit" souci...

Ayant des enfants avec windows, je préfère avoir une base win pour pouvoir tenter de réparer un souci (assez fréquent chez win... sic !), tous mes autres isos sont Linux...
Mais sur un "vieux" pc portable, Samsung N145 plus avec 2 Go de Ram, impossible d'installer du windows (xp, seven, win 10 & win 11) ?
Pour ce qui est de l'installation des multiples systèmes Linux, aucun souci, mais pour windows, les systèmes sont reconnus, mais lors du boot, en boot normal, "petit tiret en haut à gauche de l'écran", tout le temps, aucune autre possibilité ?
Le disque dur est un AHCI, peut être là où serait le souci ?
L'installation avec iso sur dvd, nickel !
Je ne vois pas où peut se trouver le souci ?
Merci pour l'aide à venir et bonne journée à toutes et tous

Et encore toutes mes félicitations pour votre clé magique...

I've set up a Ventoy USB with 3 extra partitions. Everything works great and I have several iso's installed in Ventoy's main partition.

I installed a Linux distro in the 3 extra partitions. The partition layout is /dev/sdd3 is an extended partition containing sda5, sda6, sda7, to get around a 4 partition limit using an MBR. The partitions are mounted as follows, /dev/sda4 is not setup,  /dev/sda5 is root, /dev/sda6 is swap, and /dev/sda7 is home.

I can chroot into the Linux install, and boot it from SystemRescue's iso grub menu option findroot.

However, when booting into it using SystemRescue, it uses SystemRescue's kernel rather than the Arch kernel in the install.

I've looked into a way to manually configure Ventoy's grub, but cannot even find a conventional grub.cfg file.

Is it possible what I'm trying to do, boot a Linux distro installed on the same USB as Ventoy?

If not, I may try to manually setup a grub boot USB to boot multi iso's, and have Ventoy installed within it. However this option would be much more work than leveraging Ventoy's boot loader.



EDIT 1

Ok, just figured out the grub.cfg file is on the 2nd Ventoy partition. I mounted it and am currently exploring...

EDIT 2

Added a menu entry to grub.cfg and it shows up on starting Ventoy. Now if I can figure out how get Ventoy to mount the partitions, should be no problem to have grub boot it.

Problem is, Ventoy is booting (one of several?) images, so extracting, editing and re-compressing is a bit of work. I'm sure there would be an easier way to implement this without editing one of the OS images, but I just don't yet know how all these external files work.

How can we Use Ventoy in Linux

[b]Hi AlexBryansk, When do you have ventoy mod 1.0.89? Please share with me, thank you very much.[/b]