scrublord
Contributor
Contributor

VMware cannot install Network Adapters / Drivers

Jump to solution

My VMware installation spontaneously stopped working properly, and now my VMs can no longer connect to each other or the internet. Their network device drivers are seemingly broken, and reinstallation or repair do nothing to solve the problem. 

This has been brought up several times before without resolution - 

https://communities.vmware.com/t5/VMware-Workstation-Player/Installer-stuck-at-Installing-Network-Dr...

https://communities.vmware.com/t5/VMware-Workstation-Player/host-only-adapter-driver-does-not-seem-t...

Here is some info about my setup:

Host OS - Windows 10 Pro

scrublord_0-1627400747325.png

VMware Version - Workstation 16 Pro

scrublord_1-1627400798663.png

Virtual Machine Operating Systems - Windows 10 Enterprise and Ubuntu 18

scrublord_2-1627400965634.png

scrublord_3-1627400976941.png

The VMs are set to the "NAT" configuration.

When I try to reinstall, repair or just restore defaults in the Virtual Network Editor, VMware gets stuck whenever "Installing network adapters" or "Installing virtual network drivers"

scrublord_4-1627401253638.png

 

scrublord_5-1627401291496.png

As you can see, there is an unresponsive process called "VMware network install library executable". If I use the Task Manager to open the file location, I see that this corresponds to an executable called "vnetlib64":

scrublord_6-1627401402132.png

Eventually, after several minutes, the process seemingly just quits without any further communications to me, and the setup is left unchanged: 

scrublord_7-1627401454803.png

Checking for the virtual adapters in the Device Manager, I can see that they are broken:

scrublord_8-1627401515641.png

I can also see that their drivers are either not present or not working:

scrublord_9-1627401539943.png

I don't see any sign of anything VMware related under my Network Connections:

scrublord_10-1627401561364.png

Previously, a person called "continuum" suggested checking the registry at HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ROOT\VMWARE\0000
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ROOT\VMWARE\0001

to see if the install was complete, so here are screenshots of that:

scrublord_11-1627401700122.png

scrublord_12-1627401709040.png

My "vminst" file in %tmp% is MASSIVE, but here are the latest entries:

