![]() Installing to AppData is not okay for every scenario or user. As the suggested workaround, while sound in theory, doesn't really work because of the weird hardcoded way your updater works, please award us the courtesy of being able to choose our install location. Doing so is considered bad form by most coders as well as administrators, and even, as someone said, could be considered malicious behavior as it attempts to circumvent user privileges. AppData is NOT meant for installing executables and shared data into. Spotify, PLEASE let us choose our install location (like it used to be - why did you "fix" this when it wasn't broken to begin with?) and don't try to force us to use AppData for reasons unknown. "Users" folder goes in AppData, the rest goes in ProgramFiles. Tried to solve it using symlinks instead, but then my Users folder also ends up being written to ProgramFiles which I do not want, obviously. Stupid design choice by Spotify, and while it's not quite as bat-poop insane as, say, Microsoft's choice to install Age of Empires Online (a game that measures in at ~10 GB or more) to your AppData folder (even though the latter installs in Local rather than Roaming), it's still just bad design. It will still be in your Program Files folder too, but every time you run it from there, it will want to update/restart and then it runs from your AppData folder again. Furthermore, when updating in this fashion, Spotify will set itself to autostart on login again, which should not be done once I've set it to disabled - an upgrade should respect this but does not. For Windows Desktop only (Microsoft store version is not suitable).Sorry, but doing so (moving the folder and fixing the shortcuts) will just write Spotify back to your AppData folder the next time it wants to update. ![]() Modified Spotify Client for Windows System requirements
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |