Cannot open\load App store with Win 8 Enterprise upgrade


Recommended Posts

Hello, I hope someone can help me. I upgraded my work PC with windows 8 Enterprise edition from win 7. I activated my windows, I signed in with a live account and trusted my PC. Yet the App store will not launch. I get the following error in event viewer:

Activation of the app winstore_cw5n1h2txyewy!Windows.Store for the Windows.Launch contract was blocked because of a temporary issue with its license. Try launching the app again in a moment.

- System

- Provider

[ Name] Microsoft-Windows-Immersive-Shell [ Guid] {315A8872-923E-4EA2-9889-33CD4754BF64} EventID 5974 Version 0 Level 2 Task 5974 Opcode 0 Keywords 0x4000000000000000 - TimeCreated

[ SystemTime] 2012-08-20T15:38:30.313247700Z EventRecordID 39 Correlation - Execution

[ ProcessID] 3656 [ ThreadID] 5496 Channel Microsoft-Windows-TWinUI/Operational Computer dxxx.domain.com - Security

[ UserID] S-1-5-21-182877557-1355096703-1231754661-1029

- EventData

AppId winstore_cw5n1h2txyewy!Windows.Store ContractId

Windows.Launch

Does anyone have an idea what is causing this? I am on a work domain is there anyway to troubleshoot it so I know exactly what it is trying to do to tell my network admins if something is blocking the app store. I did run this app apps.diagcab and it said everything is ok. Help please, if not I will need to go back to windows 7. Let me know if you need additional info.

Link to comment
Share on other sites

If it's the same issue as Server 2012, if your running as the account named "Administrator", you can't access the store. You have to make a user, give it admin privileges (if you care to) and use that, it will be able to use the store.

Link to comment
Share on other sites

This is a MSDN Key I am using. I am logged in as my domain ID with admin privileges. I been reading here http://social.technet.microsoft.com/Forums/en/W8ITProPreRel/thread/acc45e6e-86fe-4928-9f33-429ce8bebc8f that it might be an issue with joining to a domain and GPO is affecting it.

I wish MS had more logging features to show what exactly is causing the issue. any other ideas I can try?

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.