I can't believe this still hasn't been fixed. I often put off updating VirtualBox because of this issue alone. I just wrote a batch script that modifies the registry for you so you don't have to do it manually after every update: https://gist.github.com/dansmith65/7950823
You will probably have to run it as an Administrator for it to work.
Add the key "*NdisDeviceType" with a DWORD value of 1
-
dansmith65
- Posts: 5
- Joined: 11. Feb 2013, 07:27
-
rpmurray
- Volunteer
- Posts: 918
- Joined: 3. Mar 2009, 00:29
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Windows 7, Mac OS X (various flavors)
- Location: Between Heaven and Hell
Re: Add the key "*NdisDeviceType" with a DWORD value of 1
What's the ticket number of your bug report?dansmith65 wrote:I can't believe this still hasn't been fixed.
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Add the key "*NdisDeviceType" with a DWORD value of 1
Unfortunately, we don't get to set Microsoft's development schedule.dansmith65 wrote:I can't believe this still hasn't been fixed.
Re: Add the key "*NdisDeviceType" with a DWORD value of 1
The workaround should be done on the VirtualBox side - no need to wait for new Windows.
For now: I have found VBS script for VMWare and changed it to work with VirtualBox and added restart of network adapter - see virtualbox.download.oldium.net/VirtualBoxFixNIC.vbs
For now: I have found VBS script for VMWare and changed it to work with VirtualBox and added restart of network adapter - see virtualbox.download.oldium.net/VirtualBoxFixNIC.vbs
| Edit: Updated VirtualBoxFixNIC.vbs to show balloon tip when the update is done (if there was a change) |