I found myself redeemed. Kali Install ISO was unable to fix the botched Grub2 USB install it did. Bootice wasn't smart enough to get G2 pieces together. Grub4DOS while installed in USB thumb MBR by Bootice failed to boot Kali from the USB, and generally failed at all counts executing commandline. The only winner I found after sleepless nights was, of course, venerable ship captain from Outside of the Asylum with best links around, but also... a step behind... Boot Repair Disk.
While booted both in VMWare or from Rufus scalped USB thumb by BIOS, it created comprehensive and quite readable report about multiple bootable entities on my PC, and - the most important - pinpointed the problem namely with Kali USB, suggesting to reinstall Grub2 on it. I reluctantly agreed knowing many possible undesirable consequences for my entire system. But - a minute later Kali USB was fixed, no other drives touched at all.
And the next moment I already booted Kali USB installed distro from BIOS. Basically, Boot Repair Disk substituted something dropped on disk by Kali Installer with very capable Grub 2, both in MBR and the right partition folders. Now inhabitants of this ship have bright record, and morally fully prepared to storm "boot kali from VHD" fortress.
Have recently shifted to using UEFI since I installed Windows 11 and now I find that EasyBCD won't work with UEFI, so have tried AIO Boot, Ventoy, Grub2win, clover and a few more before settling on grub2win finally which boots linux/win fine with secureboot enabled (using shim.efi)
download easybcd for kali linux
Download Zip
https://inli-inde.blogspot.com/?u=2wYh6V
I tihnk EasyBCD used neogrub or chainloading or some shit to boot the linux VHDs and didnt ask for any boot file, just the path to VHD, while BootICE seems to need some boot file (like grub.efi / shim.efi / ubuntu.efi i guess)
Before wasting time in all sorts of permutations/combinations I just wanted to check whether anyone knows how to create BCD entry for a linux vhd boot ? Installing to VHD was not a problem earlier at least.
If i remember correctly (the vhds were created a couple of years back - been just updating them since then) i had done the linux VHD installations with Hyper-V or by creating a file as a raw disk image with DD and formating and mounting it and then chrooting into it before running the linux installation.
There's only enough space on SSD to boot win11 from 1 partition and elementary linux from 2nd and keep a 3rd data partition. So VHDs were good as compared to using say 65GB USB3 pendrive etc which were much slower compared to SSD.
While updating some drivers on win11 The grub menu disappeared and system start to boot direct into win11. So i looked it up how to bring grub menu back. I used EasyBCD tool to add Kali linux boot option but when i rebooted it was different it wasn't like previous setups, previously grub was directly loaded now it first load Window Boot Manger and then from there I have to select Kali linux then it launch Grub menu Again with its own Kali and win11 options.
Things were different from previous setup but Everything was fine and i can boot into both Kali and win11. But then I want it to be fixed to i looked it up and set Kali Linux boot option as default in EasyBCD in win11 and set timeout to 0 so it directly load grub. here all the problem started in my opinion I thought by doing this I will load grub from where I can load win11 and Kali linux but I had already set timeout to 0 and made kali default so it went into kind of a loop when try to boot win11.
35fe9a5643