This is a very aggressive bug I had to make a script to restart the service every minute. But then I replaced only the file vmnat.exe from the version 17.0.2 and now it is working fine

A very serious bug. I noticed it a week ago, when I updated to 17.5.0. Suddenly the vmnat.exe process started consuming 10% of the host cpu (no matter which guest I was running). After restarting the vmnat process (after a random time) the bug appeared again. The same solution worked for me: I replaced the vmnat.exe by the 17.0.0 version. Thanks!!!

PS: it's a very serious bug... it should be corrected !!!

I have what appears to be the same bug with a possible slight variation. In my case when the VMware NAT Service is in the high-cpu-usage state, my VMs that are configured to use NAT will not connect to the internet. Restarting the VM NAT service appears to restore network access. However, after a short while, the high CPU usage returns, brings both the VM and its host to a relative crawl. If I don't restart the VM NAT service, eventually internet connectivity for the VMs is lost until the VM NAT service is restarted again, 

I am having the same problem. My computer fan is constantly running now, even when VMWare Workstation is closed.

+1

Mine also continues to consume high CPU even after VMWare workstation is closed

Mine is the same. High CPU usage continues even after closing VMware Workstation Pro. The only way to stop it without restarting the computer is to restart the VMware NAT service.

Restarting the VMWare NAT Service did not solve the issue for me. I have to stop the service altogether. This means that VMs don't have network access, can't get OS updates, etc. which are often needed. Also, my company does not want to elevate privileges unnecessarily, nor allow us to do certain things on our host machines. That is why we have to use VMs! So we have to contact IT or request extra privileges to be able to stop the VMWare NAT Service.

Agreed. Restarting the NAT Service does not solve the high CPU usage issue. Rather, it suppresses it for a seemingly random amount of time, but it always returns.

same here. 17.5.0 build-22583795

I'm having the same issue as well. Where can I get that file?