Indeed I'm in Europe. Could that really make a difference?
[W8.1 Update 1] "Windows Store failed to sync machine licenses. Result code 0x80070490"
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.
128 answers
Sort by: Newest
-
Anonymous
2014-10-25T08:35:03+00:00 -
Anonymous
2014-10-25T07:57:41+00:00 I've applied all updates but I still get the error.
Out of curiosity - are you in US or in Europe? Perhaps the problem was fixed in US servers and not in Europe.
-
Anonymous
2014-10-24T08:15:43+00:00 I've applied all updates but I still get the error.
-
Anonymous
2014-10-18T15:38:14+00:00 My last two were on 10-6 & 10-8, 2 to 3 minuets after waking.
Woke quite a few times after that with no error.
I assume that means it is fixed for me as well (?) in NE USA.
-
Anonymous
2014-10-17T20:26:19+00:00 Interesting - I still get the same error. Did you change the WSRefreshBannedAppsListTask scheduled task in any way? Are you currently connecting to the Internet from US territory (perhaps the fix is only present on some servers)?