Spoiler
2021-07-27T11:24:08.613-04:00| inst-build-16894299| I2: VNL_GetVnetAdapterStatus: searched for adapter 'VMnet16': installed=FALSE IP=FALSE IPX=FALSE
2021-07-27T11:24:08.614-04:00| inst-build-16894299| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-07-27T11:24:08.614-04:00| inst-build-16894299| E2: GetIPv4Key: address not found for 'VMnet16': IPSubnetAddress
2021-07-27T11:24:08.614-04:00| inst-build-16894299| I2: GetVnetParameter: vmnet: 'VMnet16' 'NAT' 'UseNAT'
2021-07-27T11:24:08.614-04:00| inst-build-16894299| E2: GetVnetParameter: vmnet config not found: VMnet16\NAT
2021-07-27T11:24:08.614-04:00| inst-build-16894299| I2: VNLRegistryGetVnetUseNAT: got result 0 and value 0
2021-07-27T11:24:08.614-04:00| inst-build-16894299| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-07-27T11:24:08.614-04:00| inst-build-16894299| I2: GetVnetParameter: vmnet: 'VMnet16' '' 'DisplayName'
2021-07-27T11:24:08.614-04:00| inst-build-16894299| I2: GetVnetParameter: type of 'DisplayName': 0x00000001
2021-07-27T11:24:08.614-04:00| inst-build-16894299| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-07-27T11:24:08.615-04:00| inst-build-16894299| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-07-27T11:24:08.615-04:00| inst-build-16894299| E2: VNLStartupCOM: security specification failed since already set (ignoring)
2021-07-27T11:24:08.615-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: finished with COM initialization (attempt)
2021-07-27T11:24:08.615-04:00| inst-build-16894299| I2: WMI_ConnectToWMI: Connecting to WMI server
2021-07-27T11:24:08.616-04:00| inst-build-16894299| I2: WMI_ConnectToWMI: Connected to WMI server
2021-07-27T11:24:08.616-04:00| inst-build-16894299| I2: AdjustSecurity: security query success
2021-07-27T11:24:08.617-04:00| inst-build-16894299| I2: AdjustSecurity: authn 0x0000000a authz 0x00000000
2021-07-27T11:24:08.617-04:00| inst-build-16894299| I2: AdjustSecurity: servername NT AUTHORITY\SYSTEM
2021-07-27T11:24:08.617-04:00| inst-build-16894299| I2: AdjustSecurity: authLev 0x00000006 imp 0x00000002
2021-07-27T11:24:08.617-04:00| inst-build-16894299| I2: AdjustSecurity: authInfo 0x00000000 capabilities 0x00000001
2021-07-27T11:24:08.641-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: next enumerator returned: 0x00000001
2021-07-27T11:24:08.641-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: Next() returned 16 items
2021-07-27T11:24:08.641-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.641-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.641-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.641-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.641-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.641-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.641-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.641-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.641-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.641-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.641-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.641-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.641-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.641-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.641-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.641-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.641-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.641-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.641-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.641-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.641-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.641-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.641-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.641-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.641-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.641-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.641-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.641-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.641-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.641-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.641-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.641-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.641-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: next enumerator returned: 0x00000001
2021-07-27T11:24:08.642-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: all network cards properly enumerated
2021-07-27T11:24:08.642-04:00| inst-build-16894299| I2: VNL_GetVnetAdapterStatus: searched for adapter 'VMnet17': installed=FALSE IP=FALSE IPX=FALSE
2021-07-27T11:24:08.642-04:00| inst-build-16894299| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-07-27T11:24:08.642-04:00| inst-build-16894299| E2: GetIPv4Key: address not found for 'VMnet17': IPSubnetAddress
2021-07-27T11:24:08.642-04:00| inst-build-16894299| I2: GetVnetParameter: vmnet: 'VMnet17' 'NAT' 'UseNAT'
2021-07-27T11:24:08.642-04:00| inst-build-16894299| E2: GetVnetParameter: vmnet config not found: VMnet17\NAT
2021-07-27T11:24:08.642-04:00| inst-build-16894299| I2: VNLRegistryGetVnetUseNAT: got result 0 and value 0
2021-07-27T11:24:08.642-04:00| inst-build-16894299| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-07-27T11:24:08.642-04:00| inst-build-16894299| I2: GetVnetParameter: vmnet: 'VMnet17' '' 'DisplayName'
2021-07-27T11:24:08.643-04:00| inst-build-16894299| I2: GetVnetParameter: type of 'DisplayName': 0x00000001
2021-07-27T11:24:08.643-04:00| inst-build-16894299| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-07-27T11:24:08.643-04:00| inst-build-16894299| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-07-27T11:24:08.643-04:00| inst-build-16894299| E2: VNLStartupCOM: security specification failed since already set (ignoring)
2021-07-27T11:24:08.643-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: finished with COM initialization (attempt)
2021-07-27T11:24:08.643-04:00| inst-build-16894299| I2: WMI_ConnectToWMI: Connecting to WMI server
2021-07-27T11:24:08.645-04:00| inst-build-16894299| I2: WMI_ConnectToWMI: Connected to WMI server
2021-07-27T11:24:08.645-04:00| inst-build-16894299| I2: AdjustSecurity: security query success
2021-07-27T11:24:08.645-04:00| inst-build-16894299| I2: AdjustSecurity: authn 0x0000000a authz 0x00000000
2021-07-27T11:24:08.645-04:00| inst-build-16894299| I2: AdjustSecurity: servername NT AUTHORITY\SYSTEM
2021-07-27T11:24:08.645-04:00| inst-build-16894299| I2: AdjustSecurity: authLev 0x00000006 imp 0x00000002
2021-07-27T11:24:08.645-04:00| inst-build-16894299| I2: AdjustSecurity: authInfo 0x00000000 capabilities 0x00000001
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: next enumerator returned: 0x00000001
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: Next() returned 16 items
2021-07-27T11:24:08.670-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.670-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.670-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.670-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.670-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.670-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.670-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.670-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.670-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.670-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.670-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.670-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.670-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.670-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.670-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.670-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: next enumerator returned: 0x00000001
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: all network cards properly enumerated
2021-07-27T11:24:08.670-04:00| inst-build-16894299| I2: VNL_GetVnetAdapterStatus: searched for adapter 'VMnet18': installed=FALSE IP=FALSE IPX=FALSE
2021-07-27T11:24:08.671-04:00| inst-build-16894299| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-07-27T11:24:08.671-04:00| inst-build-16894299| E2: GetIPv4Key: address not found for 'VMnet18': IPSubnetAddress
2021-07-27T11:24:08.671-04:00| inst-build-16894299| I2: GetVnetParameter: vmnet: 'VMnet18' 'NAT' 'UseNAT'
2021-07-27T11:24:08.671-04:00| inst-build-16894299| E2: GetVnetParameter: vmnet config not found: VMnet18\NAT
2021-07-27T11:24:08.671-04:00| inst-build-16894299| I2: VNLRegistryGetVnetUseNAT: got result 0 and value 0
2021-07-27T11:24:08.671-04:00| inst-build-16894299| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-07-27T11:24:08.671-04:00| inst-build-16894299| I2: GetVnetParameter: vmnet: 'VMnet18' '' 'DisplayName'
2021-07-27T11:24:08.671-04:00| inst-build-16894299| I2: GetVnetParameter: type of 'DisplayName': 0x00000001
2021-07-27T11:24:08.671-04:00| inst-build-16894299| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-07-27T11:24:08.671-04:00| inst-build-16894299| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-07-27T11:24:08.672-04:00| inst-build-16894299| E2: VNLStartupCOM: security specification failed since already set (ignoring)
2021-07-27T11:24:08.672-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: finished with COM initialization (attempt)
2021-07-27T11:24:08.672-04:00| inst-build-16894299| I2: WMI_ConnectToWMI: Connecting to WMI server
2021-07-27T11:24:08.673-04:00| inst-build-16894299| I2: WMI_ConnectToWMI: Connected to WMI server
2021-07-27T11:24:08.673-04:00| inst-build-16894299| I2: AdjustSecurity: security query success
2021-07-27T11:24:08.673-04:00| inst-build-16894299| I2: AdjustSecurity: authn 0x0000000a authz 0x00000000
2021-07-27T11:24:08.673-04:00| inst-build-16894299| I2: AdjustSecurity: servername NT AUTHORITY\SYSTEM
2021-07-27T11:24:08.673-04:00| inst-build-16894299| I2: AdjustSecurity: authLev 0x00000006 imp 0x00000002
2021-07-27T11:24:08.673-04:00| inst-build-16894299| I2: AdjustSecurity: authInfo 0x00000000 capabilities 0x00000001
2021-07-27T11:24:08.698-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: next enumerator returned: 0x00000001
2021-07-27T11:24:08.698-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: Next() returned 16 items
2021-07-27T11:24:08.698-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.698-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.698-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.698-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.698-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.698-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.698-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.698-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.698-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.698-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.698-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.698-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.698-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.698-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.698-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.698-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.698-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.698-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.698-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.698-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.698-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.698-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.698-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.698-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.698-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.698-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.698-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.698-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.698-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.698-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.698-04:00| inst-build-16894299| E2: ProcessSpecificHostAdapter: descriptions don't match at character 0
2021-07-27T11:24:08.698-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: at end of loop
2021-07-27T11:24:08.698-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: next enumerator returned: 0x00000001
2021-07-27T11:24:08.698-04:00| inst-build-16894299| I2: ProcessSpecificHostAdapter: all network cards properly enumerated
2021-07-27T11:24:08.699-04:00| inst-build-16894299| I2: VNL_GetVnetAdapterStatus: searched for adapter 'VMnet19': installed=FALSE IP=FALSE IPX=FALSE
2021-07-27T11:24:08.699-04:00| inst-build-16894299| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-07-27T11:24:08.699-04:00| inst-build-16894299| E2: GetIPv4Key: address not found for 'VMnet19': IPSubnetAddress
2021-07-27T11:24:08.699-04:00| inst-build-16894299| I2: GetVnetParameter: vmnet: 'VMnet19' 'NAT' 'UseNAT'
2021-07-27T11:24:08.699-04:00| inst-build-16894299| E2: GetVnetParameter: vmnet config not found: VMnet19\NAT
2021-07-27T11:24:08.699-04:00| inst-build-16894299| I2: VNLRegistryGetVnetUseNAT: got result 0 and value 0
2021-07-27T11:24:08.699-04:00| inst-build-16894299| I2: VNL_GetNumberOfVnets: number of vnets: 20
2021-07-27T11:24:08.699-04:00| inst-build-16894299| I2: GetVnetParameter: vmnet: 'VMnet19' '' 'DisplayName'
2021-07-27T11:24:08.700-04:00| inst-build-16894299| I2: GetVnetParameter: type of 'DisplayName': 0x00000001
2021-07-27T11:24:08.700-04:00| inst-build-16894299| I2: VNL_GetNumberOfVnets: number of vnets: 20

