Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BlockTheSpot not working anymore after system reinstall, same Spotify version. #513

Closed
8 tasks done
gettysburg opened this issue Jan 26, 2024 · 1 comment
Closed
8 tasks done

Comments

@gettysburg
Copy link

gettysburg commented Jan 26, 2024

  • You are using the Spotify last tested version mentioned in the README.
  • You are using the latest BlockTheSpot from github.
  • You uninstalled Spotify and just ran the patch
  • You read through the known issues section in the README.
  • You read through the additional notes section in the README.
  • You enabled logging by editing config.ini set log = 1.
  • Make sure whether an issue related yours is already open or not.
  • Make sure you have completed everything in the above checklist.

Hi,

on the 24th of January, BlockTheSpot was sometimes working for me, sometimes not - this is likely related to me accidentally installing the x32 version of the app.

Somehow, and I don't remember how, I eventually got it to work, probably by installing the x64 version.

However, now after a system reinstall, I can't seem to get it to work at all, with the old BTS version with x32 support, and the newest binary just supporting x64-compiled binaries.

There was no recent update that could have caused this, the binaries that I have on my PC were signed on Monday, January the 15th 2014.

What is actually going on, and could you take a look at the situation?

It just doesn't make any sense for me, BTS has worked for a few months now with numerous Spotify updates, and seems to work on the latest version, just not on my PC?

Windows Defender and all that crap is disabled.

Looking at the processes that Spotify spawns, it doesn't even load dpapi.dll anymore, with the patch, or without.

I am running Windows 11 Enterprise 23H2 with all updates installed.

I even tried injecting the DLL myself, to no avail, according to SystemInformer they do have some of the exploit protections that Windows allows developers to enable on, on the renderer process that also performs network activity:

DEP (permanent)
ASLR (high entropy, force relocate)
Win32k system calls disabled
Extension points disabled
CF Guard
Signatures restricted (Microsoft only) 
Non-system fonts disabled
Images restricted (remote images, low mandatory label images)
Child process creation disabled
SMT-thread branch target isolation

But even that process does not load dpapi, not the patched or original file.

Doesn't make any sense for me.

If anyone else encountered something similar, please leave a comment.

@gettysburg
Copy link
Author

gettysburg commented Jan 29, 2024

And after a few days, downloading the installer through the web player, now it works.. you have to download the right version, and there seem to be multiple x64 versions.

I uploaded the installer I used for you people:

SpotifySetup.zip

If you think this is a virus, right click on the executable, go to properties and you can see that it has a signature from Spotify.

@mrpond Can you maybe take that installer file and link to it on the main project page as a possible solution?

It is different from the other installers available online, at least according to the checksums.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant