Hi,
It might be the same issue, but that one is cured by disabling virtual printing as is described here:
Re: "Out of Memory" errors after Windows 10 Creators Update
Note that a "not enough physical memory is available" is usually a different error.
I agree that It sounds similar, there's a difference as for example the error you mention tends to happen at boot time of a VM while the OOM error as described in the other thread happens over time while the VM is running.
So it might help to actually capture the error or to attach a vmware.log file from one of the problematic virtual machines.
--
Wil