Why ? (in general or for this specific case ? i use ventoy myself so i want to know if i should not ^^)
Ventoy is fine for those who actually know how to use it. The issue is most just hear about it and install and use it without knowing what partition type its set to or if secure boot is enabled/disabled for the uefi portion of the disk. Many come trying to install with ventoy with MBR wanting to install to UEFI.
in you should check bios and if secure boot is really disabled drive is not show up at all that means mostly that it is locked down by something may bitlocker or some sort of RAID intel rst could do that.
and yea ventoy is working just fine in 90% of systems. the issue is that it happens very often that users do not fully sync the usb after copy ISO files onto the usb drive.. these flash drives can take like up to 30 Minutes to sync in the most bad case (usb 2 and a very bad quality or old stick)
And if the ISO is not 100% synced on the drive it will act abnormal.
Thanks thats good to know
secure and fast boot are disabled.
UEFI
everything is in gpt.
how do I disable all that?
Can you put in your ventoy disk and give us the following information
sudo ventoy -l /dev/sd?
replace the /sd? with the appropriate letter.
how do I know what the appropriate letter is? the windows assigned letter like D: ?
fast and simple way is to lsblk
This will show all drives connected
chop out the extra l, lsblk
good catch lol
Seems to still only show the (ventoy) usb.
Are we absolutely sure the drive is not locked down by something like bitlocker and/or that BIOS settings are good? Besides secure boot there is also if storage is set to something like RAID instead of AHCI/SATA (we want AHCI/SATA). Is the cable/connection OK?
PS.
lsblk
should not be expected to show anything different from fdisk
.
Just (less) of the same information with less verbosity.
But you can go ahead and try it as well if you want.
What you should try is resetting the Bios to default settings then make sure secure boot is turned off. Make sure the drive settings are set to AHCI. Create a new live usb with another method on Windows such as using etcher. Then try booting on the new live usb and see if there is a difference.