Any ideas why the memory test images no longer work after updating ?

So I created the AOMEI Backupper ISO ampe.iso file using the built in Create Bootable Media tool in the AOMEI Backupper program,  but I can't get the ampe.iso to boot in Ventoy.
Secure boot is turned off and other Windows ISO are able to boot in Ventoy so I don't think it's a Ventoy issue. Anyone experienced this with this AOMEI ISO and have solution for it ?

Hello,

some operatings systems (e.g. some Linux live systems) are available as DVD-version(*.iso) and in addition as USB-version (*.img) .


Are both "versions" read only if started from an Ventoy-USB stick (out of the box) ?


Thank's in advance!

Im using an switch router with same vlans (extreme switch) and trying to boot in the iventoy but only can achieve success if i try to boot in Legacy (im not using any external DHCP, Iventoy is set to Internal).

Already tried almost anything, but cant find an option to iVentoy force send only bootfile for UEFI, i think might this will fix my problem but cant solve how can i force iventoy to only share bootfile for UEFI. anyone can help me please?

Error in the client trying to boot in pxe ipv4:

">>Checking Media Presence.......
>>Media Present......
>>Start PXE over IPv4
Station IP address is 192.168.0.204

Server IP address is 192.168.0.1
NBP filename is ipxe.x64.snoponly.efi.0
NBP filesize is 0 Bytes
PXE-E99: Unexpected network error.
"

Anyone having this same issue? i already tried to change every config inside the iventoy, but only can achieve the boot if i change my client pc to Legacy instead of UEFI. (i want to boot in UEFI with secure boot OFF).

iVentoy v1.0.20 win64 free running on Windows 10 x64 (Host BIOS set to UEFI with Secure Boot OFF same as clients)

Hi there, I have started using Ventoy recently, but I have a question, where do I install the OS that I use in Ventoy? do I install it to the hard drive, or just live boot, I would love any help.

Hello,

Is there any support for running as a service or is it advised to use thirds-party software such as runasaservice or nssm?

//X

In earlier Dell models, enrolling the ventoy key into the key manager works fine and allows you to boot Ventoy after enrolling the key.

However, in at least the new Dell Latitude 5550's, this no longer works.  As a matter of fact, you don't even get the pop up from Ventoy to enroll the key into the key manager, it just tries to boot, then can't.

The only way to boot Ventoy with new Dell laptops is to disable secure boot in the bios, do what you need, then re-enable secure boot.

Can you put this on a buglist or a list to fix?

start server error
   
  log.txt (Size: 129.35 KB / Downloads: 6)

Hello everybody,
Introducing: I'm new in this forum and last month I didn't even know what the word "Linux" meant... I am learning this world.
And I discovered Ventoy ! I join the millions of people who have already said how excellent it is.
So, please be understanding if what I'm saying here could be well known to everyone...except to me.

Currently I'm having fun with theme and I've noted the recommended " tap 'c' and 'exit' " on dozens of forums (it doesn't really suit me).
In fact, in normal use one never (rarely) needs to quit Ventoy... Except when testing theme creations, where you do it 100 times a day.

Then, from this 'exit' word, I've also discovered 2 other magic ones: 'halt' and 'reboot'.
{- I don't really know why one doesn't talk about it more ? Is it disruptive for the Ventoy process to use them ?
- I seem to have understood that they risk to close all current sessions ? But I'm alone on my PC ? Also, I haven't launched any distro yet ?
Note: I also tried 'shutdown' and 'poweroff' words used in Grub, but without result}

Anyway, here is still a full way to quit, not as fast as " tap 'c' ", but it's graphical mode and just "for the pleasure" of using what exists (and also what Mr. Ventoy has spent so much effort to offer to us). This uses the 'ventoy_grub.cfg' via 'F6/exMenu'.

This is long version, using 'submenu'...
In fact, I don't have any other commands in it yet, one can also place these commands in "primary menu" level and then rewrite 'F6/exMenu' title in simply "F6/Exit" ?

Watch out: the “Oops!” container is useful to protect against excessive {Enter} key typing (if not, when arriving into menu, you risk to exit without wanting it).
The "Ho Ho Ho" containers are facultative, to separate the block from other commands (if any).

==== (Sorry, I have tried to use "CODE" decoration, but...) ====

menuentry ' ' --class=custom {
echo 'Ho Ho Ho'
}
submenu 'Quit Ventoy Program -->' --class=customsub {
  menuentry ' ' --class=custom2 {
  echo 'Oops !'
}     
menuentry ' --> Exit and Return to BIOS Boot Shell' --class=custom2 {
  echo 'Bye Bye... You are redirected to BIOS Boot Shell…'
  sleep 2
  exit
}   
menuentry ' --> Exit and Reboot the system' --class=custom2 {
  echo 'See you soon... System is rebooting…'
  sleep 2
  reboot
}
menuentry ' --> Complete Shutdown' --class=custom2 {
  echo 'Bye Bye.. System is shuting down…'
  sleep 2
  halt
}   
menuentry '<-- Return to previous menu [Esc]' --class=vtoyret VTOY_RET {
  echo 'return...'
}
}
menuentry ' ' --class=custom {
echo 'Ho Ho Ho'
}

menuentry '<-- Return to previous menu [Esc]' --class=vtoyret VTOY_RET {
echo 'Return …'
}

=========== END ===========

I hope it will please someone as newbie as me.
Thanks for reading

• 2024/06/08 --- 1.0.99 release
  

1. Upadte EFI boot files. Fix the Linpus Lite error on some computer.
   
   
2. Fix the issue that VTOY_LINUX_REMOUNT can not take effect in latest openSUSE. (#2551)
   
3. Fix the issue when installing on /dev/mdX device. (#2846)
   
4. languages.json update