Spotify app makes system restore fail

Anonymous
2017-11-18T21:02:23+00:00

I think I'v installed the Spotify app from the Microsoft store three times over the last months, and every time I get the same effect: system restores are no longer possible:

So that's a reason for me not to use the app anymore, although for the rest, it works as a charm!

Anyone any idea why the Spotify app and System Restore are incompatible?

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

53 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-03-01T00:03:54+00:00

    i hear your pain and had to spend the time to do a full software restore and re-install of important apps (anything not that important I wouldn't bother with since I think this could happen again (it happened to me twice).  

    this guy Elmont said that if you can boot to a command prompt (I couldn't) you could try this.  I cannot say whether it works: 

    "

    I don't have an answer for the Spotify issue that as that is why I'm reading this forum but I do know whats going on with the bad update that screws up USB functionality. <br><br>Its a really easy process. <br><br>If you computer boots into windows open up a command prompt with administrator permissions. "cmd.exe" <br><br>once cmd is up type the following. <br><br>Dism /online /get-packages <br><br>Find the last rollup update that was installed. <br><br><image> <br><br>Once you have found the package name you need to remove it. <br><br>Type the following: <br><br>dism /online /remove-package /packname:[THE PACKAGE NAME HERE] <br><br>Replace [THE PACKAGE NAME HERE] with the rollupfix name that you find in your Dism search. - mine is highlighted in red above <br><br>so for my issue I typed this: dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.248.1.17 <br><br>after the package uninstalls you will be asked y/n to reboot.  <br><br>after rebooting your USBs will work again. <br><br>** you may have to do this for more than one rollup package. <br><br>Good Luck! "<br><br><br><br><br><br>you are 100% right about microsoft
    Post a reply <br> ---

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-03-01T01:28:04+00:00

    In reply toalanfishbein, unfortunately  removing the update package using this method may have worked BEFORE I tried the Restore process, but I am now caught up in an endless restart/fail/restart loop with no apparent way out of it.

    I will remember this for next time though as it seems with current quality control this is happening more and more frequently.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-03-02T18:12:17+00:00

    It is now March 2018 and still no workaround. I still have to this Issue

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-03-05T12:54:30+00:00

    The way I see it, %localappdata%\Microsoft\WindowsApps holds EXE shells for all Store apps which declare in their manifest that they want to be able to called from the command line. Consequently, I don't think Spotify is at fault but rather how Microsoft chose to implement this feature. In my case, apart from Spotify there are also executables for Unigram and Bash in that folder. Attempting to copy any of them into another folder returns exactly the same error code as is shown in the screenshot from the original post. Therefore, I'd say the issue is that System Restore has problems accessing those files just as e.g. Explorer and xcopy have, possibly due to wrong permissions, although the permissions window does not show anything out of the ordinary so this may not actually be that likely.

    Was this answer helpful?

    0 comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more