• July 17, 2017
    Announcement: New site design for Microsoft Community

    In July, Microsoft will roll out the first of ongoing site improvements aimed to modernize Microsoft Community and help customers get the most out of their community experience.

    • During the roll out period, you may see the old or new site design depending on your location

    • We expect the roll out to finish by 31 July

    Note: Past private message conversations will not move to the new site design. Please save any private messages you would like to keep.

     Learn more about the upcoming site improvements in this thread.

    Thank you for being part of Microsoft Community!


Windows Media Player Exception fails with code: 0xc0000005 file CompPkgSup.DLL

MartinO'Shea asked on


My copy of Windows Media Player has decided to fail whenever I try to use it. It gives message:

Investigating Event Viewer I find the following:

Faulting application name: wmplayer.exe, version: 12.0.14393.82, time stamp: 0x57a55d49
Faulting module name: CompPkgSup.DLL, version: 10.0.14393.953, time stamp: 0x58ba5c12
Exception code: 0xc0000005Fault offset: 0x000000000000349d
Faulting process ID: 0x2110Faulting application start time: 0x01d29daf15ffab4a
Faulting application path: C:\Program Files\Windows Media Player\wmplayer.exe
Faulting module path: C:\Windows\System32\CompPkgSup.DLL
Report ID: 75c8d5b9-2e77-474d-b774-e7069f11dfb6
Faulting package full name: 
Faulting package-relative application ID:

As far as I know this might have been caused by the Windows update dated 14 03 2017, following which I now have Windows 10 64 bit Pro Version 1607 Build 14393.953.

Any ideas?

Martin O'Shea.

125 people had this question

Abuse history

The answered status icon Answer
Red5goahead replied on

KB4015438 (on delivery)
Windows 10 Pro (Creators Update)
Mobile Lumia 950 (Anniversary Update)
Italy NW
12 people found this helpful

Abuse history

Most Helpful Reply
Family Cahill replied on

You are not alone. It looks like the update screwed up anything that uses the inbuilt DVD/MPEG2 decoder.

Options I've seen so far are to overwrite the DLL with old version or use LAV codecs. Trouble is that SFC could put the bad  DLL back again.






16 people found this helpful

Abuse history