Ahhh, the mention of a lawsuit got your attention. Repeat after me, as your arrogant self put it, say once again the words "repeat after me" and you WILL BE SUED. Get it. I paid for your commercial version expecting tech support. If I don't get tech support one-on-one now and get it without the smart-ass, then we'll take it from there. And you won't be happy with the outcome, I can promise you. You, NeoSmart, imply in legally identifiable places that your software will dual boot "almost anything" from the Windows boot manager. You don't really say what the exceptions are and I'm more than a week into the process to find out that, given the exceptions you've just described, the reality is not really what the website says.
Where does it say the following: "A PC with legacy boot enabled can use the legacy BOOTMGR, but that does not automatically mean it will do so. If you (ever) booted Windows in EFI mode, it will continue to use the EFI bootmgr bootloader forevermore." Clearly, I loaded Windows 10 without a clue what a UEFI was or how the boot logic might have changed, as did 99.999999% of people who were forced on to Windows 10.
I'm not completely sure my system ever booted into Ubuntu after I moved to Windows 10. I did rebuild my five or six computers on new naked 1 tb SSD drives about six months to a year ago. And it is possible that I lost the Ubuntu dual boot then. Could be. I doubt it but can't rule it out which is more honesty that your website provides.
On the other hand, if you want to get real and try to solve my problem or, could be, show me civilly that it can't be solved, I'm open to preceding amicably. I am using what I understand to be the legacy bootmanager - at least I think I am - but I have no idea what the phrase "does not contain a trace of the UEFI configuration" could possibly mean. What I do know is that I can't escape the grub4dos "bug". Whether that's an EasyBCD "bug" or a Windows "bug" or an Ubuntu "bug" I have no idea.
Where do we go from here?