Skip to main content

Could not open virtual machine – vmx is not a valid virtual machine configuration file

I recently faced an issue with one of my VMWare virtual machine that when I try to run this virtual machine it did not work. VMWare display this message that “Could not open virtual machine: .vmx. ".vmx" is not a valid virtual machine configuration file.”


Could not open virtual machine: G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx.

"G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx" is not a valid virtual machine configuration file.


I try to open .vmx file [G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx] in notepad then I found it was empty (0 KB).


I wanted to resolve it quickly so I try following method and it worked very well. But this is not a valid documented process so please try with caution. Following are the steps

1. First of all go to the folder where you have your virtual machine and delete all .lck folders.


Windows XP Professional.vmdk.lck
Windows XP Professional-000001.vmdk.lck
Windows XP Professional-000002.vmdk.lck

2. Open the .vmx file. In my case it was empty and 0KB.


3. Copy the content from any other .vmx file that you may have. This could be from a backup or from other virtual machine you may have. Let me know if you do not have any so I can send one to you.


4. Change following line in the file

scsi0:0.fileName = "Windows XP Professional-000001.vmdk"
displayName = "Apps - Windows XP Professional - QTP"
nvram = "Windows XP Professional.nvram"
extendedConfigFile = "Windows XP Professional.vmxf"

To get this value “scsi0:0.fileName = "Windows XP Professional-000001.vmdk"” you need to open Windows Explorer with detail view. Sort the folders & files by recent date and copy the name of the most recent .vmdk file.  See the picture below and you will notice that in my case it was "Windows XP Professional-000001.vmdk". Other values are self explanatory but if you have any question then post a comment & I will respond back with particular details.


Following line should also be changed but I could not find the correct value for it. So I left it like this.

ethernet0.generatedAddress = "00:0c:29:1d:4b:3f"

5. After you done editing, save & close the file.

6. Open VMWare and try to open the virtual machine. It it show you a message (I forgot to take screen shot of that message). The message will say something like this “Did you copy or move this virtual machine.” It will give you two options to chose from. 1. Copy & 2. Move. Select Copy option and Do not select move option. If you select move option then VMWare will not generate new SID & other keys.

7. That it. It should open your VMWare virtual machine and you should be good to go.   

Alternate Methods:

There are many other methods too that you can try to resolve this issue.

1. Create a new virtual machine & attach the existing .vmdk file: Create a new virtual machine with custom (advanced) configuration option and chose “I will install the operating system later”. Later in the new virtual machine wizard chose “Use an existing virtual disk”. This will allow you to browse and select your existing virtual disk. While browsing for file remember to sort the folders & files by recent date and then select the most recent .vmdk file.

2. Recover vmx from log file: Following pages describe this process. 

3. Recreate vmx file: Following pages describe this process.

VMware ESX – How to easily recreate a missing or corrupt VMX file - 

Understanding VMware VMX Configuration Files – Learn How To Create and Edit VMX Files


  1. I dont have the Ubuntu-10.10.vmx file can you please send it asap

  2. Thanks a lot for this resolution! Still valid and woking 100% (with vm workstation 11)
    (Lucky me to have a copy of the f***** up vmx file o0)

    I "produced" this issue while restoring a large sql-db in the vm. Unfortunatly my host-disk was nearly full, vm-workstation probably tried to expand the vm-disk consuming the very last byte of the host-disk, *boom*

    learning: always ensure to have at least the configured max capacity disk-size of the virtual disk free on host-disk... -.X

  3. Graciaaaaassss, me salvaste la tesis,
    No podia reparar la máquina virtual por nada, pero con esto funcionó perfectamente

  4. Thanks for sharing the post.. parents are worlds best person in each lives of individual..they need or must succeed to sustain needs of the family. best vpn

  5. I admit, I have not been on this web page in a long time... however it was another joy to see It is such an important topic and ignored by so many, even professionals. professionals. I thank you to help making people more aware of possible issues. China VPN

  6. There are a few things borrowers need to remember when they utilize CA, OR, NM, SC or AZ vehicle title advances to remake credit.

  7. Keep a precise record of charge exchanges. On the off chance that you utilize charge cards, keeping an exact record of your charges and returns is additionally crucial to the achievement of your income administration endeavors. Cash Advance

  8. It is very arduous to mention once precisely have to be compelled to money your check. generally it's going to terribly troublesome to money if it's not official hours.
    check cashing Hartford


Post a Comment

Popular posts from this blog

SharePoint WebPart Error - Unable to add selected web part (s) – MOSS 2007

ISSUE: Recently I faced this issue that when I try to deploy my WebPart.  Unable to add selected web part(s). WebPartName: Cannon unregister UpdatePanel with ID ‘ctl00RTMPanel’ since it was not registerd with the ScripManager. This might occure if the UpdatePanel was removed from the control tree and later added again, which is not supported. Parameter name: updatePanel.   I faced this issue twice and both the time the issue was not what display here. This could be sure to any error in the WebPart. Following are list resolution from multiple instances.   RESOLUTION: 1. Check the WebPartName.webpart file. Check whether you have a proper PublicKeyToken value. When I face the issue the value was PublicKeyToken=$PublicKeyToken$. If you have used WSP builder then in the Visual Studio you will find this file at \WebPartsProject\12\TEMPLATE\FEATURES\WebPartName\WebPartName.webpart. Sometime when you create a new WebPart using WSP builder then you do not get

Microsoft 2007 - Microsoft Technology That Defines a New Decade

Last year Microsoft came with VS.NET 2005, SQL Server 2005 etc. VS.NET 2005 was a major change over VS.NET 2003 in terms of feature, web controls and the way you program. Same is true for SQL Server 2005 you can now use C# or VB.NET to create store procedures and store procedures could be a .NET class. So no more missing of Oracle package in SQL Server. Be prepared for much more then this as Microsoft is now changing everything. Year 2007 Microsoft will bring a new Operating System named Vista (formerly code-named "Longhorn") First Look... that have completly new file system named WinFs and 1000s of new features. Vista will also come with WinFX which is set of next-generation managed APIs provided by Microsoft. Microsoft have created a new section in their MSDN website [ View ... ] so that people can start preparing for the next generation i.e. 2007. Here you can get information on Windows Presentation Foundation WPF (formerly code named "Avalon") provides the fo

How To Create Virtual Machine Using Existing vmdk file in VMWare Workstation

vmdk file is hard disk of the VMWare virtual machine. There are many scenarios where you may need to create a new virtual machine for an existing vmdk file. This is also an alternate Method to the “ vmx is not a valid virtual machine configuration file – Could not open virtual machine ” issue. Please refer to the previous post “ Could not open virtual machine – vmx is not a valid virtual machine configuration file ” for a full list of possible resolution. This post is to describe one of the solution in more details. How To Create a new virtual machine & attach the existing .vmdk file: 1. Open VMware and select create a new virtual machine with custom (advanced) configuration option. 2. Chose “I will install the operating system later”. and chose “I will install the operating system later”. 3. Select the operating system that matches the operating system in your existing .vldk file. 4. Select a location of the new virtual machine 5. Chose “Use an exis