10 workstation crashing

Similar Questions

• VMware workstation, crashes when I try to create a new virtual machine

  Hello

  I never had this problem before, but I didn't create a new virtual machine in a very long time. Last time I created one was making Workstation 9 I think. Some time after the upgrade to Workstation 10 or 8.1 of Windows Update 1 it has started.

  In 10 Workstation running on Windows 8.1, I select the file > new Virtual Machine dialog coming upwards and in a few seconds crashes of VMware workstation and closes.

  So I checked the Windows event logs and find

  Warning "VMware Workstation to function properly, must be reinstalled after the upgrade to Windows."

  So, I upgraded from 10.0.2 to 10.0.3 and it uninstalled and reinstalled but I still get this warning.

  Followed by an error

  ***

  Journal name:	Application
  Source:	Application error
  Date:	15/08/2014 23:33:53
  Event ID:	1000

  Task category: (100)

  Level:	Error
  Keywords:	Classic
  User:	N/A
  Computer:	P7Win8MC

  Description:

  Name of the failing application: vmware.exe, version: 10.0.3.48389, time stamp: 0x539a4fb0

  Name of the failed module: MSVCR90.dll, version: 9.0.30729.8387, time stamp: 0x51ea24a5

  Exception code: 0xc0000005

  Offset: 0x0003bece

  ID of the process failed: 0 x 1788

  Start time of application vulnerabilities: 0x01cfb902de541c11

  The failing application path: C:\Program Files (x 86) \VMware\VMware Workstation\vmware.exe

  Path of the failing module: C:\WINDOWS\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.8387_none_5094ca96bcb6b2bb\MSVCR90.dll

  Report ID: 24d5effb-24f6-11e4-bedd-20cf30780548

  ***

  So I need help to track down what I am not sure what VMware paper to look to maybe see what is happening.

  Thank you

  Rainey

  Well, I found the problem.

  I looked in the UNK file and found a few ISO files wrongs tracks.

  I had mounted some ISO in the past and they have made the entry in this file of preferences such as "isoLocationMRUx".

  I'd change the leter this ISO file player so they could not be found as input, once I corrected the paths I can now create a new virtual machine.

  He is responsible for ion BONE the new virtual machine now.

