Steve Si

It sounds like Windows repair is changing the boot sector or maybe boot files on the USB drive. Ventoy and Ventoy utilities will check the contents of the boot sector...

Maybe your have third-party antivirus installed on Windows 11 such as Acronis, Eset, etc.? This may block writes to boot sectors.

That md5 is for UBUNTUDDE REMIX 21.10 (IMPISH INDRI) OFFICIAL RELEASE and so is correct - did you press m on a ventoy drive made with Linux? The other difference...

It may be that there was not enough RAM reported as 'free' by the BIOS. This can happen if you do not do a cold boot from the system each...

You should also try pressing ctrl-r before selecting the ISO (for grub mode).

To check MD5/SHA256, you must boot to Ventoy and select ISO and press m. Is that how you checked the SHA256? i.e. the file on the USB drive must be...

How does ventoy boot memtest efi file? Doesn't it use chainloader? You should set root and terminal_output console before booting to any . efi. Can it do any harm?

Can you give examples of efi files which won't boot using chainloader please? Presumably grubfm cannot boot those efi files?

Why not search the Ventoy Forum for VTOY_LINUX_REMOUNT https://forums.ventoy.net/index.php Did you use the ventoyplugson app to edit the ventoy.json file?

Did you check for unwanted spaces? Can you upload zip file containing your ventoy.json here https://forums.ventoy.net/showthread.php?tid=130&pid=5398#pid5398 Why not use the official app?