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.

What I did managed to narrow down to is that if I call the windows store using the command prompt 'start' command, I get a "remote procedure call" error (the the one in point 2 below).

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. Tried re-registering the Store app by running: powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\WinStore\AppxManifest.xml

7. Tried the instructions found here to fix the remote procedure call error.

NOTE: 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 Thursday, May 14, 2015 9:30 PM added point 7

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

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

The two .json files is normal to show up after SFC per: https://support.microsoft.com/en-us/kb/3022345?wa=wsignin1.0

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

I would start with repairing what was corrupt by replacing it with a known good copy if you haven't already tried?

I'm also assuming you've tried this already:

Open RegEdit

Go to HKCU\Software\Classes\LocalSettings\Software\Microsoft\Windows\CurrentVersion\AppModel\Repository\Packages

• Right click the key and select Permissions
• Check if the Owner is SYSTEM. If not, change the Owner to SYSTEM.

• Edited by aw00t 4 hours 48 minutes ago