VMware Communities
aldreyribeiro
Contributor
Contributor
Jump to solution

Bridged network does not work - Cannot change network to bridged: There are no un-bridged host network adapters - workstation pro 15.5.6

Hi,

My windows 10 pro has been updated to the 2004 version. After opening the workstation pro, I did the automatic update to version 15.5.6.

After all, the bridge network was no longer available. In device management, the network drivers (VMnet0,1 and 😎 have an exclamation sign. I tried to update but to no avail.

In the Virtual Network Editor, when I try to change VMnet0 to Bridged, I received the message:

Cannot change network to bridged: There are no un-bridged host network adapters.

I uninstalled VMware workstation pro 15.6, reinstalled versions 15.5.1, 15.5.2, and 15.5.5, but in all cases, the bridge network does not work.

I have several VMs, but all using the NAT network. Today I went to create a VM with a bridged network and saw that it was not connecting.

1 Solution

Accepted Solutions
aldreyribeiro
Contributor
Contributor
Jump to solution

After uninstalling and installing practically all versions, I decided to try a program to repair the Windows registry (Glary Utilities) and after performing the procedure, I reinstalled vmware workstation and everything was working. The good thing is that I didn't have to format the PC.

View solution in original post

Reply
0 Kudos
13 Replies
haiweiz
VMware Employee
VMware Employee
Jump to solution

Try to uninstall Workstation 15.5.6 then reboot host, download installer from website and install 15.5.6 again.

Sound like your OS refuse to install/upgrade all VMware network adapters, please collect the support data and upload to us.

Reply
0 Kudos
Gnart
Contributor
Contributor
Jump to solution

I have the same/similar problem. Host is on Win10 2004 and VMworkstation 15.5.1. The bridged guest VMs didn't have any problem. I upgraded to VMworkstation 15.5.6 for concurrently running Hyper-V hypervisor.

Existing guest machines using bridged network no longer have access to the network.

I uninstalled and reinstalled VMworkstation 15.5.6, it did not solved the problem.

I uninstalled the NIC/Driver in Win10 guest and restarted the guest so that Win10 device manager would re-installed the NIC/Driver that didn't work.

Win10 Device Manager showed no problem (no exclamation mark).

I changed VMworkstation virtual network VMNet0 Bridged from Automatic to the physical NIC (Intel(R) Dual Band Wireless-AC-3160 - Wi-Fi), it didn't solve the problem.

I created a new Win10 2004 guest to test, it didn't work in bridged mode.

I disabled the host Wi-Fi and enabled the wired network interface (Realtek PCIe Fe Family Controller) to perform further test.
VMworkstation guess VMs would only work in NAT.
The guest VMs showed a virtual Intel(R) 82574L Gigabit Network Connection NIC.

To All having this problem: VM bridged guest has no access to bridged network, change it to NAT until this problem is fixed.

Reply
0 Kudos
lgrullon22
Contributor
Contributor
Jump to solution

I am disappointed VMware haven't dedicated resources to this bridging issue...I am hoping their upcoming release 16 next month have the answer to the bridging issue.

loungehostmaste
Enthusiast
Enthusiast
Jump to solution

this is mainly a windows problem, on Linux the network configuration on my machine is untocuhed for years now and similar issues 10 years ago with "VMware Server" where a routine update damaged the config was the reason to throw away Windows from the host and move it where it belongs: into a virtual machine, still not perfect because the useless installer instead pachages or a simple tarball but way better then windows installers

Reply
0 Kudos
lgrullon22
Contributor
Contributor
Jump to solution

Still your comments do not address resolution to the actual issue we are experiencing.

aldreyribeiro
Contributor
Contributor
Jump to solution

After uninstalling and installing practically all versions, I decided to try a program to repair the Windows registry (Glary Utilities) and after performing the procedure, I reinstalled vmware workstation and everything was working. The good thing is that I didn't have to format the PC.

Reply
0 Kudos
billrothjr
VMware Employee
VMware Employee
Jump to solution

The following worked for me with WS 16 on Windows 10 Version 10.0.19045 Build 19045. 

 

  1. Go into the network editor
  2. Pick "Restore Defaults"
  3. vmnet0 sets it self up to autobridged
  4. changed autobridged to the ethernet interface I know is working
------
Bill Roth, VMware
Reply
0 Kudos
Iain3
Contributor
Contributor
Jump to solution

I have tried to upgrade to workstation 17, the installer is a joke just hung on everything, that's after I had to end task Workstation 15 as it was stuck and didn't handover to the upgrade properly. there are so many issues all over the community about this and nothing has been done. After 6 hours I'm having to give up and looks a like a complete rebuild of Windows 10.

Don't VMWare test anything???

Reply
0 Kudos
GaryBrouwers
Contributor
Contributor
Jump to solution

Same problem. After "upgrading" to 17.0.2, all virtual networking was removed. After "Restore Defaults", there is no VMnet0 anymore and no way to set up a bridged network; only get the infamous "there are no unbridged network adapters" message. It appears to be an issue updating. If you have a working system, I would recommend not updating.

Reply
0 Kudos
GaryBrouwers
Contributor
Contributor
Jump to solution

Upgrading to 17.0.2 caused the "no un-bridged network adapters" issue for me. "Restore Defaults" does nothing to fix it. After "Restore Defaults" I just get VMnet1 and VMnet8... no VMnet0 no auto-bridge, and no way to set any adapter to "Bridged" without getting the error. This is a bad issue.

Reply
0 Kudos
aldreyribeiro
Contributor
Contributor
Jump to solution

Recently, I had the same issue. Now with VMware Workstation 17.0.2
In this case, my problem was the Kaspersky Endpoint Security installed on my computer. To resolve this, I removed both (Vmware Workstation and Kaspersky Endpoint Security), reinstalled VMware Workstation 17 first, then install Kaspersky again.
After that, everything works fine.

Reply
0 Kudos
GaryBrouwers
Contributor
Contributor
Jump to solution

Ugh, thanks. I have to have the IT department uninstall/re-install the antivirus. Unfortunately I think I've run out of other suggestions.

Reply
0 Kudos
GaryBrouwers
Contributor
Contributor
Jump to solution

Yeah, the uninstall antivirus, uninstall VMWare, install VMWare, install antivirus, was the only path we could get to work. At my company, I.T. is the only ones that can do the steps involving antivirus, so we tried to come up with an easier/faster way, but nothing else worked.

Reply
0 Kudos