The cloning may have done it. Hardly ever can you successfully clone a XP installation into a different system, much less a VM. There's a whole range of things that may be forcing wmiprvse.exe on a wild loop.
Start your XP Client in safe mode. If wmiprvse.exe behaves this time, it's almost certainly a device. Check any devices like printers and faxes on your XP Client. Uninstall them while still in safe mode. Do the same for any network cards. Reboot in normal mode. wmiprvse.exe should behave now.
No? Confirm if this may be the problem: KB 925623
Still no? Enable WMI logging and restart the service:
- Alter the following registry values:
HKEY_LOCAL_MACHINE\Software\Microsoft\WBEM\CIMOM\Logging to 2.
HKEY_LOCAL_MACHINE\Software\Microsoft\WBEM\CIMOM\Logging File Max Size to 500000.
- Stop the WMI service with
winmgmt. If it fails, try
- Restart the service with
net start winmgmt, or reboot if it fails to start.
The log file located at
%windir%\system32\wbem\logs should give you an hint on what it is doing and what is probably going wrong. I however suspect you will get the problem fixed with just the second paragraph :)