Hardware changes require WMP re-individualization?

[valerria]

I used vCenter to convert a Win 2003 PC with a "working" IBX in WMP 10, but upon deploying as a VM it won't play any protected content, giving an unknown error. Fairuse4wm can still decrypt any content already played once, before the VM conversion.

When the VM first booted up it asked to reactivate Windows due to hardware changes, which I obliged, so I'm wondering whether this may have something to do with it.

It's a special case as the WMP 10 was upgraded from WMP 9. Neither 10 nor 11 can be installed on Win 2003 by default, and there's not even any uninstaller to remove it after upgrading from 9.

To complicate the situation the mobo on the physical machine just died, so depending on how hardware dependent the IBX is, I may or may not be screwed.

[Andy_ran]

I am in the same boat

I had a windows virtual machine I converted to VMware and now get the same thing

However. I still have with windows virtual machine and it's doing the same thing

After reading up its an error on the drm. You have to re individualise which then gives a new ibx and it all fails