| 1 | <?xml version='1.0' encoding='UTF-8'?>
|
|---|
| 2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
|---|
| 3 | <topic xml:lang="en-us" id="ts_win-host-host-only-network-adapters">
|
|---|
| 4 | <title>Host-Only Networking Adapters Cannot be Created</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p>
|
|---|
| 8 | If a host-only adapter cannot be created, either with the
|
|---|
| 9 | <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> or the <userinput>VBoxManage</userinput> command, then
|
|---|
| 10 | the INF cache is probably corrupt. In this case, the install log
|
|---|
| 11 | at <filepath>%windir%\inf\setupapi.dev.log</filepath> would
|
|---|
| 12 | typically mention the failure to find a suitable driver package
|
|---|
| 13 | for the <filepath>sun_VBoxNetAdp</filepath> component. Again, as
|
|---|
| 14 | with the bridged networking problem described above, the
|
|---|
| 15 | solution is to uninstall <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, remove the INF cache
|
|---|
| 16 | (<filepath>%windir%\inf\INFCACHE.1</filepath>), reboot and try
|
|---|
| 17 | to reinstall <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
|
|---|
| 18 | </p>
|
|---|
| 19 | </body>
|
|---|
| 20 |
|
|---|
| 21 | </topic>
|
|---|
