Had no problems ever…firing up MSFS OR…downloading all the patches…until, they released this HOTFIX…for CTD, of which I did not suffer from . Now…as soon as I click on MSFS, it says, it can’t find my installation, and sends me to the download section of the MS Store. There…it hangs on DOWNLOAD and then comes back with a Code: 0x87E00017 error. Never had this trouble before.
What can I possibly do? This absolutely SUCKS!
Have you tried running it through the Xbox app?
I have the same problem. The update stopped and after this I was not able to start the simulator.
I have tried to reinstall everything, but the installation hangs in Windows Store and I get the error code: 0x87E00017.
I have noticed that Windows Store insists on installing the simulator to the c-drive even if I have configured storage for apps in Windows/System to use the D-drive.
The simulator was installed on the d-drive and was working fine before the “catastrophic update”.
Now, I am not able to fly 
I wonder if ZeroLlama262146 and me are the only the only users having problem with the late October update.
I have tried follow a lot of the suggestions I can find on this forum an on the net with no luck. Windows Store reset did not work, running the install trough the Xbox app did not solve the problem. I even tried to edit the Windows registry (I know about the danger doing this).
I bought the simulator in Windows Store with a Digital Ownership file.
When the installation start it always ask which drive to install, suggesting c-drive with not enough space.
I will then change it to my d-drive which has almost 6 TB of free space and then click install.
The installation downloads 10.06 MB and the install is paused.
Windows will now tell me that the Digital Ownership is installed.
Then I will try to continue the installation through Windows Store by click on the arrow to the right in the installation window. This is where the installation fails, and I get the Code: 0x87E00017.
I still think that there it has something to do with Windows Store not wanting to use my d-drive for the installation. Maybe the Digital Ownership file is installed on my d-drive and when I try to continue the installation, the simulator try to use my c-drive with not enough space and that is why it fails.
I do not know, and it look like I have to give up for the time being. Maybe Microsoft will have a fix in the future.
use the search function on that error code:
Mort, I had to fully re-install MSFS, but…I also have W10 downloads and apps asigned to the same drive it was on at RTM. Well, MSFS installed right back to my other-than-C: drive…and since then, I have had a pretty good run of it. So I wonder why your copy of W10 won’t send a re-install to the same drive you previously had your RTM install on…