Home
[Solved] Not enough physical memory is available to power on this virtual machine

[Solved] Not enough physical memory is available to power on this virtual machine

November 3, 2014 Virtualization 53 Comments

If you are using VMWare Workstation (or VMWare player) on Windows 8.1 and have just update Windows, specifically KB2995388, you may receive this error message when attempt to start a virtual machine.

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

VMWare’s team suggests a workaround to this issue by uninstall Windows 8.1 Update KB2995388 which is labeled as an optional update, reference: Workstation 10 issue with recent Microsoft Windows 8.1 Update
Uninstall Windows 8.1 Update KB2995388

However, some user doesn’t want to fix the issue by uninstall KB2995388 (including me). There are some workarounds to this issue. First workaround, suggested by users, is to run VMWare as Administrator.

  • Right-click on VMWare shortcut icon and select Properties.
  • Select Compatibility tab and check the box Run this program as Administrator.
    Run as Administrator

Another workaround that I have tested it myself and confirm that it’s work. Follow these steps below:

  • Open the config.ini file located at C:\Program Files (x86)\VMware\VMware Workstation (the path of VMWare’s application). If the file doesn’t exist, create a new one.
  • Add this line to the file: 
    vmmon.disableHostParameters = "TRUE"

    vmmon.disableHostParameters = "TRUE"

  • Copy the file to ‘%AppData%\VMWare’.
    For example, C:\Users\Linglom\AppData\Roaming\VMware (replace Linglom with your username).
  • Restart your computer and try to start a virtual machine.

Related Posts

53 Comments

  1. blah December 1, 2014

    hey man, Thanks worked for me!!

  2. mR.sHIT December 17, 2014

    Fuck you it not work to me ! lier just waster my time !

  3. VMUser December 20, 2014

    Buddy,
    It worked for me. Thanks!

  4. Nacho December 22, 2014

    !!!Mil Gracias!!!
    Gracias a gente como tú que solucionan problemas que los demás ni sabemos cómo arreglar..

    🙂

  5. Bero January 9, 2015

    Worked for me too! thanks man!

  6. MrDude January 15, 2015

    Awesome! Worked for me too! Back up and running!

  7. Eng.wgamal January 16, 2015

    hay frinds — the problem may be solved by opening the VMWARE as an Administrator

    right click –open — as administrator
    it works with me

  8. 2Dee January 16, 2015

    Simply running as administrator resolved the issue where adding the line to config.ini in VMPlayer did not for me. In Win8.1 start screen just RightClick your VMPlayer button and “Run as administrator”. Now I just have to remember to do that next time….

  9. Razvan January 16, 2015

    Great. Thanks a lot! It worked for me.

  10. HackedMyself January 20, 2015

    @2Dee

    RightClick -> Properties -> Compatibility -> Check ‘Run as Administrator’

    and you don’t have to remember! 🙂

  11. Dhama_SCCM January 20, 2015

    Thanks guys… I tried reinstalling VMWARE on my machine but did not worked.

    Finally below worked for me… 🙂 :).. Thanks

    RightClick -> Properties -> Compatibility -> Check ‘Run as Administrator’

    and you don’t have to remember! 🙂

  12. RDL January 26, 2015

    Thanks! Running as administrator worked for me

  13. mostafa February 3, 2015

    Thanks Man. Simple, easy, and it works.
    Keep it up, Great blog!

  14. Moby February 3, 2015

    Thanks, tried everything except the workarounds, and the first workaround with running as admin client did it for me 🙂 Oh happy day!

  15. Faz February 13, 2015

    Hey man , thankyou for this work around…

  16. a.hacker February 21, 2015

    thanx so much.it’s worked.

  17. rockskier February 25, 2015

    I hate Windows updates!
    The config.ini change worked second time round once I (a) spelled “Parameter” correctly and (b) copied the config.ini file to the c:\users\rockskier\AppData\Roaming\VMware folder. No need to run vmplayer as administrator.

  18. Telgee February 25, 2015

    Thanks a lot.. you really helped out hey

  19. Gautam Matkar February 26, 2015

    Awesome !!! Solution 2 worked

  20. Karen February 26, 2015

    Thanks, running as administrator worked for me.

  21. Kevin21 March 4, 2015

    The option “Run as administrator” worked for me.

  22. xiaobo March 6, 2015

    Awsome! it works: adding the config.ini file solved the problem for me.

  23. Ashok March 8, 2015

    Thanks it worked for me

  24. Fukku March 24, 2015

    I tried running it as administrator and it worked 😀 Thank you!

  25. Marcos April 17, 2015

    Great! It Worked!

    Thank you, bro!

    Aloha!

  26. manjunath April 22, 2015

    thanks it’s solved my problem

  27. RCG May 21, 2015

    Thanks for sharing. Solved my problem instantly!!

  28. Ashish May 23, 2015

    That was a real quick solution…cheers

  29. venkkat June 13, 2015

    i did not found config.ini can u help me in another way

  30. linglom June 14, 2015

    You can create a new text file with Notepad and save it as config.ini. Or you can download the file from the link below by right-click on the link and select ‘Save Link As’.
    http://www.linglom.com/downloads/VMWare/config.ini

  31. IOS Dev July 3, 2015

    Worked for me too 😀

  32. Tango July 7, 2015

    Thanks a lot. Simply running as administrator resolved the issue. VM workstation 9

  33. Kumar July 7, 2015

    Thanks a lot, working like a charm for me. config.ini. fixed the issue.

  34. Ram July 17, 2015

    Thanks bro its working

  35. shakir August 2, 2015

    thankx a lot have a good time ever

  36. shakir August 2, 2015

    thnxxxxxxxxxx lot always good time with u…………

  37. darwin August 5, 2015

    i tried both the workarounds. sadly, none worked 🙁

  38. Bob September 6, 2015

    Running as Administrator did not work, neither did removing KB2995388. Am just restarting to see if adding the config.ini file works.

  39. Bob September 6, 2015

    Adding the config.ini worked, many thanks.

  40. lore September 14, 2015

    Work. Thanks a lot. Great

  41. Ella Mousavi October 6, 2015

    It worked … thanks

  42. Darwin October 18, 2015

    For me it only worked when I run the program as Administrator

  43. Dragan October 21, 2015

    thanks it’s solved my problem

  44. jojo November 23, 2015

    Great.. config.ini soution works..

    Thanks…..

  45. locuxs February 13, 2016

    Thank you … the config.ini file worked for me as well

  46. Sanjay March 2, 2016

    Thank you, running as an Administrator solved the issue !!

  47. Siva K Venkadesan March 21, 2016

    The simple fix is, locate the vm instance in windows explorer and delete two directories suffixed with “.lck” and a file with “.vmem” extension.

  48. rajan verma May 28, 2016

    Thank you so much
    It’s working for me
    Thanks once again

  49. Mohammad Ahsan July 16, 2016

    I tried many ways found on different blogs but all in vain.
    Finally, yours tips worked.

    Thank you, very much.

  50. asfaq November 1, 2016

    Thanks man I worked for me too
    keep going

  51. Someone November 3, 2016

    Thanks, working.

  52. Aaron January 30, 2018

    Thank You! This issue was driving me nuts! I added the line to the config fle (which I had to create using notepad and saving as config.ini) and it worked on reboot!

  53. Nah July 11, 2018

    Merci pour ces solutions cq marché pour moi.Super blog

Leave a Reply