Opened 14 years ago
Closed 8 years ago
#7614 closed defect (obsolete)
Bridged Adapter Name not available
| Reported by: | stalky | Owned by: | |
|---|---|---|---|
| Component: | network/hostif | Version: | VirtualBox 3.2.10 |
| Keywords: | Bridge | Cc: | |
| Guest type: | Windows | Host type: | Windows |
Description
Updating from release 3.2.8 to 3.2.10 I found some of my VM cannot start (crash, sorry I forgot the error code). After some further investigation the issue was that the Bridged Adapter name has been reset and it was not possible to set it again. So to use VM with a bridge connection I was forced to go back to release 3.2.8.
Change History (3)
comment:1 by , 14 years ago
| Component: | network → network/hostif |
|---|
comment:2 by , 14 years ago
comment:3 by , 8 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
Note:
See TracTickets
for help on using tickets.
Am I getting you right that the list of available bridged interfaces is empty in network settings gui for 3.2.10? If so, could you attach msi & setupapi logs for your 3.2.8 uninstall & 3.2.10 install.
Note: since setupapi logging actually always appends the log data to the already existing one, please remove the setupapi log files before each test (i.e. 3.2.8 uninstall & 3.2.10 install) to have distinct logs for each test.