In my personal experience, I have been using Google's public DNS service on a couple of machines for several months and I experienced the 80246002 error this morning on a Windows 7 laptop using Google's public DNS and was subsequently able to resolve it.
unfortunately, you don't give any details about how you resolved the problem..
i am thinking that the problem is due to the recent update for "windows update agent".. see this post, by "jranger2112":
jranger2112 replied on
I am just adding this this thread, since Microsoft seems to have totally messed up wua .. current
Windows Update Agent 7.6.7600.320 is broken, this needs to be fixed now, lot of people are going to be hanging out in the wind on this one
of note, this is from a fresh install, only sp1 is installed on win7x64 .. this patches installed without permission on my end
windows update agent 7.6.7600.320
definition update for windows defender
update for windows kb958488
kb2685811
kb2505454
this is as far as the update process got after sp1 was installed, since I see wua767600.320 is not showing up in Microsoft search for this update...
this is the log entry that is causing the issue directly, not sure if there is anything upstream that is messing things up
-08-28 03:40:45:108 336 bb8 Misc WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab are not trusted: Error 0x80070002
2014-08-28 03:40:45:170 336 bb8 Setup WARNING: SelfUpdate check failed to download package information, error = 0x80246002
2014-08-28 03:40:45:170 336 bb8 Setup FATAL: SelfUpdate check failed, err = 0x80246002
2014-08-28 03:40:45:170 336 bb8 Agent * WARNING: Skipping scan, self-update check returned 0x80246002
2014-08-28 03:40:45:170 336 bb8 Agent * WARNING: Exit code = 0x80246002
--end
i don't know if it a windows 7 thing..a windows 8 thing.. it seems there is an issue with a "certficate"..
i have not seen the same update for "windows update agent" on my computer.. (also, i am running windows xp and the issue might not affect windows xp.. maybe windows xp doesn't check for certificates the same way that windows 7 does)..
i could try testing things, going to "windows update", but there is no need for me to go there, and i could just wind up with problems, if the update for "windows update agent" is installed..
after all of the people who are experiencing problems with "windows updater", i hope someone at MS is aware of the problem and is trying to figure out how to straighten things out..
it is interesting that using google's DNS-servers seems to be a workaround for the problem.. i don't know why that would make a difference but apparently it does..