• How to troubleshoot Workstation Crash (vmui) - Access Violation?

  As of recently I get the following error (Windows Workstation 11.1.0,) when you start the user interface.

  ---------------------------

  VMware Workstation error

  ---------------------------

  Fatal error VMware Workstation: (vmui)

  Exception 0xc0000005 (access violation) occurred.

  A log file is available in "C:\Users\mgill\AppData\Local\Temp\vmware-mgill\vmware-ui-3224.log".

  You can request support.

  To collect the data to submit to the VMware support, choose "Collect load data" in the Help menu.

  You can also run the script 'vm-support' in the folder my computer directly.

  We will respond on the basis of your entitlement to support.

  ---------------------------

  Ok

  ---------------------------

  Nothing obvious in the newspapers. I repaired the installation. Uninstalled and reinstalled. Updated PowerCLI (who is also installed) and nothing don't change.

  Ironically, I discovered that if I don't know the error and just continue to work, everything seems to work properly. By the time I hit ok on the same windows if the user interface disappeared.

  Any help to remove this error is greatly appreciated.vm

  Here is the part of the log:

  2015 05-26 T 13: 43:01.969 + 02:00 | vmui | I120: cui::ComponentMgrCDS:RefreshComponentListWithDefaults: CDS_UNKNOWN_PRODUCT_ERROR for player-linux product

  2015 05-26 T 13: 43:01.969 + 02:00 | vmui | I120: CD: CdsUtil_QueryMsiByProductCode: {A53A11EA-0095-493F-86FA-A15E8A86A405} does not know in the MSI database.

  2015 05-26 T 13: 43:01.969 + 02:00 | vmui | I120: CD: CdsUtil_QueryMsiByProductCode: {313C6E9F-180C-46C3-8CB1-A2AFB34DF643} does not know in the MSI database.

  2015 05-26 T 13: 43:01.970 + 02:00 | vmui | E105: Error CDS: CdsUtil_QueryMsiPropertyByProductCode: MsiViewFetch failed: 259.

  2015 05-26 T 13: 43:01.971 + 02:00 | vmui | E105: Error CDS: CdsUtil_QueryMsiPropertyByProductCode: MsiViewFetch failed: 259.

  2015 05-26 T 13: 43:01.971 + 02:00 | vmui | E105: Error CDS: CdsUtil_QueryMsiPropertyByProductCode: MsiViewFetch failed: 259.

  2015 05-26 T 13: 43:01.972 + 02:00 | vmui | E105: Error CDS: CdsUtil_QueryMsiPropertyByProductCode: MsiViewFetch failed: 259.

  2015 05-26 T 13: 43:01.973 + 02:00 | vmui | E105: Error CDS: CdsUtil_QueryMsiPropertyByProductCode: MsiViewFetch failed: 259.

  2015 05-26 T 13: 43:01.973 + 02:00 | vmui | E105: Error CDS: CdsUtil_QueryMsiPropertyByProductCode: MsiViewFetch failed: 259.

  2015 05-26 T 13: 43:01.974 + 02:00 | vmui | I120: cui::ComponentMgrCDS:RefreshComponentListWithDefaults: CDS_UNKNOWN_PRODUCT_ERROR for product ws-linux

  2015 05-26 T 13: 43:01.974 + 02:00 | vmui | I120: CD: CdsUtil_QueryMsiByProductCode: {A3FF5CB2-FB35-4658-8751-9EDE1D65B3AA} does not know in the MSI database.

  2015 05-26 T 13: 43:01.974 + 02:00 | vmui | W110: cui::ComponentMgrCDS:RefreshComponentListWithDefaults: empty database installation! The substitution of installation state of windows-ws

  2015 05-26 T 13: 43:01.979 + 02:00 | vmui | I120: REGIONAL windows-1252-> user NULL = 809 system settings = 409

  2015 05-26 T 13: 43:02.220 + 02:00 | vthread-6 | I120: VTHREAD initialize identifier of the thread 'vthread-6' 6, host 10700

  2015 05-26 T 13: 43:02.262 + 02:00 | vmui | I120: VMMgr::OpenVM (cfgPath = C:\Virtual Machines\mgil-mint\mgil-mint.vmx)

  2015 05-26 T 13: 43:02.272 + 02:00 | vmui | I120: CVMUIApp::OpenTabInt: open

  2015 05-26 T 13: 43:02.273 + 02:00 | vmui | I120: BasicHttpOnSent: xmlStrcmp

  2015 05-26 T 13: 43:02.273 + 02:00 | vmui | W110: Unhandled Win32 SEH Exception

  2015 05-26 T 13: 43:02.273 + 02:00 | vmui | W110: - Win32 exception caught, exceptionCode 0xc0000005 (access violation).

  2015 05-26 T 13: 43:02.273 + 02:00 | vmui | W110: ExceptionAddress 0x5caf42aa eflags 0 x 00010282

  2015 05-26 T 13: 43:02.273 + 02:00 | vmui | W110: rwFlags 0 badAddr 0

  2015 05-26 T 13: 43:02.273 + 02:00 | vmui | W110: eax ebx 0 0 x 1 ecx 0x35f1d8

  2015 05-26 T 13: 43:02.273 + 02:00 | vmui | W110: edx 0xa70048 esi 0x35f1d8 edi 0x35f158

  2015 05-26 T 13: 43:02.273 + 02:00 | vmui | W110: eip 0x5caf42aa esp 0x35f0c0 ebp 0x35f14c

  2015 05-26 T 13: 43:02.273 + 02:00 | vmui | W110: The following data was delivered to the exception:

  2015 05-26 T 13: 43:02.273 + 02:00 | vmui | W110 :--0

  2015 05-26 T 13: 43:02.273 + 02:00 | vmui | W110 :--0

  He just disappeared!

  I uninstalled Visual Studio 2015 Preview. (Including .NET 4.5.3 preview and preview 2015 C++ Runtime).

  After that the error disappeared.

• 9 workstation crashes ugly on ASUS P8Z77 - V Pro based machine, Linux host

  I tried to solve this problem for the last five days does not. I posted a video of the accident, tests, newspapers and all the details here: http://www.kevindanenberg.com/vmware/

  Basically, seconds after I start a guest computer (any OS), the home screen turns off and restarts the host. This happens after a clean install of Ubuntu 12.04.1 64-bit on the host computer and several other flavors of Linux (see the link above for all the various events...) This happens with Workstation 9 as a player.

  It seems related to the material, because Ubuntu 12.04.1 64-bit works on a clean installation on an old machine very well.

  Material in question:

  ASUS P8Z77-V Pro

  Intel i7 - 3770S @ 3.10 GHz

  G.SKILL Ripjaws X Series 16 GB (4 x 4 GB) F3-12800CL9Q-16GBXL

  WD Black 1 TB (ATA WDC WD1002FAEX-0)

  I disassembled the machine as bare as possible test.

  I put in a request for support for VMWare and someone tries to help, but they did not understand anything or out again.

  Any ideas?

  I suspect that it is a bug in Workstation 9 about the SMEP on Ivy Bridge systems.  If so, it only affects the virtual machines by using the binary translation.  The bug should be fixed in version 9.0.1 workstation.  In the meantime, you should be able to work around the problem by asking specifically VT-x/EPT as the preferred mode - assuming that VT - x is enabled in the BIOS.

