Tip: Fix the Missing Microsoft Store in Windows 10 Build 17110

Posted on March 1, 2018 by Paul Thurrott in Windows 10 with 17 Comments

Tip: Fix the Missing Microsoft Store in Windows 10 Build 17110

Windows Insiders on the Fast ring who installed build 17110 this week got a nasty—or welcome—surprise: The Microsoft Store app is missing.

Depending on your perspective, this is either a huge and obvious problem or a hopefully peek at what Windows 10 would be like today if Microsoft hadn’t gone down its disastrous mobile path. But either way, it’s just a bug in a pre-release version of Windows 10 and nothing to get too excited about.

Also, there’s a fix.

“We launched build 17110 and have received a quick influx of feedback regarding the Microsoft Store application not functioning as expected,” Microsoft’s Jason Howard writes in a Microsoft support forum post. “There are several experiences being reported, [including] pinned tiles missing on Start, [a] missing pin from taskbar, [the] application not showing in [the] ‘All Apps’ list [in] Start, [and the app being] missing from Settings > Apps & features.”

In other words, the Microsoft Store app is gone.

Howard says that Insiders should not try to reset the Store app because that will actually remove it permanently. But he does provide the following workaround, which is apparently not “official” but does appear to solve the problem:

  • Reboot the PC.
  • Open Powershell with Administrator permissions.
  • Paste in the following command:
    Get-AppXPackage WindowsStore -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}
  • Reboot the PC.

Voila! The Microsoft Store app should now appear and work normally. Obviously, this will be fixed in time for the next Insider build, which could happen as soon as the end of this week.

 

Tagged with

Join the discussion!

BECOME A THURROTT MEMBER:

Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Register
Comments (17)

17 responses to “Tip: Fix the Missing Microsoft Store in Windows 10 Build 17110”

  1. Redbreva

    No Store problem for me, just a GSOD most times I exit Edge, which is a pity as I seem to be one of only a small number of users who actually use/like Edge!!

    Ah well, back to Firefox till the next build...

  2. craigsn

    This fix is not working for me. As the AppXManifest.xml isn't found in any windows directory, only in my Visual Studio directory, and this fix doesn't even find that.

    • johnbaxter

      In reply to craigsn:

      On one of my machines, the manifest file was not found the first time I ran the command but there was no error the second time. And the store seems to have been fixed.


      On the other machine, the manifest file was not found in several tries but the store appears to have been fixed anyhow. I don't know what pieces of store might be missing (it is able to download things...I haven't tried to acquire anything new.


      And all three cases (the two above plus simple failure) appear in the comments to the forum post.

  3. SvenJ

    No store problem here. Icon and tiles are everywhere they should be.

  4. hrlngrv

    The double quotes in the Powershell command copy-paste as something other than ASCII double quote characters.


    FWIW, the Powershell command doesn't fix the Store app on my system. No great loss, though I have to wonder how that affects updating the Store version of desktop Office.

  5. jimchamplin

    I've paused updates and I'm sticking on 17107 until the next build.

  6. RonH

    I just did my update 17110.rs4_release.180223-1515.

    no issues.


    did they fix it?

  7. JeffFerguson

    Thanks, Paul. I wondered what that blank spot was on my Insider build's Taskbar. I'll give this fix a shot tonight.

  8. Tony Barrett

    I'd say it's a bit of a bonus that the store has gone awol. Maybe MS could roll that out to the release channel! ;-) Nobody's losing out much.

  9. derylmccarty

    I did have the "issue" (problem, no so much) but the correction using Power Shell worked the first time. I did not boot then Power Shell (admin) then restart, I just stopped the Edge article I was reading, went to PS, executed the command, then restart. Et Voila

Leave a Reply