IT JUST GOES ON LIKE THAT FOR A WHILE. I will attach a zipped version but be warned, it is SUPER LONG. 

moderator edit by wila: Moved the log snippet in a spoiler

Labels (1)
0 Kudos
2 Solutions

Accepted Solutions
RaSystemlord
Expert
Expert

EDIT: To make the text a bit more detailed

I cannot give you a specific answer to this. But about the other of your links - discussion ended in Windows 11 related problem. I did verify that the Microsoft delivered Windows 11 worked just fine in VMware on that date. It is a DEV version and it seems to change many times a week. I later tried the new install from ISO-file and that worked very well, too, in VMware - however, this isn't really testing VMware, but it is more about if the suggested way to create a correct ISO-file works as it should be ... still talking about Windows 11 from strictly Microsoft sources.

I understand that your case NOW is not about Windows 11.

However, if Network adapters are failing to install, there are many generic reasons why an install in Windows fails. Typically, it is not related to an application, but to a certain Windows instance ... but we don't know for sure.

The generic reasons include:

- versioning. Not sure what the 16 version needs to be with that particular Windows 10 version. Needs to be checked or taken the latest one.

- Windows Feature Upgrades do break applications. This is a Day-One-Problem of Windows 10. Have you done a reinstall AFTER the feature upgrade or any update to make sure?

