Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Whenever I open Windows Store, it's just stuck in an endless (my patience ended after 30 minutes) loading screen. Other apps, such as Skype, work fine. It's only Windows Store that doesn't work.

So far I've tried

  • Installing all available Windows updates & restarting
  • Starting Store from apps.windows.com and start menu
  • Running wsreset.exe
  • Running apps.diagcab (more on this below)
  • Re-registering Store
  • Running sfc /scannow (returns a very long CBS.log, and I'm not sure what I'm looking for there)
  • Running DISM

Windows Resource Protection found corrupt files but was unable to fix some of them.

apps.diagcab results

Windows Store Apps

My display drivers are the latest available and I'm only running Windows Defender as antivirus.

CBS.log

(from sfc)

https://i.3v.fi/CBS.log

DISM log

[1680] Caller did not request sparse mount
[1680] Mounting new image.
Wim:         [\\?\GLOBALROOT\device\harddisk0\partition2\Recovery\WindowsRE\Winre.wim]
Image Index: [1]
Mount Path:  [C:\WINDOWS\TEMP\b887443b-888f-4048-9cdd-02492983e700]
[1680] Wimserv process started for guid 0694d7d7-a638-4e34-bc87-f96a867c04f4.  Id is 392
[392] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition2\Recovery\WindowsRE\Winre.wim.
[392] Mounted image at C:\WINDOWS\TEMP\b887443b-888f-4048-9cdd-02492983e700.
[1680] [0x8007007b] FIOReadFileIntoBuffer:(1415): Tiedostonimen, hakemistonimen tai levynimen syntaksi ei kelpaa.
[1680] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
[1680] [0xc142011c] WIMGetMountedImageHandle:(2568)
[1680] [0x8007007b] FIOReadFileIntoBuffer:(1415): Tiedostonimen, hakemistonimen tai levynimen syntaksi ei kelpaa.
[1680] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
[1680] [0xc142011c] WIMGetMountedImageHandle:(2568)
[1680] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition2\Recovery\WindowsRE\Winre.wim.
[1680] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition2\Recovery\WindowsRE\Winre.wim.
[1680] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition2\Recovery\WindowsRE\Winre.wim.
[1680] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition2\Recovery\WindowsRE\Winre.wim.
[1680] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition2\Recovery\WindowsRE\Winre.wim.
[1680] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition2\Recovery\WindowsRE\Winre.wim.
[1680] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition2\Recovery\WindowsRE\Winre.wim.
[392] Received unmount request for image with guid 0694d7d7-a638-4e34-bc87-f96a867c04f4.
[392] Unmount for image at C:\WINDOWS\TEMP\b887443b-888f-4048-9cdd-02492983e700 complete.
-- snip large chunk of chinese letters --
[2176] [0x8007007b] FIOReadFileIntoBuffer:(1415): Tiedostonimen, hakemistonimen tai levynimen syntaksi ei kelpaa.
[2176] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
[2176] [0xc142011c] WIMGetMountedImageHandle:(2568)
-- snip large chunk of chinese letters --
share|improve this question
    
I would use DISM to repair your corrupted windows insallation. –  Ramhound Jun 12 at 11:09
    
@Ramhound tried it now, didn't help. –  3ventic Jun 12 at 12:06
    
Post the generated log for the action you performed. –  Ramhound Jun 12 at 12:08
    
@Ramhound posted the logs for both sfc and dism –  3ventic Jun 12 at 13:40
    
Do you get the same issue when you perform a clean boot? If the answer is yes, then try checking the disk for errors by running chkdsk C: /r from an elevated command prompt (in case you haven't already). According to the CBS.log you posted, there's a couple of WebAdministration.mfl files which are corrupted. They are part of the Microsoft-Windows-IIS-ManagementScriptingTools.Resources package, so they shouldn't have anything to do with the Windows Store app. –  and31415 Jun 12 at 13:51

1 Answer 1

up vote 0 down vote accepted

What ended up fixing this was renaming the cache folder located at C:\Users\<Your User Account>\AppData\Local\Packages\WinStore_<some characters>\LocalState. After that the store launched fine.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.