- use WofCompress to UnCompress EFI and Boot folder inside VHD instead of renaming as x-EFI and x-Boot
UnCompressed EFI folder inside VHD is needed for booting 2 Partition VHD from RAMDISK using UEFI Grub4dos aka G4E
More Info: here
Excuseme my friend but I disagree with this. It is possible it may work fine for you because your PC firmware has NTFS driver, but it do not apply on all cases, it is more common the UEFI firmwares only have FAT drivers.
Let me put it this way:
Using UEFI grub4dos version 2020-12-15 (first version that optionally allows to load ntfs_x64.efi driver):
On two partitions VHDs having both folders as real size files on FAT-32 partition is enough.
And if we have those folders on the NTFS partition and using UEFI grub4dos version upto 2020-12-15 the boot will fail, because it starts looking for EFI folder on last partition (NTFS) first, unless (I assume as I can't test it) the user PC has NTFS driver on its firmware (which is your case).
On single NTFS partition VHDs, both folders require to have real size files and depending if the user PC do not has NTFS driver on its firmware, also load first the ntfs_x64.efi is required.
Using UEFI grub4dos version 2020-12-26, (not released yet) please see this post and the next one.
On two partitions VHDs. Boot and EFI folders can exists having real size files, on FAT-32 and on NTFS partition without any issues as now this version is coded to start looking for EFI folder on the active partition FAT-32 (in this case), first (not on the NTFS as before), and the folders on NTFS partition are totally unnecessary and a waste of espace if we have two partitions, because they are not used.
On single NTFS partition VHDs. the conditions remain the same as on older versions: both folders require to be real files and depending if the user PC do not has NTFS driver on its firmware, also load first the ntfs_x64.efi is required.
NOTE: In all cases files have to be not compressed, or real files and no pointers in the case of Wimboot installs.