Post 17.0.2 to 17.5 upgrade results in no networking (NAT) for VMs

[jfrostjr]

I upgraded from 17.0.2 to 17.5 on my Windows 11 Pro 22H2  based device today.   After completing the upgrade I can no longer get my VMs to connect to the default NAT.  Multiple reboots of the host do not make a difference or upgrading VMWare Tools on the VMs (Windows 10 Enterprise 22H2))

[ERFulton]

This resolved the NAT issue(s) for my install too. No more high CPU on my ThinkPad x280 as well.
Thank you @Flawinne_F

[Dillman1d]

This is really discouraging. I am facing the same issue. NAT is no longer working. Cannot ping the NAT gateway. If I go bridged is partially works. My VMs are can acess the internet but I can only ping the gateway using IPV6. This really stinks.

[Dillman1d]

I agree. ALL 16 of my VMs are offline unless I go bridged. Even bridged, IPV4 is not working only IPV6. 

[chytons]

Try the workaround @Flawinne_F suggested

I have not had any other NAT related issues after trying that.