Maybe it was because windows update was running in the background?
Could very well have been a factor. I gave up on it quickly. Repeatedly crashing renders it an unnecessary annoyance. VirtualBox works well enough, is stable and reliable, and Veertu doesn't distinguish itself enough to merit the pain in switching.
See new comments of trial I'm running today - I'm replying to my main post as I go.
In fact, it ate my entire CPU while it was running, even when the VM OS (Windows 10) settled down after startup. and was apparently running no CPU-intensive processes.
It also crashed twice in the space of an hour, bringing down the entire VM, necessitating a restart.
Not touching Veertu again for a long time.