• VMware Workstation 11 crashes after installing VMware tools

  As the title suggests, VMware Workstation 11 crashes after installing VMware Tools with a guest Windows 7 x 64. I am running VMware on a host Windows 7 x 64. It happens every time I try to install the guest operating system. Attached to this post are all the newspapers that I could find that I thought would help solve the problem.

  
  

  Thank you

  Wila

  Hello again,

  Maybe the following post helps (where you installed Visual Studio)

  How to troubleshoot Workstation (vmui) - Access Violation Crash? How to troubleshoot Workstation Crash (vmui) - Access Violation? How to troubleshoot Workstation Crash (vmui) - Access Violation?

  --

  Wil

  As you may already know, VMware has just released a major update for 11 workstation (including VMware tools updated). Workstation now works almost perfectly. I don't have accidents since then. This means that I have was right in my post above. This is indeed nothing more than a BETA version of VMware buggy, lazy, masked as a "final". Wow, it looks like that a respectable company like this would not resort to such unethical practices. I mean that you would expect this kind of crap of a company like Electronic Arts, but VMware? Come on guys, you're better than this!

• Crash after upgrading to Workstation 10.0.6 - 2700073

  Upgrade to 10.0.6 - 2700073 this morning, and workstation crashes as soon as I start it.

  The details are in the attached ZIP file:

  -capture of screen crash

  -captures of three log entries of applications to screen the accident events

  -vminst.txt, which has been updated at the time of the accident

  The .xml file that is mentioned in one of the entries in the event log does not exist on my system.

  I'm running on a host Windows 8.1 and have been running earlier versions of workstation for more than a year on this PC.

  PC is a Lenovo Thinkpad T503

  I'm going to uninstall this version and try to reinstall the previous version.

  Someone at - it ideas about the cause of these problems?

  Had the same problem of crash after the upgrade and after some research I found this post which gives a few details why the crash occurs.

  To solve the problem simply do the following:

  Find the file libcurl.dll in your VMware Workstation installation folder.

  (I found 3 cases on my machine windows 8.1)

  C:\Program Files (x 86) \VMware\VMware Workstation\x64

  C:\Program Files (x 86) | VMware\VMware workstation

  C:\Program Files (x 86) \VMware\VMware Workstation\OVFTool

  Make a copy of the files in the first 2 files with a modified date of 04/28/2015

  Replace with a copy of the file in the 3rd record (\OVFTool) before the date last updated on 02/04/2015

  Start VMware Workstation

  This fixed the issue and no uninstall or reinstall required, I tested and did not have any issue.

  I take no credit for this that the problem was discovered in the post below, which has more details on the exact cause.

  http://blog.rewolf.pl/blog/?p=1167

