error code 0xc03f300d

Anonymous
2018-04-08T15:38:19+00:00

cannot install apps even free ones I own.

cannot sign in to xbox games

Windows for home | Previous Windows versions | Microsoft Store

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

75 answers

Sort by: Most helpful
  1. Anonymous
    2018-04-09T01:20:14+00:00

    A couple of months ago W8.1 couldn't get into xbox. It appears they made a patch not a fix. Now we got WStore effected also. Just look at trying to type in this forum. They messed up.

    Please look into this MS. It appears you caused it, and I am losing confidence in your ability to control your systems. Unless you want us all in W10?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-04-08T23:51:55+00:00

    The same error occurs in all my family's account on our home computer. Same issue on another Windows computer (my laptop). DEFINITELY a Windows issue: MS store apps on my iPhone and Android phone (including logging into Xbox Live). Occurs on my Windows 8.1 PC, on my Windows 10 PC, on my Windows 8 phone, and on my Windows 10 phone.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-04-08T23:12:48+00:00

    I am getting the same message, Windows 8 version.  Frustrating...it was working yesterday.  Get same message with all microsoft games I "own" so why a message about purchase? Tried uninstalling and then reinstalling.  same problem.  Grrrr

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-04-08T22:29:16+00:00

    I am also having the same problem and cannot even play/download the games I already purchased!Same error code that everybody else is getting. Unable to find a solution-I have tried everything I can think of.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-04-08T22:00:41+00:00

    Yeah, I saw a similar error thread back on 2015 and seems it took more than 10 days for them to fix it...

    Was this answer helpful?

    0 comments No comments