Mine stopped on the 8th but came back on the 20th & is now another regular occurrence.
[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: Most helpful
-
Anonymous
2014-10-27T19:59:21+00:00 -
Anonymous
2014-10-26T18:51:27+00:00 Hi,
I have found this error started on 8 Oct and appears every day, just one, no matter how may boots.
-
Anonymous
2014-10-25T14:37:45+00:00 There is an idea on page 9 in this thread (changing the user the task is run as) but in my opinion it will make the task not do what is supposed to do (so you might as well disable the appropriate task in Task Scheduler - see page 9 or page 1).
Some users report that the error had gone away for them about two weeks ago and we are trying to figure out why it's gone for them although they had made no apparent change to Windows settings (my guess it's because they are in US and contact US servers).
-
Anonymous
2014-10-25T14:16:55+00:00 Sadly I am still getting the error. Without reading 11 pages did anyone post a fix by chance?
-
Anonymous
2014-10-25T14:09:45+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.
Confirmed. It's gone for me as well. I, too, can got back to TLS errors and the like which can be "safely ignored".