• Workstation 9: crash when the USB peripheral attachment VM remotely

  Dear experts, is there a workaround?

  I'm trying to attach a USB flash drive to a Linux VM on ESXi server.

  The workstation crashes with the message:

  

  Workstation version 9.0.2 develop 1031769, Host Win7 SP1 x 64.

  Otherwise, Wks works fine with virtual machines the and remote. I can connect the same device to a local virtual computer.

  Here is the relevant excerpt from the newspaper.

  Thanks in advance for any ideas.

  -Pavel

  2014-01-22T20:26:59.303+02:00| vmui| I120: REM-USB: Opening device 0x807815567
  2014-01-22T20:26:59.772+02:00| vmui| I120: REMDEV:RemoteDeviceConnected USB reconnecting:0
  2014-01-22T20:26:59.772+02:00| vmui| I120: REM-USB: Connecting device 0x807815567
  2014-01-22T20:26:59.772+02:00| vmui| I120: USBGW: Write arbitrator op:8 len:8
  2014-01-22T20:26:59.772+02:00| vmui| I120: USB Hint: A USB device is about to be unplugged from the host and connected to this virtual machine. It will first be stopped to enable safe removal. With some devices, the host may display the message "The device can now safely be removed."
  2014-01-22T20:26:59.772+02:00| vmui| I120: 
  2014-01-22T20:26:59.772+02:00| vmui| I120: USBGW: Write arbitrator op:6 len:105
  2014-01-22T20:27:00.188+02:00| vmui| I120: USBGW: Write arbitrator op:8 len:8
  2014-01-22T20:27:00.188+02:00| vmui| I120: USBGW: Write arbitrator op:8 len:8
  2014-01-22T20:27:00.188+02:00| vmui| I120: USBGW: Write arbitrator op:8 len:8
  2014-01-22T20:27:00.188+02:00| vmui| I120: USBGW: Write arbitrator op:8 len:8
  2014-01-22T20:27:00.188+02:00| vmui| I120: USBGW: Write arbitrator op:8 len:8
  2014-01-22T20:27:00.188+02:00| vmui| I120: USBGA: device 807815567 arrived
  2014-01-22T20:27:00.188+02:00| vmui| I120: USBGW: Write arbitrator op:10 len:8
  2014-01-22T20:27:00.418+02:00| vmui| W110: Unhandled Win32 SEH exception
  2014-01-22T20:27:00.418+02:00| vmui| W110: ----Win32 exception detected, exceptionCode 0xc0000005 (access violation)----
  2014-01-22T20:27:00.418+02:00| vmui| W110: ExceptionAddress 0x6debddeb eflags 0x00010202
  2014-01-22T20:27:00.418+02:00| vmui| W110: rwFlags 0 badAddr 0
  2014-01-22T20:27:00.418+02:00| vmui| W110: eax 0 ebx 0x441df84 ecx 0x7731e38c
  2014-01-22T20:27:00.418+02:00| vmui| W110: edx 0xcb0048 esi 0x79d0d40 edi 0x1
  2014-01-22T20:27:00.418+02:00| vmui| W110: eip 0x6debddeb esp 0x1ce58c ebp 0x1ce5a4
  2014-01-22T20:27:00.418+02:00| vmui| W110: The following data was delivered with the exception:
  2014-01-22T20:27:00.418+02:00| vmui| W110:  -- 0
  2014-01-22T20:27:00.418+02:00| vmui| W110:  -- 0
  
  

  Update: this seems to be fixed in v 9.0.3.

  -pa

• HELP me please, could not return to vm and crash of vmware workstation 7

  Help!

  I'm in deep problem with a virtual machine that does not work either... I'm disparate because I can't go to a previous snapshot.

  I have a machine t1500 dell with core i870, 16 GB of ram, nvidia quadro fx 512 mb graphics card, 500 gb hd, windows 7 pro 64-bit.

  In this machine wmware workstation 7 (latest version) is installed with autoprotect runs up to 10 daily snapshot.

  About 40 days, I converted two computers in vm... one with 32-bit vista and one with 32-bit xp.

  Every month the recent, everything works well... but yesterday all the vm was crushed because the space in my hd was full... so since the Snapshot Manager, I deleted some old snapshot.

  During the removal of a few shots, sometimes it shows me that he can't remove because the disc is always busy... but, but icon in the timeline of the Snapshot Manager went... go in the folder where I saved the files in vm, also failed in the Recycle Bin of windows.

  Once deleted, I try to turn it on again the vista 32 bit vm... aaaaahhhhhh, it does not start! and it remains pending mode... why!... If I try to take it back, all wmware workstation crash and I can only see a windows message error that vmware workstation has stopped working.

  Then I try to run the virtual machine with 32-bit xp and it work without any problem.

  Then I opened again snapshot manager and I try to use the function "go to...". "to recover a snapshot... ahhhhhh! nothing to do! It crash again!

  so I tried also to remove some files as described in this Ko... but not at all, it crash again!

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1003846

  HELP ME, PLEASE! I have all my projects in this machine is very important... If I lose the...

  OK, so it looks like us (you) lost snapshot sw2 - 000010.vmdk, which was created between March 1 and March 2.

  What we need to do now is to repair the broken chain instant (because of the missing original sw2 - 000010.vmdk) and create a clone of this disc. Snapshots 000043 and 000044 contain no data and can be ignored.

  What we need to do is:

  1.) to repair the chain instant (link sw2 - 000009.vmdk to sw2 - 000006.vmdk)

  • SW2 - 000009.vmdk backup since we need to modify this file
  • Copy the sw2 - 000009.txt attached to the virtual machine file
  • Copy dsfi.exe to the virtual computers folder
  • run: 'sw2 - 000009.vmdk' dsfi.exe 512 800 'sw2 - 000009.txt.

  2.) creating a clone

  • find a drive with enough free space on the drive on which the clone will be created!
  • run: "C:\Program Files (x 86) \VMware\VMware Workstation\vmware - vdiskmanager.exe «r - t 0 \sw2clone.vmdk C:\vm\sw2\sw2-000042.vmdk»»
  • Create a new virtual machine and attach the vmdk cloned (using existing disk) instead of creating a new disc
  • Before you start the virtual machine, create a snapshot where the clone has some corrupted data and you must go back to for example to fix this virtual disk to a helper VM or open it with the disk mounter utility.
  • run the chkdsk command to check that the disc is ok

  André

