Hi, Athough I have to admit, after having run this as administrator
(1) set PATH=.;%PATH% (2) comregister.cmd (3) loadall.cmd Running VirtualBox.exe as Administrator, and only starting the newly created vm, gives me positive results. Failing to start VirtualBox.exe as Administrator gives me *nothing*, and starting any 'old' vms even when running VirtualBox.exe as administrator still gives me the old bug. - Maarten
_______________________________________________ vbox-dev mailing list vbox-dev@virtualbox.org https://www.virtualbox.org/mailman/listinfo/vbox-dev