- Windows Install may be broken. Not sure how to fix that, however, log files or Event Viewer should indicate if the installer itself fails. As for fixing, I'm sure google and microsoft will tell you how. In my cases, the matter has been about an outdated Windows Update resulting in an outdated Install software.

- you have manually tried to correct the situation. See log-files AND Event Viewer to find out, why it failed.

- potentially, any other application can break Windows. This may be far-fetched in this case, but if you have another computer with a vanilla Windows 10, you might want to try it out, for testing, if it isn't useful. This would test at least that your VMware install .exe isn't corrupted.

- failing to install using Run As Administrator during install. Being an Administrator is NOT enough in some cases. (linked into registry matters)

- one way of how Windows gets broken, is to get wrong permissions in registry. No idea, how that might have happened, but that is a possibility, if some installation programs have not behaved correctly

- you may have some security software, which does more than you think. Some anti-virus software may have kind-of stealth fire-walling, which will block network related things. In corporate computers, this might come as a surprise to the user ... information may be shared as need to know -basis.

The above is in no particular order. Personally, I would check Event Viewer first to check for failures.

View solution in original post

scrublord
Contributor
Contributor

So looking around I noticed my normal network adapters behaving strangely. I did a "reset network settings", and it removed the drivers on the adapters - no problem, I backed them all up beforehand. What was weird, though, was that windows would not let me install or update the adapters because of "Code 56":

scrublord_0-1627496701974.png

At this point I concluded that there was something very wrong, so I went for a full system reset. After that, I reinstalled VMware, and it worked! The installation went smoothly, didn't hang or crash when installing the drivers, and when it was finished the virtual adapters it installed worked!

scrublord_1-1627496806514.png

So yes, RaSystemlord totally called it. It was definitely something snarled up besides the installer!

View solution in original post

0 Kudos
19 Replies
RaSystemlord
Expert
Expert

EDIT: To make the text a bit more detailed

I cannot give you a specific answer to this. But about the other of your links - discussion ended in Windows 11 related problem. I did verify that the Microsoft delivered Windows 11 worked just fine in VMware on that date. It is a DEV version and it seems to change many times a week. I later tried the new install from ISO-file and that worked very well, too, in VMware - however, this isn't really testing VMware, but it is more about if the suggested way to create a correct ISO-file works as it should be ... still talking about Windows 11 from strictly Microsoft sources.

I understand that your case NOW is not about Windows 11.

However, if Network adapters are failing to install, there are many generic reasons why an install in Windows fails. Typically, it is not related to an application, but to a certain Windows instance ... but we don't know for sure.

The generic reasons include:

