Contributor
Contributor

Windows 8.1 October rollup KB2995388 and issue with Workstation 10

Just installed this update today, noticed after that I could no longer start any VMs with the error of "Not enough physical memory is available", even though 60gb were free and 47gb was allocated available to VMs.  Rebooted, same issue...uninstalled the patch and everything working fine again.

Anybody else running a 8.1 host install this yet?

75 Replies
Contributor
Contributor

I have the same issue - not enough physical memory after the latest (8.1) updates... Running on 16GB RAM, 14GB available on average...

0 Kudos
Leadership
Leadership

Thanks for reporting this.  We'll investigate ASAP.

--

Darius

Contributor
Contributor

Having the same problem since I installed the latest update. Thanks for looking into this.

0 Kudos
Contributor
Contributor

At least one workaround - uninstalling KB2995388 worked for me - VM's now run with no issues...

0 Kudos
Contributor
Contributor

I also have this issue after installing the October updates.

As a workaround:

Open the config.ini file located at C:\ProgramData\VMware\VMware Workstation.

Add this line:

vmmon.disableHostParameters = "TRUE"

Save & reboot your PC.

Contributor
Contributor

Looks like this has happened before when Windows 7 SP1 came out:  VMware KB: After installing Windows 7 SP1, VMware Workstation reports the error: Not enough physical...

0 Kudos
Contributor
Contributor

Yeah have the same issue...going to uninstall KB2995388 for now

0 Kudos
Leadership
Leadership

Yep, we need to make Workstation compatible with certain updates to the OS itself – almost every major OS update and occasionally minor updates too.

--

Darius

0 Kudos
Contributor
Contributor

Same issue here as well. After installed Oct 14 2014 MS patches I cannot power on any ov the virtual machines that i have. The host machine has plenty of memory and the hosted guest machine is running CentOS 6.5 with 1 GB of ram. Workstation is v 10.0.3 build-1895310

The attached file is the error message

0 Kudos
Contributor
Contributor

This workaround listed by works without any problem. Thanks

0 Kudos
Contributor
Contributor

Ended up with the same problem after installing KB2995388. I did the quick fix from Steve78 (in this thread) and it worked for me.

0 Kudos
Contributor
Contributor

Same issue with Workstation 9:

VMWare Workstation 9.0.4 build-1945795

Installed on:

Windows 8, 64-bit  (Build 9200) 6.2.9200

32752 MB

Just applied the October 2014 Windows Updates and after rebooting Workstation 9 did not/could not see most of the available memory (I think it thought there was less that a GB available when in fact only ~2GB of the 32GB installed were in use)

Temporary fix was to roll-back the system state to the restore point Windows Update made before applying the updates.

0 Kudos
Contributor
Contributor

I'm running the Technology Preview, and was getting "internal error" trying to launch VMs after yesterday's patches were installed. The config.ini change worked for me. (Note that you have to have to open the ini file as admin to modify it.)

0 Kudos
Contributor
Contributor

I am also facing this issue with Windows 8.1 x64.  None of my virtual machines power on saying not enough physical memory when I have 16gb.

0 Kudos
VMware Employee
VMware Employee

dariusd has provided the temporary workaround by uninstall the update, here is a blog post with detailed steps if anyone need a reference.

Workstation 10 issue with recent Microsoft Windows 8.1 Update | VMware Workstation Zealot - VMware B...

Contributor
Contributor

WinServer2012R2 + Wks10 the same error, after installation of October updates.

0 Kudos
Contributor
Contributor

Had the same issue, ran the installer, selected repair and was able to start VMs again.

0 Kudos
Contributor
Contributor

I did the same thing last night but still had the same issue.

Tonight I installed only the Windows Defender and dictionary updates and my VMs are working...weird!

0 Kudos
Contributor
Contributor

Running repair didn't work for me, neither did fully uninstalling and reinstalling, still not working.

0 Kudos