Any significant change in capability will, no doubt, be important enough to be announced in the accompanying changelogs for future VirtualBox Updates. That's the current reality and the choice for the vast majority who report these issues here.Īt present, the realistically available options for dealing with this 'Warning Message' are to either to dispense with mixing these conflicting virtualisation solutions completely or to learn how to toggle the use of Hyper-V/VirtualBox (or any other conflicting 3rd-party virtualisation software), which is relatively easy, while waiting/testing for improvements over time. If access to Hyper-V is really necessary, then they can't use VirtualBox effectively at the same time.
If someone wants to use VirtualBox and hits this problem then they simply have to completely disable Hyper-V to use VirtualBox effectively. It doesn't change anything, that's the whole point.
