Once you uninstall the store version its not there anymore and once the desktop version that you install is migrated its removed from the original folder, so there is always only one version installed.
I’ve never been able to find that flag anywhere.
I wonder though, if blocking the migrator from running after the first install would be effective (as in also stopping it from running for future launches)…
I also just went to install this after upgrading my windows and I am now stuck on the store version too. Anything that I am able to do to assist you as well I will do. There hasn’t been any other equalizer I’ve used for the past 5 years but yours and now that it is gone my music sound muddy.
SpotifyMigrator.exe is the application that runs after an install of the desktop version (after its decided you are the lucky owner of a free “upgrade”)
The exe is placed in the folder for the desktop version on install, and its overwritten even if write protected. Installation also fails if you make the file permissions something that blocks the installer from modifying it…
previously i’ve focused on a general solution that does not involve extra apps or anything third party. But i might try making a tiny app today that can be run before installation of the desktop version that blocks/kills the migrator before it manages to do any damage.
My only problem is that its hard for me to replicate the issue on any of my machines/VMs.
I’m always able to just uninstall the store version and get the desktop version installed without hassle…
I was also able to uninstall the store version, remove ask the registry entries attached and install and older desktop version and your equalizer is working without issue. It says there is an updated version available, but not automatically updating which is nice.
I was trying to remove all of the registry entries for Spotify, and found a handfull of them that will not let you remove them. They all seemed to have to do with the MS Store… If I could get rid of those, then I think I could reinstall the original version of Spotify and be good…
Hi guys, I am also stuck having to run with the store version no matter what installer I run so I can’t use Equalify that I purchased today so very interested in this thread.
Didn’t help as still can’t move your dll’s into the crazy WindowsApps folder even though I own it.
I also pulled down an older version and see what you mean, it automatically updates to the windows store version, I watched the icon on the desktop change to the newer version before I could even click it.
Unless there’s a fix can I have a refund please as I can’t use the application sadly.
No matter what i do, i can not replicate the problem with the store version not going away after uninstalling it.
I’ve set up the latest windows 10 on several virtual machines and real hardware with various settings.
On every try the store version goes away just by uninstalling it, and i can then install the regular desktop version without any issues.
What version of windows do you have, what language is set, what region are you in? Anything else that can help?
Are you sure your windows version is 100% updated?
I will check my Windows version when I get home. The machine is an Asus Strix laptop which had a factory installed copy of W10 (updated of course). I also have another machine running a “upgrade” version of W10 (came from W7 to W10 through the free upgrade.).
For full dislosure, I am not an Equalify user (yet).
I tried the first method in the last link provided in the thread. It manages to stop Spotify launching automatically after the installation but even after deleting the migration file, it still runs it. Unsure how it does it but I tried a bunch of times and every one of them ended up with the migration happening.
I’ve also tried the registry edit option and I’m glad to report that it does work, however you get an error every single time you launch Spotify which also causes it to open 4 to 5 instances of the program, clogging up the machine and making it quite painful to use.
The error I get is the following:
I’ve tried to edit the registry once again to see the effects it would have and to get rid of the error, but I can’t find the modified key. If you would be so kind to let me know, I’ll update with the results I find.
As i assume you have read in the posts above, i’m having a very hard time replicating the problem, which in turn makes it very difficult to figure out a solution…
Any way you can record what is happening on your screen?
Or any way you could let me see whats happening real time (teamviewer or something similar).
If you uninstall all instances of spotify, store and normal.
Reboot your computer, and install again using the modified installer from the post above. Then open the Spotify folder and delete the SpotifyMigrator executable. there shouldnt be any way for a migrator to run…
That “restriction” message is expected, but if you delete the executable it shouldnt be able to run it and you shouldnt get the message…
Hey, no worries at all, you seem to be the main person trying to sort this out so getting back to you is the least I could do.
The migration executable file is indeed deleted and I’ve checked it does stay that way, with or without PC reboot, Spotify doesn’t download it again, which is the strange part because the error keeps popping up every time I launch the program.
What I have found, however, is that every time I launch the program, the Store app gets installed once again which seems like a plausible explanation for why the errors pops out again. For clarification, the version that opens is the non-Windows Store version, but the WS version does get installed every time I launch the program, so there might be something else that prompts for this.
(just say hi and i’ll put you in the right channel)
If not could you please uninstall spotify then open a powershell window with administrator rights and run this command: Get-AppxPackage -AllUsers *Spotify* | Remove-AppxPackage
Then try to install spotify again using my installer and see if that changes anything.
Don’t get the error on startup anymore, the program’s behavior is back to normal and updates through it run just fine. No sign of new installs of the WS version anymore either.
Many thanks for your help, seems like you’ve cracked the solution for me and hopefully for any others that stumble upon this thread!
Hi! I was having a similar issue. Be sure that you run the powershell command from an administrative account. It appears that when the microsoft store version is loaded on that account, it will always default to that on user accounts.