Windows 8.1 : Store won't connect [Error 0x80004005]

Discussion in 'Windows 8' started by pixelo, Nov 6, 2013.

  1. pixelo

    pixelo MDL Novice

    Jun 3, 2012
    8
    0
    0
    #1 pixelo, Nov 6, 2013
    Last edited: Nov 6, 2013
    Hi,

    I recently installed Windows 8.1 entreprise x64 (French), connected it to a new Microsoft Account (verified)
    but everytime i open the Store it shows this screen.
    Sans titre.png
    I've tried :

    - wsreset.exe
    - powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\WinStore\AppxManifest.xml
    - Changing Microsoft account

    but nothing works


    Update

    [SOLVED] USE "RESET WINDOWS WITHOUT DELETING FILES"
     
  2. hbhb

    hbhb MDL Expert

    Dec 15, 2010
    1,017
    263
    60
    disable your anti-virus if any and try
     
  3. pixelo

    pixelo MDL Novice

    Jun 3, 2012
    8
    0
    0
    it's a fresh install so no antivirus installed yet..
    i just disabled Windows Defender.
     
  4. PaulDesmond

    PaulDesmond MDL Magnet

    Aug 6, 2009
    6,979
    7,149
    240
    are you activated?
     
  5. pixelo

    pixelo MDL Novice

    Jun 3, 2012
    8
    0
    0
    i activated it using KMSpico v9.0.3.20131029_Beta
     
  6. PaulDesmond

    PaulDesmond MDL Magnet

    Aug 6, 2009
    6,979
    7,149
    240
    other Metro apps are working?
     
  7. pixelo

    pixelo MDL Novice

    Jun 3, 2012
    8
    0
    0
    #7 pixelo, Nov 6, 2013
    Last edited: Nov 6, 2013
    (OP)
    IE, News, Video, Audio, Skype, ... everything is working perfectly, only Store seems to have this problem
    also tried this :

    - deleting SSL status from IE
    - regsvr32 softpub.dll wintrust.dll

    but still no result.


    I wanna ask you guys, is it possible to install Windows 8 Pro and activate it with Microsoft Toolkit and then from there update to Win8.1, am i gonna have to reactivate ?
     
  8. PaulDesmond

    PaulDesmond MDL Magnet

    Aug 6, 2009
    6,979
    7,149
    240
    Store: is this problem from the beginning or is it a temporary bug? Since all apps seem to work there could be a local problem but not sure

    Installing 8 and activating it with MTK will get you to a new activation when upgraded to 8.1, no way arround
     
  9. pixelo

    pixelo MDL Novice

    Jun 3, 2012
    8
    0
    0
    The problem existed from the beginning o_O
     
  10. PaulDesmond

    PaulDesmond MDL Magnet

    Aug 6, 2009
    6,979
    7,149
    240
    #10 PaulDesmond, Nov 6, 2013
    Last edited: Nov 6, 2013
    I saw that you even reregistered the store which confuses me. This method helps solving most of the problems
    No idea atm
     
  11. pixelo

    pixelo MDL Novice

    Jun 3, 2012
    8
    0
    0
    #11 pixelo, Nov 6, 2013
    Last edited by a moderator: Apr 20, 2017
    (OP)
    posting last lines from my winstore.log hope this helps :

    Code:
    2013-11-06 13:30:26.444, _Info_                WS   [00002156:00002740] WinStoreBroker::GetParentalControlSettings: Entering
    2013-11-06 13:30:26.444, _Info_                WS   [00002156:00000284] WinStoreBroker::GetSLSDiscovery: Entering. fExpire is 0
    2013-11-06 13:30:26.444, _Info_                WS   [00002156:00002740] WinStoreBroker::GetParentalControlSettings: SID for current user is S-1-5-21-1735778623-880248060-3040968324-1001
    2013-11-06 13:30:26.444, _Info_                WS   [00002156:00002740] WinStoreBroker::GetParentalControlSettings: not enabled; IsWPCEnabled returned 0x00000000
    2013-11-06 13:30:26.444, _Info_                WS   [00002156:00002740] WinStoreBroker::GetParentalControlSettings: Leaving with a result of 0x0
    2013-11-06 13:30:26.448, _Info_                WS   [00002156:00000284] WinStoreBroker::GetSLSDiscovery: Leaving with a result of 0x0
    2013-11-06 13:30:39.619, _Info_                WS   [00002156:00000284] WinStoreBroker::GetUpdateCountSource: Entering
    2013-11-06 13:30:39.619, _Info_                WS   [00002156:00000284] WinStoreBroker::GetUpdateCountSource: Leaving with a result of 0x0
    2013-11-06 13:30:39.619, _Info_                WS   [00002156:00000284] CUpdateCountDispatcher::UnregisterHandler - unsubscribing from WNF_WUA_NUM_PER_USER_UPDATES notifications.
    2013-11-06 13:30:39.619, _Info_                WS   [00002156:00000284] WinStoreBroker::GetUpdateCountSource: Entering
    2013-11-06 13:30:39.619, _Info_                WS   [00002156:00000284] WinStoreBroker::GetUpdateCountSource: Leaving with a result of 0x0
    2013-11-06 13:30:39.619, _Info_                WS   [00002156:00003612] WinStoreBroker::RecordStoreActivity: Entering.
    2013-11-06 13:30:39.619, _Info_                WS   [00002156:00000284] WinStoreBroker::GetInstallControl: Entering
    2013-11-06 13:30:39.619, _Info_                WS   [00002156:00000284] WinStoreBroker::GetInstallControl: Leaving with a result of 0x0
    2013-11-06 13:30:39.619, _Info_                WS   [00002156:00003612] WinStoreBroker::RecordStoreActivity: Leaving with a result of 0x0
    2013-11-06 13:30:39.619, _Info_                WS   [00002156:00003612] CProgressDispatcher::UnregisterHandler: Unregistered handler {49994037-4161-4F16-BA5E-486AC49C7D3A} (cookie=3, git=1281)
     
  12. Nucleus

    Nucleus MDL Guru

    Aug 4, 2009
    2,868
    2,950
    90
    #12 Nucleus, Nov 6, 2013
    Last edited by a moderator: Apr 20, 2017
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. pixelo

    pixelo MDL Novice

    Jun 3, 2012
    8
    0
    0
    still persist
     
  14. pixelo

    pixelo MDL Novice

    Jun 3, 2012
    8
    0
    0
    Problem solved by "resetting Windows without deleting files" :biggrin:
    thanks everyone
     
  15. hbhb

    hbhb MDL Expert

    Dec 15, 2010
    1,017
    263
    60
    good job Pixelo:bye1:
     
  16. Enigma256

    Enigma256 MDL Senior Member

    Jan 17, 2011
    357
    309
    10
    0x80004005 is the code assigned to "Unspecified Error" which unfortunately doesn't narrow things down. When I first started using Win8, I got that error from the store because I had disabled the Firewall service (which the Store apparently didn't like). But, again, this being a 0x80004005 code, it could easily have been something else.