Changes between Version 3 and Version 4 of Ticket #15019, comment 30
- Timestamp:
- Jan 19, 2018 4:54:18 PM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #15019, comment 30
v3 v4 31 31 After following a few links, via "maltem"'s comment, earlier in this thread ( https://www.virtualbox.org/ticket/15019#comment:29 ), it occurred to me to double-check the VirtualBox network adapters, via Control Panel\Network and Internet\Network Connections, and lo and behold, both host-only adapters were greyed-out (disabled). All I had to do was right-click and Enable both and this problem was resolved in my case! 32 32 33 For whatever it's worth, attempts to import a new VM yielded three separate Administrative elevation prompts, all of which I approved, so this wasn't a case of VirtualBox having insufficient permission to do whatever it was trying to do. Furthermore, I tried elevating the Powershell console to Administrator-level access before booting the VM with Vagrant, which made the prompts disappear (because they are of course unnecessary given Powershell's theelevated access), but the error condition did not change.33 For whatever it's worth, attempts to import a new VM yielded three separate Administrative elevation prompts, all of which I approved, so this wasn't a case of VirtualBox having insufficient permission to do whatever it was trying to do. Furthermore, I tried elevating the Powershell console to Administrator-level access before booting the VM with Vagrant, which made the prompts disappear (because they are of course unnecessary given Powershell's elevated access), but the error condition did not change. 34 34 35 35 Also, running the 5.2.6 installer's "Repair" option, which did require a restart (and I obliged), had no bearing on the observed behavior.
