For many people using VMware Workstation they should be aware of an issue which occurs after updating Windows 10 to the new Windows 10 Anniversary. In fact I have run across this issue with other major Windows 10 updates.
After performing a major update to Windows 10 VMware Workstation’s VMnet0 is removed. The removal of VMnet0 breaks the network connection for guest Virtual Machines. To repair connectivity for the guest Virtual Machines you can add a new virtual network or set the Virtual Network back to their default settings. If you set the VMware Workstation network back to default settings you will lose any and all custom networks.
How to fix bridged networking in VMware Workstation after applying Windows 10 update (Threshold 2)
How to fix bridged networking in VMware Workstation after upgrading to Windows 10
The other day I was prompted to install an update for my HP Printer however the update failed every time I attempted to apply it. After searching the web I found out that you can Show and/or Hide Windows 10 updates. Microsoft’s official KB page can be found here: Windows 10 Show or Hide updates trouble shooter.
I found a similar post on HP Forums: Error 0x80070490, Error 0X8024200b – Windows 10 / Windows Update.
Below are the steps within the Windows 10 Show and/or Hide updates:
As you can tell from the screenshots I chose to hide the HP “NULL” device driver as the update would not install.
A couple of days ago I updated my Windows 10 workstation with the new “Windows 10 Threshold 2” update. Once the upgrade was complete I launched VMware Workstation 12 Pro and noticed that my Virtual Machine did not have network connectivity.
Based on my past experience when upgrading from Windows 8.1 to Windows 10 I discovered that VMware Workstation’s VMnet0 was removed. Due to this previous experience it made sense to check VMware Workstations “Virtual Network Editor” to confirm if VMnet0 had been removed again. Sure enough the same problem existed after applying “Windows 10 Threshold 2.”
To restore “Bridged Networking” in VMware Workstation you have to re-add VMnet0. In order to add VMnet0 you’ll need to restore your default network settings. Be warned though as any custom network configurations will be lost when restoring your default network settings. See my past post here: VMware Workstation Bridged Network Failure after upgrade to Windows 10.
If you have any issues restoring Bridged Networking please reply to this post or send me a note via the Contact Page.
The other day I built a Virtual Machine to test errors I experienced in Outlook 2010. I applied the latest Windows Updates to the Virtual Machine however when I was prompted to update .NET 4.5.2 (KB2901983) I received the error code 13EC.
To resolve the Windows Update error code 13EC for KB2901983 I had to expand the virtual drive. My Virtual Machine had roughly 2 GB free prior to applying the update so I expanded the virtual disk by 5 GB and the update applied successfully.
If you have a physical machine then the issue is likely your C drive (operating system drive) is either full or to small.
Microsoft answers.microsoft.com has a related post: click here.