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 Sunday, May 03, 2015 11:56 AM

Here are the results of the commands you asked me to run:

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


PSPath            : Microsoft.PowerShell.Core\FileSystem::C:\Windows\WinStore\WinstoreUI.dll
PSParentPath      : Microsoft.PowerShell.Core\FileSystem::C:\Windows\WinStore
PSChildName       : WinstoreUI.dll
PSDrive           : C
PSProvider        : Microsoft.PowerShell.Core\FileSystem
PSIsContainer     : False
VersionInfo       : File:             C:\Windows\WinStore\WinstoreUI.dll
                    InternalName:     WinStore
                    OriginalFilename: WinStoreUI.dll.mui
                    FileVersion:      6.3.9600.17195 (winblue_gdr.140530-1506)
                    FileDescription:  WinStore
                    Product:          Microsoft Windows Operating System
                    ProductVersion:   6.3.9600.17195
                    Debug:            False
                    Patched:          False
                    PreRelease:       False
                    PrivateBuild:     False
                    SpecialBuild:     False
                    Language:         English (United States)

BaseName          : WinstoreUI
Mode              : -a---
Name              : WinstoreUI.dll
Length            : 1229312
DirectoryName     : C:\Windows\WinStore
Directory         : C:\Windows\WinStore
IsReadOnly        : False
Exists            : True
FullName          : C:\Windows\WinStore\WinstoreUI.dll
Extension         : .dll
CreationTime      : 02/05/2015 23:36:42
CreationTimeUtc   : 02/05/2015 22:36:42
LastAccessTime    : 02/05/2015 23:36:42
LastAccessTimeUtc : 02/05/2015 22:36:42
LastWriteTime     : 29/01/2015 01:54:50
LastWriteTimeUtc  : 29/01/2015 01:54:50
Attributes        : Archive

As for the next PowerShell command:

PS C:\Windows> LS -Re -Fi WinStoreUI.dll | sort LastWriteTime | ft Length, FullName -AutoSize
LS : Access to the path 'C:\Windows\System32\LogFiles\WMI\RtBackup' is denied.
At line:1 char:1
+ LS -Re -Fi WinStoreUI.dll | sort LastWriteTime | ft Length, FullName -AutoSize
+ ~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : PermissionDenied: (C:\Windows\Syst...es\WMI\RtBackup:String) [Get-ChildItem], Unauthoriz
   edAccessException
    + FullyQualifiedErrorId : DirUnauthorizedAccessError,Microsoft.PowerShell.Commands.GetChildItemCommand


 Length FullName
 ------ --------
1229312 C:\Windows\SoftwareDistribution\Download\1cc2ec149ef5d89d405fa08fec41a23b\amd64_microsoft-windows-store-clie...
1229312 C:\Windows\WinSxS\amd64_microsoft-windows-store-client-ui_31bf3856ad364e35_6.3.9600.17669_none_a935f262375dc...
1229312 C:\Windows\WinStore\WinStoreUI.dll

I tried running procmon will a filter that specifically looks for WinstoreUI (not only WinStore) in the PATH and it did NOT show anything.

Thanks for your help so far.

Regards,

P.

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

That looks good.

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

That too.

I tried running procmon will a filter that specifically looks for WinstoreUI (not only WinStore) in the PATH and it did NOT show anything.

Doing what?  What was it that made us think that there was a problem with this module?  Try that again, tracing it this time?

Really the only possibly significant difference that I can see is still your fsutil result.  What about also doing an fsutil on your WinSxS module?  FWIW when I do that I see both listed too.  The applied copy (in WinStore) is listed before the WinSxS, in case that means anything.  I still don't know which one is supposed to be real but I don't think that there are two physical copies.

Another related diagnostic that I am aware of but have never used is sxstrace.exe.  Maybe having that running would give ProcMon something extra to show you?

Now I'm wondering if we are on a wild goose chase, following red herring.   Isn't Blackbox troubleshooting of closed source software fun?   ; }

HTH

Hi Robert,

I am new to procmon. So what I did first was to filter all entries as to show only entries that contains the word winstore in the path. So every time I try to open the Store app, I can see the relevant entries.

Then when you mentioned WinStoreUI.dll I decided to remove the winstore filter and replace it with 'WinStoreUI'. However when I open the Store app, nothing shows on procmon when the WinStoreUI filter is in place.

If you have any suggestions on how to run procmon to look for clues, please let me know.

I tried running sxstrace. I generated a trace file but when I parse it to a txt. I get a 3 bytes txt file with nothing in it...

Regards,

P.

PS: I do not fhind this fun at all :) -- In fact I find Modern apps to be at pre-alpha quality at this stage. Maybe Windows 10 can bring them to beta quality. I have a lot of issues with tham such as not being able to specify install location, not being able to specify location of swapfile.sys, apps take longer to open than desktop apps (what with those splash screens?!) and now this ridiculously complicated troubleshooting.

• Edited by pmdci 16 hours 51 minutes ago rant

If you have any suggestions on how to run procmon to look for clues, please let me know.

As I indicated I just use it for finding clues by finding diagnostics and supplementing them.  Is it that you don't understand that ProcMon is used to trace other activity, such as use of the other tools that you are having trouble with?

I tried running sxstrace. I generated a trace file but when I parse it to a txt. I get a 3 bytes txt file with nothing in it...

As I said I haven't used it.  I imagine it is generating binary trace information which perhaps might be useful on its own but I was only thinking of it as adding additional trace points into the ProcMon trace, e.g. in particular in one filtered by WriteFile.

My point about trying to find WinStoreUI in a trace of the crash that you had (assuming that is recreatable) is that ProcMon might have it recorded in Stack detail in some of the records when it was loaded.  You would not be able to filter that using a Path filter. 

Sorry you missed my frustrated note of sarcasm about trying to do self-support of Microsoft products.  Looks like you should wait and see if someone who knows how this stuff works wants to respond.  Otherwise call support.

 

Good luck

Hi Robert,

I did not miss your note of sarcasm as it wasn't that subtle. I just took on the opportunity to vent on my frustration with a product that seems to have been rushed into the market.

I might as well just give up with this junk and wait for Windows 10 to fix it.

Regards,
P.

Hi Robert,

I am new to procmon. So what I did first was to filter all entries as to show only entries that contains the word winstore in the path. So every time I try to open the Store app, I can see the relevant entries.

Then when you mentioned WinStoreUI.dll I decided to remove the winstore filter and replace it with 'WinStoreUI'. However when I open the Store app, nothing shows on procmon when the WinStoreUI filter is in place.

If you have any suggestions on how to run procmon to look for clues, please let me know.

I tried running sxstrace. I generated a trace file but when I parse it to a txt. I get a 3 bytes txt file with nothing in it...

Regards,

P.

PS: I do not fhind this fun at all :) -- In fact I find Modern apps to be at pre-alpha quality at this stage. Maybe Windows 10 can bring them to beta quality. I have a lot of issues with tham such as not being able to specify install location, not being able to specify location of swapfile.sys, apps take longer to open than desktop apps (what with those splash screens?!) and now this ridiculously complicated troubleshooting.

• Edited by pmdci Monday, May 04, 2015 2:29 PM rant