Oracle VirtualBox 4.x not Starting when upgrading the Windows 8 to Windows10//Workaround

I had been running Windows 8 with Oracle VirtualBox 4.x.y.  As the upgrade completed and I tried to Launch Virtual Box it was not starting. 

Also I had been using BroadBand Connection over wi-fi to connect my PC to the internet. 

Here are the series of steps which was needed to be done to get my VirtualBox and VMs up and running and be able to connect to the internet.

1) Download and Install the latest Oracle VirtualBox from the site 

https://www.virtualbox.org/wiki/Downloads

I downloaded and installed Oracle VirtualBox 5.0.4

2) After installation the Virtual Box will start 

3) for the VMs if you see the configuration related issues for USB, select USB 1.1 or if you are not using USB Support for the VMs, deselect that option from VM Configuration and save each VM configuration,

This was enough to make my VMs up and running but  I had lost connectivity to the Internet and CentOS/Fedora Online repositories. NSLOOKUP to google.com was also not working.

1) The problem was my ISP gave my PC an IP 192.168.x.x and I was also using the IPs 192.168.10.x for my VMs. As I started the VMs I lost the connectivity over Wi-Fi to the Internet from my PC

2) TO get around this, I deleted the Network Interface which I was using for VirtualBox VM Network

a) Start the "Oracle VM VirtualBox Manager" -> File -> Preferences -> Network -> Host Only Networks 

Delete the Network 

b) Add a new network -> In the Adapter Section: Set an IPv4 address which is a different network than 192.168.x.x (as this network is what was being provided by my ISP)

So i gave an IP address of 193.168.10.1./24 

You can infact select any IP address here as these are for Internal Access to the VMs from your PC so it should be fine.

c) Now Open the Virtual Machine Configuration settings - > Network - > Adapter2 -> Ensure that this is set as "Host Only Adapter" and "Name" corresponds to the New adapter which you just defined for the VMs to use in the eralier sep

This was however not enough as in the CentOS/Fedora VMs i had been using eth1 still with 192.168.10.x IPs

Boot the VM, go to the console of the booted VM and edit the IPADDR in /etc/sysconfig/network-scripts/ifcfg-eth1 to IP belonging to the IP network which was defined earluer

I used 193.168.10.103 with 255.255.255.0 and restarted the network services suing either

systemctl restart network.service (for CentOS 7 and FC on higher versions) or

service network restart on (CentOS 6 and less and FC lower versions)

Happy Learning !