New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vagrant not showing network interface after upgrade to Windows 10 #6076

Closed
diegofersan opened this Issue Aug 1, 2015 · 6 comments

Comments

Projects
None yet
7 participants
@diegofersan

I am having this issue after upgrading to Windows 10.

INFO interface: info: Available bridged network interfac
INFO interface: info: ==> default: Available bridged net
==> default: Available bridged network interfaces:
INFO interface: ask: What interface should the network b
INFO interface: ask: default: What interface should
default: What interface should the network bridge to?

@najawa

This comment has been minimized.

Show comment
Hide comment
@najawa

najawa Aug 7, 2015

I have the same issue:
image

najawa commented Aug 7, 2015

I have the same issue:
image

@diegofersan

This comment has been minimized.

Show comment
Hide comment
@diegofersan

diegofersan Aug 7, 2015

@najawa, try to download last virtualbox version and run windows cmd as admin.
You can see more here: http://migre.me/r5scd

I hope this helps you.

@najawa, try to download last virtualbox version and run windows cmd as admin.
You can see more here: http://migre.me/r5scd

I hope this helps you.

@indominus

This comment has been minimized.

Show comment
Hide comment
@indominus

indominus Aug 18, 2015

i have latest version, but problem still exists

i have latest version, but problem still exists

@klmdb

This comment has been minimized.

Show comment
Hide comment

klmdb commented Sep 11, 2015

+1

@mitchellh

This comment has been minimized.

Show comment
Hide comment
@mitchellh

mitchellh Nov 23, 2015

Member

This apparently is caused by VirtualBox not liking the WIndows upgrade. To fix I've heard you can reinstall VBox and restart. Sorry!

Member

mitchellh commented Nov 23, 2015

This apparently is caused by VirtualBox not liking the WIndows upgrade. To fix I've heard you can reinstall VBox and restart. Sorry!

@mitchellh mitchellh closed this Nov 23, 2015

@nathan-fiscaletti

This comment has been minimized.

Show comment
Hide comment
@nathan-fiscaletti

nathan-fiscaletti Jun 4, 2018

This is still an issue on Windows 10. Running CMD as administrator didn't fix it, Upgrading VB didn't fix it, uninstalling, re-installing and restarting didn't fix it either, nor did any combination of those.

This is still an issue on Windows 10. Running CMD as administrator didn't fix it, Upgrading VB didn't fix it, uninstalling, re-installing and restarting didn't fix it either, nor did any combination of those.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment