Windows 10 Creators update (v1703) broke pfSense running on VM
-
I am running pfSense 2.3.4 on vmware workstation 12 on Windows 10 x64. I have WAN, LAN and OPT1 (DMZ) networks.
Creators update (v1703) installed and pfSense stopped working. I did a clean install of 1703 and pfSense still did not work.
I removed vmware and installed pfSense on Hyper-V. But it didn't work either! Specifically, I could not reach the interfaces, probably bridged networking or virtual switches are broken. I tried both the default Microsoft ethernet drivers and the latest Intel NIC drivers.
Has anyone had problem or success with the VMs running on Windows 10 x64 v703? I am back to the Anniversary update.
-
I have some test VMs on my laptop which is running VMware workstation 12 with Windows 10 creator's update, no problems at all there.
AFAIK it won't let you have both VMware workstation and Hyper-V active on the same Windows installation though, did you bypass that restriction somehow? Or did you uninstall VMware before activating Hyper-V?
-
This is a know issue. After applying Creator's Update, your VMs will report a disconnected interface and you have no connectivity.
The solution is to go to Edit - Virtual Network Editor.
Click Change Settings at the bottom-right.
Click Restore Defaults in the bottom-left.
Done. -
I have some test VMs on my laptop which is running VMware workstation 12 with Windows 10 creator's update, no problems at all there.
AFAIK it won't let you have both VMware workstation and Hyper-V active on the same Windows installation though, did you bypass that restriction somehow? Or did you uninstall VMware before activating Hyper-V?
No, I had to uninstall the vmware first to test Hyper-V.
-
@KOM:
This is a know issue. After applying Creator's Update, your VMs will report a disconnected interface and you have no connectivity.
The solution is to go to Edit - Virtual Network Editor.
Click Change Settings at the bottom-right.
Click Restore Defaults in the bottom-left.
Done.Thank you, I read about that issue as well. What I don't understand is why Hyper-V had the same problem?
-
Thank you, I read about that issue as well. What I don't understand is why Hyper-V had the same problem?
It was most likely a completely different problem with similar symptoms.
-
I had a problem with bridged networks after that update. Checking vmware network config I found that there was no bridged network (settings removed). The solution is to reset the setting thus restoring the bridged connection. After that things worked fine again…lesson learned, don't trust MS
here is a link to an explanation as to why this happens...
https://chentiangemalc.wordpress.com/2015/07/09/windows-10-build-upgrades-break-vmware-workstation-network/
