Comment 23 for bug 1813165

With Win10 you need to make sure it is not running Hyper-V under the hood (e.g. when you enable Hyper-V role Windows will put itself in a VM -- and thus you will get a nested environment).

To be 100% sure do the following:
# rmmod kvm_intel
# modprobe kvm_intel nested=0

And see if the issue reproduces. In case it does, this is definitely something different, the original bug only affects nested environments.