If you are still using MED-V v1, you may run into this issue when you are running the VM pre-requisites utility on the Windows XP image:
"Unhandled exception has occured in your application. If you click Continue, the application will ignore this error and attempt to continue. if you click Quit, the application will close immediately."
Details will show the following:
************** Exception Text **************System.Management.ManagementException: Critical error at System.Management.ThreadDispatch.Start() at System.Management.ManagementScope.Initialize() at System.Management.ManagementObject.Initialize(Boolean getObject) at System.Management.ManagementClass.GetInstances(EnumerationOptions options) at System.Management.ManagementClass.GetInstances() at Kidaro.VMPreparation.PreparationUtils.IsMasterDriveSCSI() at VMPreparationTool.VMPreparationToolActivator.Activate() at VMPreparationTool.VMPreparationToolForm.OnApplyClicked(Object sender, EventArgs e) at VMPreparationTool.VMPreparationToolControl.ApplyClickHandler(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at DevExpress.XtraEditors.BaseButton.OnClick(EventArgs e) at DevExpress.XtraEditors.BaseButton.OnMouseUp(MouseEventArgs e) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at DevExpress.XtraEditors.BaseControl.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
This is caused by a corrupt WMI repository.
You will also see the following in the event logs:
"WMI ADAP was unable to process the performance libraries: 0x80041001" and/or "WMI ADAP failed to connect to namespace \\.\root\cimv2 with the following error: 0x8004100a"
if this has happened, you will need to run the WMI Diagnosis utility for Windows XP to find out what may be wrong with the repository. You can download it here:
If necessary, you may need to rebuild the WMI repository although this should only be done as a last resort.
Click Start, Run and type the following command:
rundll32 wbemupgd, UpgradeRepository
This command is used to detect and repair a corrupted WMI Repository. The results are stored in the setup.log (%windir%\system32\wbem\logs\setup.log) file.