VMWare Workstation "Not Enough Physical Memory..." Issue after Windows Updates on Windows 8.1



Yep... Another update and another bug. I just applied this months updates on my computer at home and guess what? It caused almost a "fatal" error on my VMWare Workstation virtual machines! As soon as my computer boots, I tried to fire one of my vms and I got the following scary message.


Now, of course, this didn't made any sense on a computer with plenty of RAM. So I knew right away that this wasn't a physical memory issue. After all, the vm was running for days just before the restart...

Time for a quick search regarding the message and BANG! VMWare is aware of the issue and they published a solution on their blogs.

http://blogs.vmware.com/workstation/2014/10/workstation-10-issue-recent-microsoft-windows-8-1-update.html

Basically, it's one of the Microsoft Updates causing this issue and the remedy for now is to uninstall this particular update from your computer...(dahh!)

KB2995388

But what exactly is this update all about? Well, you can find it here;

https://support.microsoft.com/kb/2995388

When I look at the things that this update is fixing & improving, to be honest, I really don't want to remove it from my computer :( But if you are dependent on your VMs like me, I have no choice but to remove it for now... Until one of these guys (vmware or/and microsoft) resolves the issue.

To remove the update from your computer, go to "Control Panel, Windows Update". On the left pane, click on "View update history". Find the KB2995388 update in the list and remove it. You need to restart your computer after the removal.



And... if your computer is configured to check for updates and install them by itself... It will probably installed automaticly again :) Hide this update next time so it won't get installed again.

What a sunday morning :)

Comments

Post a Comment

Popular posts from this blog

System.Messaging.MessageQueueException (0x80004005): A workgroup installation computer does not support the operation (Public Queue create issue)

This is a weird issue that I don't fully understand why it would happen. But the symptoms are very persistent as we're able to reproduce these behavior easily. Issue: The MSMQ (Microsoft Message Queuing) fails to create Public Queues and throws  "the System.Messaging.MessageQueueException (0x80004005): A workgroup installation computer does not support the operation" exception.
Read more

Veeam Backup Error : Failed to prepare guest for hot backup. Error: VSSControl

Image
Problem Description; I had this issue on one of my backup jobs recently and I was able to fix the issue with the solution explained below. After a quick google search, I realized that I'm not the only one and neither you are :) Full Error Description; Failed to prepare guest for hot backup. Error: VSSControl: Failed to prepare guest for freeze, wait tim eout 9 00 sec Error: VSSControl: Failed to prepare guest for freeze, wait timeout 900 sec
Read more

warning: Win32API is deprecated after Ruby 1.9.1; use fiddle directly instead - Chef Development Kit Update

Today, I needed to do some tests with a newer version of the Chef Client and test my cookbooks. To version 14.12.9-1 to be precise. I also upgraded my ChefDK on my workstation to the 4.2.0 version. I believe that upgrades Ruby version as well and now I have ruby version 2.6.3p62 Right after the upgrade, I tried with a basic knife node list command to see if I needed to reboot or anything was broke... Everything seems to be working fine, except I get this annoying "warning" message. As it's just a warning, I don't really care about it as it just seems to annonce something that is deprecated... Problem; You receive "warning: Win32API is deprecated after Ruby 1.9.1; use fiddle directly instead" warning when using ruby or chef knife commands. Solution; You need to comment out that warning message in Ruby lib scripts.
Read more