Windows Insider killed my Virtual Box

mikejbird · 23 Nov 2020

Evaluation copy. Build 20231.rs-Prerelease 201002-1444
Who do I scream at at Microsoft for buggering my system.
I made a huge mistake of signing on to the Insider Program back in May.
What harm could it cause thought I?
Now my boot time is 20-30 mins.
I just tried to go to VirtualBox and it caused a reboot.
It took me days to setup VirtualBox so that I could run my Microfocus Cobol 5.1 compiler in an XP environment.
I turned off the insider program about a month ago.
I think my system is stuck between versions.
I'm so pissed off with Microsoft. Who do I complain to? Nobody...

cereberus · 24 Nov 2020

Look in a mirror and you will see the person you can blame.

It is made very clear Insider versions are test versions and may have bugs.

Reinstall the release version from scratch, then look at your reflection in the mirror silently for a minute and then tell yourself that you will learn how to make image backups.

sdowney717 · 25 Nov 2020

Cant you maintain 2 bootable win10 versions, like one is regular windows releases, and the other is insider releases? That seems like the way to go. Lets you experiment and see what happens with the one, but you still have the other. I honestly dont know, but I dual boot 2 versions of 10 on my 2 in 1 ASUS notebook PC.

f14tomcat · 26 Nov 2020

sdowney717 said:

Cant you maintain 2 bootable win10 versions, like one is regular windows releases, and the other is insider releases? That seems like the way to go. Lets you experiment and see what happens with the one, but you still have the other. I honestly dont know, but I dual boot 2 versions of 10 on my 2 in 1 ASUS notebook PC.

Yes, you can dual boot on same machine, or triple boot, or in my case septuple boot. Yeah, 7 of them, same machine.

ASCiiDiTY · 27 Nov 2020

A few builds ago it made me uninstall VB before letting me go to the new version, it hasn't been supported in these builds for a while. Somebody mentioned disabling hyper-v as a solution but I didn't look into it.

Ztruker · 29 Nov 2020

There was a while when Hyper-V and VirtualBox did not co-exist. One or the other had to be disabled. I thought that was fixed a while ago but they very well may have broken it again.

Hopachi · 30 Nov 2020

Ztruker said:

There was a while when Hyper-V and VirtualBox did not co-exist. One or the other had to be disabled. I thought that was fixed a while ago but they very well may have broken it again.

Last time I tried with both installed, VirtualBox (6.1.12) was running under the 'green turtle' icon instead of the VT chip. Was way too slow than normal, guessing that co-existence is still work in progress. 64bit VMs failed to start back then.

I didn't tried VirtualBox 6.1.16 yet to check, but there were some fixes applied regarding systems with enabled Hyper-V.