Changes between Version 3 and Version 4 of Ticket #14832, comment 14
- Timestamp:
- Jun 10, 2019 1:53:21 AM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #14832, comment 14
v3 v4 4 4 1) following the somewhat paranoid install instructions floating about with reluctant support people here -- disconnect internet/wifi, drop your Internet etc. protection (didn't uninstall, did turn off the two menu abilities of Norton), de-install VirtualBox, use Run as Admin on the installer, let installer start Virtualbox, then close it, remembering then to turn back on your Internet protection. I believe this dance does nothing, but parts of it might for some?? 5 5 6 2) I found pretty hidden away a similarly cross-your-fingers-and-dance-backwards-three-times fix that's worked for competent-sounding others. This is to locate the actual one of the three Network Interfaces VirtualBox installs that is failing, from the detailed name in the error messag gand hovering over these until you find the one which shows such a label only that way - watch out as the #N numbering doesn't agree with the Windows label. Then: open its settings, _un_check the VirtualBox NDIS6 Bridged Networking Driver, close. Open again, check this Driver to be on. Close. Then Disable this same network adapter, and then enable it again.6 2) I found pretty hidden away a similarly cross-your-fingers-and-dance-backwards-three-times fix that's worked for competent-sounding others. This is to locate the actual one of the three Network Interfaces VirtualBox installs that is failing, from the detailed name in the error message and hovering over these until you find the one which shows such a label only that way - watch out as the #N numbering doesn't agree with the Windows label. Then: open its settings, _un_check the VirtualBox NDIS6 Bridged Networking Driver, close. Open again, check this Driver to be on. Close. Then Disable this same network adapter, and then enable it again. 7 7 8 8 Try a vagrant up, and likely you'll be back on the air.