• using the VMware workstation 100% disc

  Hi all

  I have amd multi-purpose 8350 with 12 GB of ram and 1 TB hard drive (no ssd). I created a few 10 vms and when I try to start few of them suddenly disk use increases to 100%. I turn them all at the same time, I give some time between each vm poweron. Always the same problem occurs. In addition, even after some time, after activating my vms, same problem occurs. on my windows host computer, the use of the disc is 100% most of the time. because of this my vmware workstation crashes and I am not able to do anything. I have to wait until the use of the disc is free again. I disabled windows search on my host machine, but no luck.

  I added the lines on all my machines virtual vmx files but no use.

  
  

  MemTrimRate = '0 '.

  mainMem.useNamedFile = "FALSE".

  sched.mem.pshare.Enable = "FALSE".

  prefvmx.useRecommendedLockedMemSize = 'TRUE '.

  
  

  Can someone help me out here?

  
  

  Thank you

  Chaitanya.
  

  Hi Shawn,

  Thank you for your response...

  At start-up, if it's slow, it's fine. But it happens all of a sudden, even when I'm working. When it freezes, I can't do anything. Just count numbers to kill some time... I have to wait until he's back to normal and I donno when it happens.

  While I was looking on the internet, someone posted on an Internet site that disabling superfetch-bit, and windows update services can reduce disk performance. I'm 100% sure they are stopped on my windows host computer. So, I disabled the. But I was really surprised to see the performance of disk after I disabled the services. Now, I have a lag for a few seconds and that occurs only when I start the vms system. After that they are running no problem at all. I donno why a stopped service would cause such an impact. Subsequently, if I do not have a service, I turn it off, turn it off.

  Finally, after you turn off the 3 services, I have no problem.

  Thank you

  Chaitanya.

• Race of Workstation 7 32-bit

  VMWorkstation 7 supports the 64-bit version? I installed it on my windows 7 64 bit and it shows running 32-bit. The default installation is \Program Files (x 86)-version - 32-bit applications.

  In addition, it crashes during the creation of the virtual computer. Anyone with questions?

  Hello

  workstation is not really a full 64-bit software.

  The GUi is 32-bit, and the rest of the components are 64-bit. Workstation files then places on the x 86 directory are only from the GUI. It is ok

  Please, explain in more detail when and how workstation crashes on your computer.

  Don't forget to launch (and use) the workstations with a user with administration rights. Also check (if you have) the av perhaps plaguing workstation.

  Best wishes / Saludos.

  Pablo

  Please consider to assign all useful or correct answer. Thank you!! - Por favor considered premiar any respuesta correcta o util. ¡¡MUCHAS gracias!

  Virtually noob blog

• Lightroom 6.5 will not work after restoring the windows 10

  First of all, let me say that Adobe support for a pro user product sucks. Really? no other than this support?

  My windows 10 workstation crashed and did a restore. I understand that it is early and I had to reinstall the update 6.5.

  Problem is that Lightroom does not open because he repeats to me there is problem of catalog and will not allow last backup is only a few days to work.

  Then. How to solve this problem?

  The only thing that worked was completely reinstall Lightroom 6, and then apply the latest update.

  After that, I was able to use the last catalog had been saved.

  You guys seriously need better than this forum support if you want to think of yourself as a product for professional use.

  When all else fails reinstall, but this kind of support, it's not what you need.

  Capture One to become a better alternative if you have a serious problem.

