Bricked Spotify upon installation.

[SorenFloof]

Despite falling the installation guide step for step, the application refuses to launch and without an error message/dump to help figure out what went wrong. I've also noticed that the app launches after swapping back to the original dll.

Unsure what is going on or what I'm doing wrong.

[Mafiosee]

Same issue... App even not appears in task manager.

[FFGamer04]

See issue #663 . I tried and it didn't fix my spotify, but maybe it fixes yours?

[sleepyparsa]

Same issue here

[mrpond]

make sure you had something like this in the folder. follow step carefully and don't use any script

[virustack]

i do have that in the folder, yet spotify is still bricked

[FFGamer04]

Mine looks like this. I followed the instructions step by step, no scripts

[Mafiosee]

Here is dump, from %localappdata%\Spotify\User Data\Crashpad\reports

5f9c5932-9959-460d-b47b-26065dbd7f58.dmp

Here is call stack

[1n3JgKl9pQ6cUMrW]

I did not update yet (both Spotify and the patch), so I am still using version 1.2.79 with the old patch and update-block.

BUT I did try out the new patch some days ago (in an isolated test-environment). What I did see, was that you had to delete the old patch files dapi.dll also. Because the new Spotify will crash when both the new, and old patch are available.

Not sure this is the case for some of you, but be sure to 100% complete delete Spotify (the folder and it's content) first before updating Spotify and applying the new patch.

You won't lose anything, just need to re-login through the browser.

[1n3JgKl9pQ6cUMrW]

@mrpond

Maybe rename chrome_elf_bak.dll in a future update to chrome_elf_patch.dll or chrome_elf_required.dll since for many devs a 'bak` file is a deprecated file.

And in this case it's not deprecated but required for the patch to work.

Using another naming-convention, we can prevent human errors that will delete / ignore that file upon installation.

[SorenFloof]

I did not update yet (both Spotify and the patch), so I am still using version 1.2.79 with the old patch and update-block.

BUT I did try out the new patch some days ago (in an isolated test-environment). What I did see, was that you had to delete the old patch files dapi.dll also. Because the new Spotify will crash when both the new, and old patch are available.

Not sure this is the case for some of you, but be sure to 100% complete delete Spotify (the folder and it's content) first before updating Spotify and applying the new patch.

You won't lose anything, just need to re-login through the browser.

I attempted to do what you suggested with a complete fresh reinstall but the same case happened where the app just wont open at all. Quite a bummer. :(

[mrpond]

check the MT Lib in release. I fix it already

[mrpond]

@mrpond

Maybe rename chrome_elf_bak.dll in a future update to chrome_elf_patch.dll or chrome_elf_required.dll since for many devs a 'bak` file is a deprecated file.

And in this case it's not deprecated but required for the patch to work.

Using another naming-convention, we can prevent human errors that will delete / ignore that file upon installation.

yup, maybe It help. but I want to make sure people learn to read.
but I don't know why some PC won't work, I need to dig deeper if it not install issue.

[FFGamer04]

@mrpond thank you for your time. Unfortunantely the MT Lib solution did not work. The issue persists: If I install the patch and then run spotify, I get the spinning blue circle for a couple of seconds and then nothing. Not even a background spotify process in task manager. I am attaching the dmp file.

0c028581-8e54-4247-bff3-2a13def42163.dmp

[khatri90]

The issue seems to be resolved.