The aforementioned workaround did indeed resolve my NAT issue, but only temporarily. This morning, it was back. I saw the other workaround mentioned was to save the prior version, but it's already gone on my machine. However, restarting the VMware NAT Service has given me (at least temporary) relief. Not sure how long it will last, but my guests have network back for now and I can probably make due until 17.5.1 comes out, which I hope is soon!
