[W8.1 Update 1] "Windows Store failed to sync machine licenses. Result code 0x80070490"

Anonymous
2014-04-08T18:57:02+00:00

After a clean install of windows 8.1.1 using the ISO from Technet I started getting the following error message in my event log the first time I start my machine in the morning:

Event 512 Store-Licensing  "Windows Store failed to sync machine licenses. Result code 0x80070490"

I use a Microsoft account and I have synced by Modern apps many times manually. Running the scheduled task manually will also produce the same error. I disabled the Scheduled Task that runs the sync and I'll see if it shows up tomorrow. Btw, the Store seems to be working fine.

I  read somewhere that the MS Store will be changed for 8.1.1 so I wonder if the 'new' store will stop these messages.

The Scheduled Task that kicks this off appears to be Microsoft/Windows/WS and is called WSRefreshBannedAppsListTask.

***Post moved by the moderator to the appropriate forum category.***

Windows for home | Previous Windows versions | Performance and system failures

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

128 answers

Sort by: Most helpful
  1. Anonymous
    2014-10-16T02:37:35+00:00

    Appears to have disappeared on mine also.   Seems Microsoft finally fixed this.

    Now off to report many other REGULAR errors reported in the Events log.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-10-15T06:56:32+00:00

    For me the error has disappeared ~two weeks ago! :)

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-10-15T05:19:43+00:00

    No longer there with tech preview...

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-10-14T20:36:16+00:00

    Latest Windows Updates (from October 2014) have been installed, yet the error still appears in the Event Viewer.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2014-09-27T19:54:07+00:00

    The really sad part is that it's us - the users - speculating what is causing the error and why. No official Microsoft statement at all (or not that I'm aware of one).

    Was this answer helpful?

    0 comments No comments