VMWare Workstation 12 on Windows 10 with creators Update "Not enough physical memory is available"

[ObiTobi]

Hello,

on my 2 Machines running Windows 10 with creators update I have "Not enough physical memory is available". Both physical machines have 32GB RAM, VM with Windows 10 creators Update has 8 GB RAM. Task manager tell there are more then 18 GB free RAM.

Does anyone know this error and know what can I do?

Tobi

[Susie201110141]

Could you try to disable thinprint function and see whether this issue still exist?

Method:Menu->"Edit"->Preferences->Devices->Uncheck “Virtual Printer”

[ObiTobi]

I do not have virtual printing enabled.

[gimmely]

So, is it correct that you have two hosts, which are physical, in Windows 10 with 32GB memory on each and one guest of Windows 10 with 8GB memory on each as well?

Does the message of "(n)ot enough physical memory is available" show on the host(s) or guest?  What does the respective Task Manager show, in terms of which process/application is using most or extraordinarily high memory?

[ObiTobi]

Yes, my Laptop and Desktop are running Win 10 Creators Update and both have 32GB RAM.

And yes I have 1 VM Win 10 Creators Update 8 GB RAM on Laptop and 1 VM Win 10 Creators Update 8GB RAM on my Desktop.

The error message shows on hosts. Task manager on Host-Systems tell "nothing", there is no any application that will use more than 4 GB RAM.

I think its a compatibility error between Workstation and Creators Update. I found another thread here with same issue by different people.

https://communities.vmware.com/thread/560861

[wila]

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

[ObiTobi]

I'm sorry but where I wrote I receive the message at boot time? Maybe I'm wrong but I understand it, there was a 1 User that wrote after disabling virtual printing the error was done.

Sometimes can the VM run 5 Minutes, another time 2 hours before the error is occurred

I see the same error message as the user posted his screenshot "slewantoski2005     08.04.2017 02:50  (als Antwort auf: dariusd)" (Page 1, msg 10)

I can't post new screenshot because I need the next time the VM's and I'm temporary switched to Hyper-V.

Tobi

[wila]

Hi Tobi,

That's an OOM error.

The most likely fix is disabling thinprint though.

You mentioned "I don't use it", but it is about having it disabled as by default "you're using it" even if you don't actually use it.

If that doesn't help, then you might want to take it a step further and disable the .dll like somebody down in that thread did as well.

Now it might of course be the case that something else also causes this issue, unique to your machine.

My best guess however still is that it is thinprint biting you.

--

Wil

[ObiTobi]

Hi,

virtual printing is really disabled (see screenshot). No any VM has Printer Device and its not activated at preferences.

Do you mean this DLL "TPCInRDP.dll" to rename?

Tobi