[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

128 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-06-18T07:08:53+00:00

    In my case, in Task Scheduler > Microsoft > Windows > WS there are two tasks that report something else than (0x0; which I think is "Success") as 'Last Run Result' and they are:

    Sync Licenses: 0800700E

    WSTask: 0800710E0

    "Surpricingly" I did do, by quickly searching, find any additional info what do those Run Results mean.

    Also attached a copy of that Task Scheduler screen for others to compare. Yet, of course, I do not know if these have anything to do with the actual Error in Event viewer.

    And yes, I fully agree, that 99,5% of Windows users never bother (or even know / care) about the Event log in general... For me, despite not a developer nor very very advanced user, it's ~bi-weekly habbit. But that's another story ;)

    Ramesh.Kumar, how to escallate this to 2nd/3rd level support @ Microsoft?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-06-18T01:07:56+00:00

    I have done everything, and some things not mentioned on this forum. I did "system refresh". Which took about an evening from me. After "system refresh" and updating to 8.1.. 8.1.1 and have the same problem. Next thing for me would be installing a complete different OS :)

    But as I say, I have this problem at the work PC, and at home on my Desktop and Laptop PC's. And as I said. How many do you think have this problem as 99.9% of computer users aren't checking the event viewer.. They just use the computer until it stops...

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-06-17T19:13:44+00:00

    Hello,

    Just a quick question:

    What would it take to have the issue escalated to 2nd/3rd level support within Microsoft? Was an attempt to reproduce the issue within Microsoft infrastructure made?

    The thread clearly proves that this seems to be a wide-spread issue (it's just that most users probably do not check the Event Logs so their reports do not flood the forum). The thread also proves that Windows 8.1 install refresh does not help and that the problem had started after Windows 8.1 Update.

    The thread had basically exhausted all the investigation that could be done by the end user. I believe all that remains is to attach a debugger to the process and/or decrypt SSL traffic from the server the WSRefreshBannedAppsList connects to (something end user should never have to do).

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-06-17T18:46:05+00:00

    Hi Franziska M. & RayHallman,

    That's exactly why I do NOT agree to make an OS refresh / re-install. We all have paid for a working OS, right... ;o)

    One thing I will do tonight is to put a few Tasks on "not to execute" -status and see how they impact (if any), will keep you posted.

    //timo

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-06-17T13:41:36+00:00

    I doubt there will be any help here. They will just keep copy pasting instructions how to perform a clean boot or reset Windows, completely ignoring the fact that this is an actual bug that needs to be looked at by the developers.

    We get this not only at home on every laptop/desktop machine but also at work on all Windows 8.1 installations and thats over 10 PCs total. Something in the Update 1 for 8.1 has caused this error being logged.

    Best regards

    Was this answer helpful?

    0 comments