Partilhar via

Hotfix available to prevent Media Player 10 setup from breaking content protection in Media Center 2005

  • Artigo

I previously described a scenario where installing Media Player 10 on top of Update Rollup 2 for Media Center 2005 can cause errors playing back content that is protected by digital rights management (DRM). We are still working on a fix that will repair the DRM store on machines that are already in a bad state, but in the meantime there is an additional hotfix (KB910393) that just became available that will prevent Media Player 10 from allowing you to install and revert DRM files.

As described in the knowledge base article for this issue, this hotfix will not fix the Secure Storage Protection Error on systems that are experiencing the problem. However, this update will prevent the problem by stopping the Microsoft Windows Media Player 10 installation package from overwriting certain DRM files.

You can download that hotfix at this location, and it will also be offered as a critical update to Media Center systems that have Update Rollup 2 installed if you visit Windows Update.

Comments

  • Anonymous
    November 29, 2005
    ... DRM only punishes the legitimate customer and rewards the pirates.
  • Anonymous
    January 16, 2006
    Is there a fix for those of us who've got a broken setup?
  • Anonymous
    January 16, 2006
    Hi Adam - If you have installed Windows Media 10 after Update Rollup 2 and ended up with files reverted, you can re-install Update Rollup 2 from http://www.microsoft.com/downloads/details.aspx?FamilyId=E5DAF37E-E243-4410-BC51-81CF2B56FE6E&displaylang=en to resolve this issue.

  • Anonymous
    December 27, 2006
    The comment has been removed
  • Anonymous
    January 01, 2007
    Hi Desperate_user - This hotfix appears to be not allowing you to install because the file version of wmplayer.exe and/or wmploc.dll are newer than the ones in the hotfix package. There is a more recent hotfix for Windows Media digital rights management (DRM) that is available at http://support.microsoft.com/kb/913800/en-us.  It might help to install that hotfix instead of KB910393 to resolve this issue on your system.