Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
A new media server was not initialized because WMCreateDeviceRegistration() encountered error "<error code>". The Windows Media DRM components on your computer might be corrupted. Verify that protected files play correctly in Windows Media Player, and then restart the WMPNetworkSvc service.
|English: Request a translation of the event description in plain English.|
This started to appear in my Vista x64 event log after changing the CPU. Side effects visible elsewhere included inability of Windows Movie Maker to split Media Center recordings and crash of Windows Media Player 11 when playing Media Center recordings.
Error 0xC00D278F refers to NS_E_DRM_HARDWAREID_MISMATCH, which is described at “Windows Media Format 11 SDK Error Codes”. Judging from the description, this error would mean that any hardware change could provoke it. Even as innocent as CPU change or upgrade of graphics card (Google found at least one report of upgrade from NVIDIA 6800 to 8600 causing exactly the same symptoms). The solution is available in ME891664. In short, all files have to be removed from the folder "%SYSTEMDRIVE%\ProgramData\Microsoft\Windows\DRM". After that, you can re-individualize DRM system by going to “Security component upgrade“, and clicking on upgrade button.
Unfortunately, there is no simple and visible warning for less experienced users that their DRM files became unsynchronized with their hardware.
|Private comment: Subscribers only. See example of private comment|
|Links: ME891664, Windows Media Format 11 SDK Error Codes, Security component upgrade|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated