Hi,
I have just downloaded and installed Virtual Box onto a new computer running Windows 7. I believe that version 5 which I have installed is a relatively new version.
During the install I got a message that said something like ‘Your network will be disconnected for a short time’.
After the install finished I am unable to access the Internet, or communicate with other computers on my home network. I have an Ethernet cable to connect to my router.
I have not yet created a Virtual Machine, as I want to know that comms works before added any further complications.
In Network Connections I have a Local Area Connection and a Virtual Host Only Network which is enabled. I have tried disabling this, also I have run various Windows 7 repair tools available in the Control Panel which aren’t able to solve the problem. I’ve also switched both the Windows 7 computer and the router off and on.
I have searched the web and this board for answers (using a different computer), and am unable to find that anyone else has my particular problem. I must admit I’m not particularly expert in internet communications. They normally just work.
Can anyone please suggest a fix?
Regards
Richard
Win 7 comms failed immediately after install of VB rel 5
-
ramblingEdgar
- Posts: 2
- Joined: 14. Aug 2015, 23:13
-
ramblingEdgar
- Posts: 2
- Joined: 14. Aug 2015, 23:13
Re: Win 7 comms failed immediately after install of VB rel 5
Here is an update 24 hours later.
I uninstalled Virtual Box (it was version 5.0.2) and then all comms started working. I then downloaded and installed Virtual Box version 4.3.30 - which appears to be the last of the version 4's.
After this install all comms again work perfectly.
So, my little problem is solved, I guess there was an error in version 5.0.2 (released on 13th August) which caused the difficulties.
Richard
I uninstalled Virtual Box (it was version 5.0.2) and then all comms started working. I then downloaded and installed Virtual Box version 4.3.30 - which appears to be the last of the version 4's.
After this install all comms again work perfectly.
So, my little problem is solved, I guess there was an error in version 5.0.2 (released on 13th August) which caused the difficulties.
Richard