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).