This morning I get trouble getting VirtualBox running after I upgrade Windows 10

After Windows announces the free upgrade to its brand new Windows 10, I made a reservation of Windows 10. The upgrade surprisingly fast en smoth. I was surprised to get rid of it without any trouble, until I tried to run my VirtualBox.

Maybe you faced the same problem. It may not be strange for you, people using VirtualBox on Windows host machine.

Any attempt to run VirtualBox prompts error message, that something with kernel is stopped, or not started. But if you change the Network settings of the virtualmachine from the “Bridged Network” to “NAT” or to “Intern Network”. It works fine. With these settings I was not able to access the virtualmachine from outside. I could not connect via SSH or via Samba the machine.

CONCLUSION:
Windows 10 upgrade screeded up the brigde networking internal for VirtualBox 4.3.30 and prior version.

Luckily I found the solution to this annoying issue (trouble).

If you faced the same problem as I did, this perhaps can help you to fix the problem, while waiting Oracle or Windows come up with the fix for this issue.

Here are steps to follow:

1. Disable opened network adapters on Windows 10

2. Download VirtualBox 5 from https://www.virtualbox.org/wiki/Downloads and then install it

3. Start the virtualbox, then set the Bridged Network settings as you actually did before the issue

4. Re-enable the network adapters, you disabled on Windows 10

5. Run virtualmachine, then enjoy.

That is all.