Problems booting Windows/WinPE ISOs using ventoy_grub F6

[vshanecurtis]

Hello,
I am hoping that someone here can help me understand the process that Ventoy uses to boot Windows ISOs and WinPEs. I am having difficulties using the F6 option because I do not understand the commands needed to boot a Windows ISO or WinPE using GRUB. Since Ventoy is able to do this then it is possible to duplicate the process with Grub commands. I would prefer to use the F6 option because it allows me to organize the menu to suit my tastes rather than simply listing them. I prefer to group my ISOs according to functionality such as Disk Management, Disk Imaging OS Distributions and so on. I would be grateful if someone could assist me with this issue.

[steve6375]

This question has been raised several times with the author, LongPanda. Certain internal parameters need to be set apparently and it is not as simple or very easy to just point an ISO, etc. at an internal function. The author does not support such a usage unfortunately.

[vshanecurtis]

If he's going to produce a product and questions are raised about its operation, then he needs to answer them, especially since Ventoy boots these ISOs in "native" mode. "Sorry about your luck" is an unacceptable answer

…

________________________________ From: Steve Si ***@***.***> Sent: Friday, February 28, 2025 4:34 AM To: ventoy/Ventoy ***@***.***> Cc: vshanecurtis ***@***.***>; Author ***@***.***> Subject: Re: [ventoy/Ventoy] Problems booting Windows/WinPE ISOs using ventoy_grub F6 (Discussion #3143) This question has been raised several times with the author, LongPanda. Certain internal parameters need to be set apparently and it is not as simple or very easy to just point an ISO, etc. at an internal function. The author does not support such a usage unfortunately. — Reply to this email directly, view it on GitHub<#3143 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BNWXRM3OAZYCRSFQ6KKTYFL2SAURVAVCNFSM6AAAAABYBQ4JNGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMZUHE2DOMY>. You are receiving this because you authored the thread.Message ID: ***@***.***>