- versioning. Not sure what the 16 version needs to be with that particular Windows 10 version. Needs to be checked or taken the latest one.

- Windows Feature Upgrades do break applications. This is a Day-One-Problem of Windows 10. Have you done a reinstall AFTER the feature upgrade or any update to make sure?

- Windows Install may be broken. Not sure how to fix that, however, log files or Event Viewer should indicate if the installer itself fails. As for fixing, I'm sure google and microsoft will tell you how. In my cases, the matter has been about an outdated Windows Update resulting in an outdated Install software.

- you have manually tried to correct the situation. See log-files AND Event Viewer to find out, why it failed.

- potentially, any other application can break Windows. This may be far-fetched in this case, but if you have another computer with a vanilla Windows 10, you might want to try it out, for testing, if it isn't useful. This would test at least that your VMware install .exe isn't corrupted.

- failing to install using Run As Administrator during install. Being an Administrator is NOT enough in some cases. (linked into registry matters)

- one way of how Windows gets broken, is to get wrong permissions in registry. No idea, how that might have happened, but that is a possibility, if some installation programs have not behaved correctly

- you may have some security software, which does more than you think. Some anti-virus software may have kind-of stealth fire-walling, which will block network related things. In corporate computers, this might come as a surprise to the user ... information may be shared as need to know -basis.

The above is in no particular order. Personally, I would check Event Viewer first to check for failures.

scrublord
Contributor
Contributor

Thanks, I shall go spelunking and see what I find. I agree that the application is probably not the issue.

0 Kudos
scrublord
Contributor
Contributor

So looking around I noticed my normal network adapters behaving strangely. I did a "reset network settings", and it removed the drivers on the adapters - no problem, I backed them all up beforehand. What was weird, though, was that windows would not let me install or update the adapters because of "Code 56":

scrublord_0-1627496701974.png

At this point I concluded that there was something very wrong, so I went for a full system reset. After that, I reinstalled VMware, and it worked! The installation went smoothly, didn't hang or crash when installing the drivers, and when it was finished the virtual adapters it installed worked!

scrublord_1-1627496806514.png

So yes, RaSystemlord totally called it. It was definitely something snarled up besides the installer!

0 Kudos
RaSystemlord
Expert
Expert

Great that you got it solved, although I couldn't give an exact solution 🙂 .

0 Kudos
stefy77
Contributor
Contributor

I have installed Vmware player 16 on windows 10 the networw controllers are not loading.
in the peripheral panel it says awaiting configuration

0 Kudos
RaSystemlord
Expert
Expert

@stefy77 

Please refer to my previous answer to this question. It is a rather comprehensive list of choices. Some of them are more likely than others in your particular case, but I cannot speculate on that.

0 Kudos
stefy77
Contributor
Contributor

I have installed the windows in a new hardisk from scratch and I have installed vmware so I have nothing to restore then in my case I do not even find the modules in the network settings the rest I have the same problem encountered.
The emulated machine is able to surf the internet but cannot share the address of my emulated mac and the windows

0 Kudos
RDPetruska
Leadership
Leadership

@stefy77 wrote:

I have installed the windows in a new hardisk from scratch and I have installed vmware so I have nothing to restore then in my case I do not even find the modules in the network settings the rest I have the same problem encountered.
The emulated machine is able to surf the internet but cannot share the address of my emulated mac and the windows


So, what exactly is your issue, if the virtual machine is able to connect to the internet/network?

Also, it is a violation of Apple's licensing to run their OS on non-Apple hardware.  We cannot help you with a virtualized macOS here, or VMware could get into legal trouble.

0 Kudos
stefy77
Contributor
Contributor

That I need to launch a server from the mac this creates an ip address which was then read by the windows. A few days ago I changed hardisk with the old system everything worked and vmware everything worked without errors.
With this error the mac navigates but if you share an ip address from the mac to windows it cannot read it.

0 Kudos
RaSystemlord
Expert
Expert

@stefy77 

If this "emulated mac" means running MAC OS on Windows, you got the answer above. You cannot get answers here.

If you have something else, can you explain:
- what computers you have on which OS

- where you have VMware?
- what VM virtual computers you have?

- what is the networking infra between physical computers and virtual computers?

