Forum Discussion

windracer's avatar
windracer
Brass Contributor
Apr 11, 2018

Windows Store apps can't download/run (1803 17133.73)

On the last two Insider Preview builds (17133.1 and now 17133.73) none of my Windows Store apps will run. This means I can't submit the bug via the Feedback Hub. When I check the downloads in the Windows Store app, everything is in an Error state. When I click "See details" the message is "Something unexpected happened" (code 0x80070005). If I try to click "Report this problem" it tries to open the Feedback Hub, which of course fails. 

 

So I'm stuck here. How can I fix this?

    • windracer's avatar
      windracer
      Brass Contributor

      Yeah, it's annoying because not only can I not submit bugs/feedback through the Feedback Hub, I can't use the calculator app. 

      • windracer's avatar
        windracer
        Brass Contributor

        This is really frustrating. I didn't realize how much I used the built-in calculator until it stopped working. 

         

        Here's what I see in the Store:

         

        apps failed to install

        Here's the Calculator app details:

         

        Store apps fail to download/install

        If I click on "See details":

         

        See details

        If I click on "Report this problem" it fails because the Feedback Hub won't launch:

         

        Can't "Report this problem"

         

        And again, I can't report this problem via the Feedback Hub since that doesn't work either. How can I fix this?

  • Mark McPherson's avatar
    Mark McPherson
    Copper Contributor
    Same here for my Surface Pro 3 whereas my desktop on the same Builds shows and runs the Store fine.
  • same here, there're a whole 7 apps those which failed to install in this update, including photos, camera, calculator, feedback hub along with the store app. 

  • mfmajor's avatar
    mfmajor
    Copper Contributor

    Hi, same problem here ... LOL ... i have windows defender firewall disabled and it was the problem, when enabled all works fine. This issue occurs in the new generation off windows server as well. Once again microsoft at its best... ;)

    windows 10 version 1803 build 17134.345

Resources