VMware Fusion 6: cannot start Windows 2000 VM that worked in VMware Fusion 4 Got this message when starting a Windows 2000 VM on VMware Fusion 6 on a Retina MacBook Pro with OS X Mavericks:


  This virtual machine's policies are too old to be run by this version of VMware Fusion.


Could only find this Danish question with no answers.

Fusion 6 is supposed to 


run any old virtual hardware version (this one is virtual hardware 7, I think it originates from VMware Workstation 6.5).
support Windows 2000
Anyone having the faintest idea how to start digging for a cause?


Edit: extra information about the settings, .vmx and .vmxf files.

Opening the settings for this VM gets the same message.

VMware Virtual Hardware version overview.

There are a few lines with the word policy in the .vmx file, but none in the .vmfx file. And there is a .vmpl file (which seems to have to do with the -now discontinued- VMware ACE that used to ship with older VMware versions including VMware 6.5).

These are the lines with policy in the .vmx file:

tools.upgrade.policy = "upgradeAtPowerCycle"

policy.vm.mvmtid = "52 3f 1e 13 9d 44 69 76-7c dd cc d1 67 a4 46 32"
policy.vm.managedVMTemplate = "FALSE"
policy.vm.managedVM = "FALSE"


Note:

This is not a VMware Fusion specific question, searching for "This virtual machine's policies are too old to be run by this version of VMware" (so without Fusion or Workstation) reveals some nice links including Starting a virtual machine in Workstation or Fusion fails with the error: This virtual machine's policies are too old to be run by this version of VMware (2034362) which also answers this question.
Open the virtual machine's configuration file .vmx using a text editor.
Remove the lines which starts with policy.vm.*:

policy.vm.mvmtid = "52 d6 6f f9 f3 36 0f 9f-31 da 9f f5 90 7b ce 76"
policy.vm.managedVMTemplate = "TRUE"
policy.vm.managedVM = "FALSE"

Save the file and close the text editor.
Restart the VM.




If you still encounter the error…


Rename/delete the file with the extension .vmpl
Restart the VM.


For further reading, check out this thread: VM's policies are too old to be run by this version