Biggest disappointment Long file names don't work

altae said:

Once more jimbo45, bridged networking works. Please take a look at the output of ifconfig, executed in my virtual machine (Fedora 24) under VMWare Workstation 12 Pro. You can clearly see that an IP of my LAN pool has been assigned to the virtual machine by the router (network is 192.168.1.0/24). I've also attached a screenshot of the virtual network editor.

What software of VMWare (player or workstation) do you use? And what version? On my system the existing network configuration for VMWare Workstation also stopped working after the update. But restoring defaults fixed that issue.

Hi there
@altae

VMware workstation with Host restored back to 1511 which is working fine.



It doesn't work with the new Windows (Windows build 1607)

I've tried this on TWO totally different physical machines as well. Same result.

When you start the VM in the updated Windows you get vmnet0 not available - will start with vmnet0 disconnected so ifconfig won't be of any use.

NAT works OK but I NEED Bridged for various applications that the VM has to be accessible to from a variety of different Networks with different subnets,


Cheers
jimbo

That's exactly what happened on my host. But I fixed it like this:

1. In VMWare Workstation go to "Edit\Virtual Network Editor"
2. Click on the button "Change Settings" which requests admin rights in order to show all virtual network adapters.



3. Click on the button in the lower left corner "Restore Defaults".
4. Configure the virtual network adapters according to your needs.



I've set up VMNet0 (bridged) and VMNet 1 (host-only) and deleted the NAT adapter because I don't need that one. And now everything works as before the update. Give it a try, it should work for you too.

You cannot find it because it's not there. Simple isn't it

altae said:

That's exactly what happened on my host. But I fixed it like this:

1. In VMWare Workstation go to "Edit\Virtual Network Editor"
2. Click on the button "Change Settings" which requests admin rights in order to show all virtual network adapters.



3. Click on the button in the lower left corner "Restore Defaults".
4. Configure the virtual network adapters according to your needs.



I've set up VMNet0 (bridged) and VMNet 1 (host-only) and deleted the NAT adapter because I don't need that one. And now everything works as before the update. Give it a try, it should work for you too.

Hi there

Thanks -- I had a bit of time today for re-testing --that did the trick.

Cheers
jimbo

You're welcome :)

It is still there. Don't go into the NTFS folder, it is listed in the right hand pane, when "filesystem" is highlighted on the far left

The value has moved from NTFS directly into Local Computer Policy > Computer Configuration > Administrative Templates > System > Filesystem in the RTM version of the Version 1607.