Two messages that sent people looking for a bug that was not there. No behaviour changed, no new files, no new permissions - if neither of these has bitten you, there is nothing here worth updating for.
Fixed
The Microsoft Store build of Spotify is recognised. It installs as a Windows package instead of into %APPDATA%\Spotify, so this app cannot work with it - and said so as "Spotify was not found", to people who were looking at Spotify while it played music. It now names the build and says what to install instead. Found because a volunteer reported the app as broken; it was not, but the message was.
The installer named the wrong certificate store. The wizard said "your personal certificate store". Personal is a different store that Windows really has - the CA goes into Trusted Root. Reworded to something a reader can act on.
--selftest also stops reporting "all mechanisms available" on a machine where Spotify is missing or the wrong build.
Installing
Download SpotifyAdsSkipper_Setup.exe below and run it. Windows will warn that the publisher is unknown - the installer is not code-signed - so choose More info -> Run anyway.
You need the Spotify desktop client from spotify.com. The Microsoft Store build cannot be used; if that is the one you have, this version tells you so on launch instead of claiming Spotify is missing.
Upgrading from 3.0.0 is just running the installer over the top. It closes the running copy first, and your certificate and settings are left alone.
New here? The 3.0.0 notes explain what the app installs, what the certificate is for, and what is worth knowing before you use it. All of it still applies.
Verifying the download
You do not need this to install the app. It is here in case you got the file from somewhere other than this page.
SHA-256 4622905A2A9FD9631E0C2E62E5593417077CDE3BA7293D73B37F6311CE5ACFE1
Get-FileHash .\SpotifyAdsSkipper_Setup.exe