Hello,

This is driving my insane. Windows Store decided that it no longer opens when I click on it. I have been researching this issue for two days in a row now so far I got no solution. Here is what I have tried:

0. Tried running Appsdiagnostic cabined did not fix any issues. It does try to run WSRESET.EXE but it gives me an error (see point 2 below).

1. Creating a new account - Same issue.

2. Run WSRESET.EXE - Gives me the error: The remote procedure call failed.

• Yes. all RPC services are running as expected.
• Permissions of HKCU\Software\Classes\[...]\AppModel\Repository\Packages seems fine (owner: SYSTEM). Anyway, any attempts of change gives me an access denied error.

3. Tried running SFC - No joy

4. Tried running DISM with /RestoreHeath - No joy.

5. Tried running SFCFIX - Here is what I got:

AutoAnalysis::
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-store-client-ui_31bf3856ad364e35_6.3.9600.17669_none_a935f262375dc12f\WinStoreUI.dll
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17747_none_90df8130dac08ee0\utc.app.json
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17747_none_90df8130dac08ee0\telemetry.ASM-WindowsDefault.json

6. System restore or refresh are NOT an option.

I'm impressed by the poor quality of the Modern/Metro apps. this looks more like pre-Alpha build quality than anything else.

I don't know what to do. Could someone please advise?

Regards,
P.

• Edited by pmdci 19 hours 29 minutes ago

3. Tried running SFC - No joy

4. Tried running DISM with /RestoreHeath - No joy.

5. Tried running SFCFIX - Here is what I got:

AutoAnalysis::
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-store-client-ui_31bf3856ad364e35_6.3.9600.17669_none_a935f262375dc12f\WinStoreUI.dll

So, looks like in both cases for SFC and DISM that "No joy" might have been refined by a look at the CBS.log.  Then what I do is try to figure out what "corrupt" might mean.  Running ProcMon may help, since it may only be a permissions problem of some kind or a problem with a hardlink there may be clues in ProcMon's Registry and File Access record of those events.

Simplest thing to do might be to check the hardlink.  E.g. see what you get from

    fsutil hardlink list C:\Windows\WinStore\WinStoreUI.dll

Perhaps an install had trouble with that?  Again, ProcMon or CBS.log could clarify. 

Unfortunately without the DLL Help Database it's difficult to know where stuff comes from.  E.g. both BING and Google give me no results for this search

6.3.9600.17669 winstoreUI site:support.microsoft.com

