GB10's Posts

Trying this on a new laptop running Win 10 64, the issue continues. I now know that ethernet0.connectionType = "hostonly" gets correctly set by the VmWs GUI and saved to the vmx, but during power on of the VM the vmx changes to contain  ethernet0.connectionType = "bridged" I attach the vmx's (renamed *.txt) and the log. Please help, as this is a showstopper to the network of VMs I need to run on workstation.

Thanks & will do, though it’ll be early next week before I can. File types were everything created by ESXi including vmdk, vmxf, vmsd, vmx, nvram, log. I appreciate some are surplus to requirements but didn't think any would cause this, but I may be wrong? VMs then appeared with no apparent issues by right-click on My Computer, then “Scan for VMs”.

Thanks for your questions. I have no VMs natively created by Workstation, yet. What would be a quick VM to create, to test the possibility the ESXi server source is the issue? Same issue for all 3 VMs downloaded from ESXi server. Downloads done via vSphere client using “download” of each VM’s folder from datastore, hence all VM files were copied to their own folder on Workstation host. VM guests are a Linux firewall, Windows Server 2016 and Windows 10 PC. VMware Tools were auto-updated on each VM, by Workstation. Workstation host OS is Windows 10 Pro 64bit. No plugins or scripts AFAIK, as this is a new Workstation install. VMs had no scripts on ESXi, AFAIK.

Thanks. Correct. Network setting changes made via the GUI, then seen to be correct in the vmx, which is then closed before running the VM. As the VM shuts down, the vmx changes and the GUI shows the Network has reverted to "Bridged". The same occurs despite downgrading Workstation to 16.1.2 and 15.5.7. The VMs were downloaded from ESX Servers running vSphere 5 Essentials. The VMs appear to run fine under Workstation, apart from this issue, preventing the network configuration I need.