- what are you trying to do, in terms of networking, between the physical/virtual computers?
- obviously, which tests, related to any networking, do work (and which don't)

0 Kudos
stefy77
Contributor
Contributor

From the mac I launch this command
java -jar B4iBuildServer.jar
is a server that communicates the b4i program in windows to the xcode program in mac the documentation is here
https://www.b4x.com/android/forum/threads/local-mac-builder-installation.46402/page-10#posts
The launched server creates two type ip addresses

Build server is ready

https://192.168.1.7:51042

http://192.168.1.7:51041

now this ip address with port 51042
It is inserted in the b4i program that is installed in windows and connects the windows with the b4i and xcode program that is on the mac.
Now with the old installation of the old Hardisk that did not give any installation errors while in the new one the windows did not sell the server
if I launch /192.168.1.7/test on mac it replies on windows no.
Ulteriori informazioni su questo testo di originePer avere ulteriori informazioni sulla traduzione è necessario il testo di origine
Invia commenti
Riquadri laterali

0 Kudos
stefy77
Contributor
Contributor

The Programs used are
Big Sur -> Mac
vmware 16
Windows 10 latest update

0 Kudos
RaSystemlord
Expert
Expert

@stefy77 

Based on your description, VMware isn't installed anywhere. So, why do you ask here? Probably you have something else, but what exactly?

See my questions above.

0 Kudos
stefy77
Contributor
Contributor

YES I HAVE INSTALLED VMWARE TO EMUALRE THE MAC bICSURE.
in the past I HAVE DONE EVERYTHING INSTALLATION AND IT HAS ALWAYS WORKED.
The difference is that installing the networ drives always went well.
In this case it fails to install them with information pending configuration

 

I am thinking that the network drives are not compatible with the latest windows update

 

I have the same problem as the photo posted in this post

 

 

0 Kudos
RaSystemlord
Expert
Expert

@stefy77 

Although your answer does not seem to be explicit, it seems that you are running Apple OS in Windows by using VMware.

As a Moderator already explained, you cannot get help here. EULA licensing policies are a matter of concern with responsible software companies.

0 Kudos
stefy77
Contributor
Contributor

I did not know this. My problem at the end concerns the installation of the vmware networ drivers of windows 10 that is not successful is there a manual procedure to install the drivers and solve the problem indicated above? in this page the solution was to restore the previous windows configuration but in my case the windows was installed from scratch and then I installed wmaware.
When it comes to the network drivers, the installation bar is waiting for the operation to fail and the drivers are installed with a warning awaiting configuration as you can see in the photos in this post.
Is there a solution to this problem?
I tried to uninstall vmware and repair the package without finding a solution

0 Kudos
RaSystemlord
Expert
Expert

@stefy77 

OK, with the matter of getting VMware networking to work in Windows 10 install. There was already a mention that you are able to access Internet from a VM - so networking works and is configured for Internet access, too.

As for getting errors in VMware install, this should not happen. I did provide a list of possibilities above. There were many items to check.

The solution above was a reinstall of VMware software. It is a very common problem with Windows 10 - it's, generally speaking, a Day 1 problem of Win 10 OS ... it does break applications, escpecially with Feature Upgrades. The solution is rather simple, a reinstall of the application. You say that you tried this, but did you try this AFTER any upgrade/update of Win10.

Also, are you using the very latest version VMware? If not, please do so.

I don't think there is a generic problem with Windows 10 & VMware, preventing a decent install. It must be specific to your system ... for those, please refer the list in my previous answer.

As for manual possibilities, at least with Workstation Pro, you ARE able to create Network Drivers & networks of your own choice. That can be done in GUI and is rather easy. To my knowledge, you can install Pro version, use it for 30 days and after that Network GUI stays operational for VMware Player use (which is also installed with Pro).

0 Kudos
stefy77
Contributor
Contributor

In my pc everything has always worked.
A few days ago I switched from a 128 gb hardisk to 1 Tb and I made windows setup after I installed vmware when I get home I give you the windows 10 version installed.
OK then I try to install the full version and see if I can fix it.
Thanks for help

0 Kudos
RaSystemlord
Expert
Expert

OK, Windows 10 versio as such doesn't mean much, because you can only slightly control it - it will Update & Upgrade when it wants to, in a semi-automatic way no matter what you do. I mean, if you use the very latest from VMware - all versions should be OK.

When you create manually Networks, you will hopefully get, at least, a more explicit error message if it doesn't work.

0 Kudos