VMWare bridged network is not working after upgrade to Windows 10 Insider Preview

All replies

• 

  

  0

  Sign in to vote

  This is a question for VmWare I guess...

  ---

  This post is provided AS IS with no warranties or guarantees, and confers no rights.
  ~~~
  Questo post non fornisce garanzie e non conferisce diritti

  Thursday, May 21, 2015 8:02 AM
• 

  

  0

  Sign in to vote

  I don't think so.
  
  The problem is that, since 10049 I think, it is not possible to add additional services to a network card in Windows 10.
  Trying to do it and you receive this:

  

  As VMware Workstation wants to install an additional service to allow the physical NIC to be used in VMware Virtual Networks, this functionality is currently broken. Same problem for Cisco Network Access Manager.

  Gerald

  
  

  • Edited by Gérald Mathieu Thursday, May 21, 2015 8:40 AM

  Thursday, May 21, 2015 8:35 AM
• 

  

  0

  Sign in to vote

  Well there might be some sort of bug but it could also be some change that requires developers to change the way they used to access certain functionality. You won't be able to install Wordstar 4 either, that doesn't mean W10 is broken.

  ---

  This post is provided AS IS with no warranties or guarantees, and confers no rights.
  ~~~
  Questo post non fornisce garanzie e non conferisce diritti

  
  

  • Edited by aperelli Thursday, May 21, 2015 8:44 AM

  Thursday, May 21, 2015 8:44 AM
• 

  

  0

  Sign in to vote

  The error message in my screenshot comes directly from the Windows 10 NIC properties.
  If it's not possible for Windows 10 itself to install additional features to the NIC, I doubt that VMware or Cisco can fix the problem.
  
  Just try, open your NIC properties, click on Install then select something to add to the configuration.

  Gerald

  Thursday, May 21, 2015 9:12 AM
• 

  

  0

  Sign in to vote

  Ok, that makes sense, I thought that was coming from VmWare. Then it's a bug

  ---

  This post is provided AS IS with no warranties or guarantees, and confers no rights.
  ~~~
  Questo post non fornisce garanzie e non conferisce diritti

  Thursday, May 21, 2015 9:14 AM
• 

  

  1

  Sign in to vote

  Yes and it has been reported in Windows Feedback several times.
  Maybe Microsoft just don't want us to install additional features on the NIC for the moment :-)
  
  Anyway, the only fix the poster can use for the moment is to configure his VM Ethernet adapter to use the NAT functionality instead of Bridged.

  

  Gerald

  • Proposed as answer by Yolanda ZhuModerator Monday, June 8, 2015 7:53 AM
  • Marked as answer by EMMmmmmmmModerator Tuesday, June 9, 2015 9:50 AM

  Thursday, May 21, 2015 9:29 AM
• 

  

  0

  Sign in to vote

  Confirmed.  I'm having this same issue on Build 10130.

  Tuesday, June 9, 2015 6:18 PM
• 

  

  0

  Sign in to vote

  There is also an issue in VMware Player on Build 10130. The problem revolves around installing the network services, there are issues installing the network services to the Ethernet adapter for not only VMware Bridge Protocol which gives the error:
  
  Could not add the requested feature. The error: is: Class not registered

  This error is the same error that is displayed if you try to install Microsoft Hyper-V Virtual Switch Extension Filter.

  If you try to install:
  
  Microsoft MAC Bridge, NDIS Capture, Windows Filtering Platform, the list goes on.

  It says Could not add the requested feature. The error is: This program is blocked by a group policy. ETC,ETC.

  So I'd imagine the problem isn't with the VMware drivers it's an issue within windows.

  Any ideas if there may be a fix down the pipe?

  • Edited by AsusExtreme6PC Friday, June 12, 2015 3:39 PM

  Friday, June 12, 2015 3:15 PM
• 

  

  0

  Sign in to vote

  There is also an issue in VMware Player on Build 10130. The problem revolves around installing the network services, there are issues installing the network services to the Ethernet adapter for not only VMware Bridge Protocol which gives the error:
  
  Could not add the requested feature. The error: is: Class not registered

  This error is the same error that is displayed if you try to install Microsoft Hyper-V Virtual Switch Extension Filter.

  If you try to install:
  
  Microsoft MAC Bridge, NDIS Capture, Windows Filtering Platform, the list goes on.

  It says Could not add the requested feature. The error is: This program is blocked by a group policy. ETC,ETC.

  So I'd imagine the problem isn't with the VMware drivers it's an issue within windows.

  Any ideas if there may be a fix down the pipe?

  Using NAT isn't a fix. It's not only vmware protocols that are broken it's a windows problem. I tried on 2 different machines with 2 different network cards same thing.

  This works great in windows 8 and windows 7.

  Any ideas other than NAT?

  Saturday, June 13, 2015 6:37 AM
• 

  

  0

  Sign in to vote

  This user is stating that bridged networking is working on Windows 10 Build 10147: https://communities.vmware.com/message/2517570#2517570

  I can't try it myself because my Windows 10 Enterprise Insider Preview key is not allowing me to proceed with the install.

  Friday, June 19, 2015 9:43 PM
• 

  

  0

  Sign in to vote

  Yep, confirmed working on build 10147.

  Saturday, June 20, 2015 4:35 AM