Two additional important aspects to know:
- The indvpage and its outcome is not as powerful/crucial/significant as the individualization thru real commercial licensing servers of actual vendors, i.e. simply by trying to play a protected Windows Media file without prior visiting the indvpage(s) (either ALT1 or ALT or both). Commonly none of the users of real commercial DRM music services such as Rhapsody, Napster, Zune, MusicMe, Kazaa, etc. ever get in contact with the Microsoft indvpage(s) and even in the case of troubleshooting (if the DRM environment is broken) does the indvpage any real helpful service. The point is, the outcome of the indvpage may look positive (see contents of DRM-folder!) but the (commercial) DRM-environment may still be broken. This could be easily verified in the BBC iPlayer DRM protected Windows Media-thread. That thread comes to the conclusion that:
- It makes a decisive difference whether you're on truely fresh installation of WinXP-sp3 (=ships with WMP9) versus you're were on such a system, then did a standard upgrade to WMP11 (or WMP10) and finally did a rollback to the "original" state: a "fresh" installation of WinXP-sp3 (=with its shipped WMP9). I found out that Upgrading from the shipped WMP9 to WMP10 (or directly to WMP11) and rolling back to WMP9 is not a 100% reversible process, and it compares well to any RL act where you go from one stateA over to stateB and then back to stateA, e.g. the removing of dog poop from the bottom of your shoes:
clean 
shoes (= shipped WMP9) -> you step on dog poop (= upgrade installation procedure to WMP11) -> dirty shoes, i.e. clean shoes plus dog poop (= WMP11 installed) -> you clean the dog poop off your shoes (= uninstall/rollback process back to WMP9) -> clean 
shoes (= shipped WMP9).
No matter how hard you try to apply indvpage(s) or various ResetDRM.exe's or DRM_reset.exe's, the working of the
DRM ActiveX Network Object ..
.. can get (slightly) broken such that a "Sorry, an error has occurred." error message is returned. In this case, if you cant repair the working of the DRM ActiveX Network Object by the help (=overwriting of the corrupt registry entry!) of any other commercial license server, you must reinstall a fresh Windows from scratch (and please not again with WMP11 on top!, or do you have a registry backup? 
). The (broken) set of registry entries responsible for the malheur appears to be:
Code:
HKEY_USERS\S-1-5-21-1234567890-1234567890-123456789-1003\Software\Microsoft\Windows\CurrentVersion\Ext\Stats\{***}\iexplore\***
After a fresh Windows installation, keep a copy of the full Stats branch; it may be helpful at repairing broken DRM ActiveX Network Object components in future upgrade scenarios.
The above 2 observations should be true and valid in general, i.e. when your DRM-environment
appears to be a
working DRM-environment, i.e. ...
+ you have a clean installation of a WMP version (say WMP10 with its shipped WMFR10) and the versions of thefive and the drm-dll's look all fine (e.g. uniform)
+ you have fired off all kinds of exisiting 'Reset DRM'-tools
+ you have deleted the (remaining) contents of the DRM-folder
+ you have positive outcomes with the 2 indvpage(s)
+ you have even tried to restore an old WMP9 license backup
... and the online license acquisition from a
real commercial DRM license server
still fails with an "unknown error" message. As just mentioned, the reason for the failure is not the wrong or missing
files on your system ("you have the full shoes back!") but the gone corrupt
registry entry on your system ("the shoes still smell, yuck!!").
Note, "Unknown error"-messages can also result from wrong date/time of your PC clock. Therefore make sure that the clock (see system tray!) is keeping good time/the right time.
hope this helpz