• How to change the sha - 1 certificate in my new esxi host

  Hi guys...

  as my lab crashed this morning (my computer has a blue screen) and of all the vm in my workstation crashed.

  When I'm the my computer upward run again and pressed 'play' to start the esxi host, I received some strange error messages.

  I decided to install a new host esxi5.1, and when I have finished configuring the esxi host, I noticed that the SHA - 1 certificate is not the same as the one I have (I have the new esxi I installed, and the older and sha-1 are different between the two hosts).

  I added the vCENTER esxi host, and now I have 2 hosts esxi 5.1 with different certificates of sha - 1?

  I can continue to work in this situation?

  I built this laboratory to study the vcp 5.0 certification. (I also installed the 5.1 vsphere to manage guests)

  It's a way to modify the certificate to the other esxi I have?

  Hope to hear from you soon,

  Best regards

  Nahum

  Israel.

  Hi Nahum,

  Each host is supposed to have a different SSL certificate

  If you are looking to implement of the CA signed CERT for only ESXi hosts, this should help

  VMware KB: Configuration CA signed certificates for guests of ESXi 5.x

  or

  http://www.derekseaman.com/2013/02/VMware-vCenter-51-installation-part-15.html

  Blog of Derek has also to the replacement of all certificates of vSphere if you want to go this route

  Concerning

  one

• NAT crashed with 12.1.0 Pro workstation

  Yesterday I've upgrade to Workstation Pro 12.1.0 on my Linux host. I mainly run Windows virtual machines and connect to these via Remote Desktop. Virtual machines go NAT LAN and that's why I set up NAT port forwarding to the ports of Windows Remote Desktop. This Setup worked great for a few years.

  With 12.1.0 (from 12.0.1) update it's broken. The Windows prompt has network access (for example it can access SMB shares in the network) and everything seems fine, all the necessary processes (e.g. vmware natd(8)) are running, ' / usr/bin/vmware-networks - status says it all works. So I try to connect to the virtual from Windows via Remote Desktop machine (I'm on a Mac and use Desktop jump as a customer). BOOM. The connection failed and crashed vmware-natd(8). VMware-networks now says that the NAT service is not running.

  Today, I went down to 12.0.1. and the exact same configuration works without any problem.

  So I guess that something has changed in the NAT region. I'm missing some configuration options, or is there a bug in the new vmware natd(8)?

  I'm sorry that Workstation 12.1.0 have this bug.

  We have an internal bug to track this issue.

  Currently you please come back to use Workstation 12.0.1 instead?

  Thank you!

• 11 workstation reports (0xC0000005 Access Violation) Crash at startup but VMs works without any Apparent problem

  A new installation of the workstation 11 (11.1.0 build 2496824) on a new installation of Windows Server R2 Essentials 2012 crashes on start up (front of start/resume all VMs) with a message box indicating a fatal error of VMware Workstation (vmui) occurred and identifies the exception 0XC0000005 access violation).

  If I click OK in the message box, work station closes.  If I don't click on OK in the message box, I can always transfer the focus to the window workstation and workstation seems to behave normally (that is, I can start/resume / suspend virtual machines and virtual machines behave normally).

  I have attached the log file.

  Any thoughts on what is the cause?

  This problem is fixed in VMware Workstation 11.1.2.

• After the crash of the system, Workstation 10 reports "not enough physical memory is available" - how to fix?

  On a Windows Pro 8.1 with 32 GB memory main system, I was running three virtual machines on 10 workstation.  Then we had a power failure and the system crashed.  Once the power was back and I restarted, any attempt to run a virtual machine failed with the following (change numbers) message:

  Not enough physical memory is available to power on this virtual machine with its configured settings.

  To solve this problem, decrease the size of this virtual machine to 988 MB memory, increase the amount of physical memory for all the virtual machines to 1219 MB or adjust the parameters of extra memory to enable more virtual memory machine to swap.

  This occurs if the virtual computer, I try to start is one of those that was going or who was not working at the time of the accident.  In this case if I am as an administrator or not.

  I checked Edit/Preferences/memory, and reserved memory is set to 24480 MB - 24 GB.  Can I run a virtual machine if I set the memory size to below the value indicated in the message (in this case, 988 MB).  Of course, I don't want to run like that!

  The Windows System Control Panel reports (almost) complete 32 GB system memory. Task Manager indicates that only 7% of close to 32 GB is in use.  "About VMware Workstation", reports 32640 MB.

  How can I fix it?  I'm basically dead in the water.

  Bob

  You may encounter the same problem that others have reported in this other thread: Windows 8.1 October rollup KB2995388 and problem with 10 Workstation

  Try the workaround it and see if it helps.

  --

  Darius