so how should I try to find out which update might have been a problem (or where to get replacement modules since DISM doesn't seem to be doing its job)?

HTH

Hi Robert,

Thanks for that.

Here are the results of running fsutil:

C:\Windows\system32>fsutil hardlink list c:\Windows\WinStore\WinStoreUI.dll
\Windows\WinStore\WinStoreUI.dll

C:\Windows\system32>

As for procmon, do you think this could be a problem? I could certainly get the keys from my wife's laptop which also has the latest updates...

Procmon also points out that the crashing of the Store apps writes a logfile named Report.Wer under C:\Users\[USERNAME]\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_winstore_1.0.0.0_d1f803401aaa12efca47e9c0e64e3578bee41d_71dd0148_0e09f6db

Here is what I got in one of the files. Maybe this helps?

Version=1
EventType=MoAppCrash
EventTime=130751369704740441
ReportType=2
Consent=1
UploadTime=130751369705365473
ReportIdentifier=ceb7e7fd-f1a0-11e4-bfbc-88532e7dc714
IntegratorReportIdentifier=ceb7e7fc-f1a0-11e4-bfbc-88532e7dc714
NsAppName=praid:Windows.Store
Response.BucketId=f3387ff7711554c02df0234bef4c025f
Response.BucketTable=5
Response.LegacyBucketId=98886692228
Response.type=4
Sig[0].Name=Package Full Name
Sig[0].Value=winstore_1.0.0.0_neutral_neutral_cw5n1h2txyewy
Sig[1].Name=Application Name
Sig[1].Value=praid:Windows.Store
Sig[2].Name=Application Version
Sig[2].Value=6.3.9600.17415
Sig[3].Name=Application Timestamp
Sig[3].Value=545036ce
Sig[4].Name=Fault Module Name
Sig[4].Value=KERNELBASE.dll
Sig[5].Name=Fault Module Version
Sig[5].Value=6.3.9600.17415
Sig[6].Name=Fault Module Timestamp
Sig[6].Value=54505737
Sig[7].Name=Exception Code
Sig[7].Value=00000004
Sig[8].Name=Exception Offset
Sig[8].Value=0000000000008b9c
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=6153
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=d333
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=d333408dc650b48c4892fc8326b14ff7
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=2d32
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=2d324ec2088127167c52dd60297c7d2e
UI[2]=C:\Windows\System32\WWAHost.exe
LoadedModule[0]=C:\Windows\System32\WWAHost.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\KERNEL32.DLL
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\apphelp.dll
LoadedModule[5]=C:\Windows\SYSTEM32\kernel.appcore.dll
LoadedModule[6]=C:\Windows\SYSTEM32\combase.dll
LoadedModule[7]=C:\Windows\System32\profapi.dll
LoadedModule[8]=C:\Windows\SYSTEM32\wintypes.dll
LoadedModule[9]=C:\Windows\System32\iertutil.dll
LoadedModule[10]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[11]=C:\Windows\system32\msvcrt.dll
LoadedModule[12]=C:\Windows\system32\RPCRT4.dll
LoadedModule[13]=C:\Windows\System32\CRYPTBASE.dll
LoadedModule[14]=C:\Windows\System32\bcryptPrimitives.dll
LoadedModule[15]=C:\Windows\SYSTEM32\user32.dll
LoadedModule[16]=C:\Windows\system32\GDI32.dll
LoadedModule[17]=C:\Windows\system32\IMM32.DLL
LoadedModule[18]=C:\Windows\system32\MSCTF.dll
LoadedModule[19]=C:\Windows\System32\urlmon.dll
LoadedModule[20]=C:\Windows\system32\ole32.dll
LoadedModule[21]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[22]=C:\Windows\System32\WININET.dll
LoadedModule[23]=C:\Windows\System32\USERENV.dll
LoadedModule[24]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[25]=C:\Windows\System32\twinapi.appcore.dll
LoadedModule[26]=C:\Windows\System32\MrmCoreR.dll
LoadedModule[27]=C:\Windows\System32\Bcp47Langs.dll
LoadedModule[28]=C:\Windows\SYSTEM32\rometadata.dll
LoadedModule[29]=C:\Windows\SYSTEM32\shcore.dll
LoadedModule[30]=C:\Windows\System32\Windows.UI.dll
LoadedModule[31]=C:\Windows\System32\NInput.dll
LoadedModule[32]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[33]=C:\Windows\System32\dwmapi.dll
LoadedModule[34]=C:\Windows\System32\CRYPTSP.dll
LoadedModule[35]=C:\Windows\system32\rsaenh.dll
LoadedModule[36]=C:\Windows\System32\bcrypt.dll
LoadedModule[37]=C:\Windows\system32\uxtheme.dll
LoadedModule[38]=C:\Windows\System32\actxprxy.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=MoAppCrash
AppName=winstore_cw5n1h2txyewy!Windows.Store
AppPath=C:\Windows\System32\WWAHost.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=DB59A13B8C37F10793ECDB4C8C835601

Regards,
P.

Here are the results of running fsutil:

I think that is showing that it is there by itself--no association with your maintenance.  That's probabaly what is causing the problem.  Also it is probably old and incompatible with other newer modules which did get installed correctly.  We can check on that using PowerShell.

E.g. to get more detail on the module itself you can use Get-Item (in Administrator: Windows PowerShell -- to minimize warnings, etc.)

Get-Item  C:\Windows\WinStore\WinstoreUI.dll  |  fl *

You can also try to see how that fits in with your maintenance using this next PowerShell pipeline.  Notice that recursion is being specified so I have to give you the starting point.  That's something you have to achieve separately e.g. using  cd $env:windir  and then you could Paste the bolded part into your command line. 

PS C:\windows> LS -Re -Fi WinStoreUI.dll | sort LastWriteTime | ft Length, FullName -AutoSize

Also note that though I have specified -AutoSize to try to enable capture of the full path you may have to resize your PowerShell window to actually get enough of it, e.g. at least enough to see the full file version each path contains.

I was actually anticipating that the hardlink would be associated with an old version in WinSxS, so then imagining suggesting you could try using fsutil to remove that but now I'm not sure whether to try renaming it to be a WinSxS item or delete it or what.  I don't think it is supposed to be real.  E.g. mine is showing a link to a WinSxS module, the sizes of both are the same and they sort consecutively. 

Hmm... Get-Item is showing that both Exist? (Exists : True).  Then in fact, I don't know how to tell which one is real.  It's a good thing mine are working, however that happens.   <eg>

As for procmon, do you think this could be a problem?

What I usually use ProcMon for first is getting an inventory of the diagnostics.  I do that with Operation Is WriteFile and then use the Tools Count occurrences... on the Path field which can then be sorted by Count.  After that I look at those diagnostics and if I see something that I would like clarification of I try to infer which WriteFile would have been associated with that record (e.g. using especially the Length= value in the Detail field or the sequence of those or any timing information).  Then I think I can assume that any preceding Registry and File Access events might have been associated with the generation of that one.  So, unless I have a particular hypothesis that I want to test, e.g. by finding records which prove or disprove it, I just use the ProcMon trace to supplement the diagnostics that were found by the "inventory".

HTH

Procmon also points out that the crashing of the Store apps writes a logfile named Report.Wer

No sign of  WinStoreUI.dll  in there.   But ProcMon might show if it had been loaded in this thread before the crash.  Also, ProcMon gives us pseudo Stack information in each record so you might be able to Find it in there. Otherwise, it's possible that this is unrelated to your other symptom.  FWIW I think there is more potential in finding a resolution with the other symptom and then just hope that others like this just go away.  ; )