Thanks for your help anyway!fth0 wrote:Bummer! Anyway, thanks for trying.
I'm out of ideas for the moment. IMHO, the next step would call for Windows kernel debugging, but I'm not savvy enough for that (yet). I'll post my current state of knowledge to the Bugtracker (possibly in #20165), either tonight or tomorrow, and then we'll have to wait if or when we'll get any reaction from the VirtualBox developers.
I'm willing to do other testing if necessary.
That ticket seems pertinent and I've commented on it, but it's not correctly categorized and maybe a more descriptive title would be better?