I re-read all this topic since the begining, and it seems starting with the 2020-12-05 version I loose the capability to Filedisk boot when running some tests.
From my post: http://reboot.pro/to...e-4#entry217218
And now I have a new issue, during this new tests I was UEFI booting from the Win10XPE_x64.ISO to make certain editions to the menu.lst and copying some files. etc, it was booting very fine more than 5 times until it do not fully load anymore, the loading line remains forever about 1/3 from the beginig and never moves, replaced it with the copy on my USB and same thing, tryed with and old version and then the classic message boot_image_handle not found, so now it can load any other ISO but not that one (from any partition, as tried several).
I replaced latter the boot.sdi file into Boot file on the FAT-32 UEFI bootable partition of my internal HD and also the WinPE.ISO and the problem persisted, and also tested MBR booting same ISO and it boots fine.
Latter I read some info related to this issue in the case of WinPE ISOs on wuyou.net forum about this issue may be caused by corruption of the boot.sdi file into the ISO because of repeated failures, but as I replaced the full ISO this may not be the cause in my case.
And latter from wimb post: http://reboot.pro/to...e-4#entry217233
VHD WIMBOOT map and map --mem in UEFI Grub4dos Failed with boot_image_handle not found .....
From Vortex post: http://reboot.pro/to...e-6#entry217272
The purpose of my second test was to boot the same Vhd as filedisk but I received the error message INACCESSIBLE BOOT DEVICE on a blue screen. Attached are the screenshots. I also tested the option map (hd0,gpt3)/Win10.vhd. Same result.
From wimb post: http://reboot.pro/to...e-6#entry217275
My Mini10_SV.vhd (MBR FAT32+NTFS) booting OK as RAMDISK also fails to boot as FILEDISK when using New UEFI Grub2 and menuentry
menuentry "Mini10_SV.vhd as FILEDISK" {
map --rt (hd0,gpt2)/VHD/Mini10_SV.vhd
boot
}
I also can confirm when trying to Filedisk boot a Mini-10 VHD with G4E it fail.
Then it seems Filedisk booting a WinPE ISO or a Win VHD is failing.
I'm reluctant to test this again because it will created ghost virtual CDs when Rambooting a VHD, and at the moment I don't have any, and it was not very easy to get rid of them on 5 VHDs.
alacran