You are over 1.5 years late on your promise to resolve this conflict.
You could at least provide an update. You know, good faith communication with interested users. Don’t keep us in limbo. Limbo is the sign of a company destined to abandon all its users.
Are you still working on it?
Have you abandoned the project? (just let us know)
Do you have any work around that potential users can try?
At the very least you can List The VirtualBox / Hyper-V conflict on the downloads page, or system requirements page !!!
It is difficult to find out what the install issue is, even on your website.
This knowledge is too hidden.
You cause countless people to repeat the same frustrating search, even just to learn what the issue is.
You should just state conflict, and basic reasons for the conflict: (docker, default win 10 setup, etc).
I’m certain, many just give up, before even finding out.
And if that part is frustrating enough, why ever look at Flywheel again:
- That company’s software won’t even install!
- And the error message is not helpful.
- And “nothing” useful about the error is on their website. (well, at least not easily found).
- They aren’t upfront with info.
- They make empty promises. And don’t communicate.
It’s like a huge dirty secret that you are trying to hide.
Better to be upfront, and communicative.