10-06 Crash after install: Faulting application / module name

[Maddieman]

This only happened once, on the first launch after installing it.

Faulting application name: DesktopScrobbler.exe, version: 1.0.0.0, time stamp: 0x59d74def
Faulting module name: wmp.dll, version: 12.0.7601.23517, time stamp: 0x57adfdef
Exception code: 0xc0000005
Fault offset: 0x0010e27e
Faulting process id: 0x410
Faulting application start time: 0x01d33e89e78c8c3b
Faulting application path: C:\Program Files (x86)\Last.fm\Last.fm Desktop Scrobbler\DesktopScrobbler.exe
Faulting module path: C:\Windows\system32\wmp.dll
Report Id: 2725e18b-aa7d-11e7-8a5e-0050b67a5fb2
====
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: DesktopScrobbler.exe
P2: 1.0.0.0
P3: 59d74def
P4: wmp.dll
P5: 12.0.7601.23517
P6: 57adfdef
P7: c0000005
P8: 0010e27e
P9: 
P10: 

[ben-xo]

@Maddieman can you attach the event from .NET which goes with this, as that has the actual stack trace

[VorTechS]

It seems like Windows Media Player crashed when the application tried to connect the component.

Does the same happen if you try to start Windows Media Player standalone?

If so, can you try the suggestions here:

https://answers.microsoft.com/en-us/windows/forum/apps_windows_10-winapps/windows-10-media-player-crashing/f220aae0-e764-4d14-887c-5aee582fe234

If not, close Windows Media Player and try running the app again.

[ben-xo]

So I'm getting this bug too; it crashes immediately when started from the installer, but works fine when started manually

[VorTechS]

I've added a 'hack' to the installer via a PostBuild action, which runs some Javascript to modify the MSI to enable the MSI 'Launch' feature. Give it a shot!