Win 7 SP1 Wont Update - Error 80246002

[Ex_Brit]

I've even, stupidly it turns out, tried a repair install of Windows and it makes no difference so am wondering if the problem is at MS's end?
I say stupidly because in the middle of doing a repair (upgrade) install of Windows I remembered I also had 7 SP1 installed on my Netbook so fired that up and it is giving exactly the same error.
Which tells me that it isn't a problem here.
By contrast my Vista SP2 and Win 8.1 Pro both update just fine.
I've run several Fixits to no avail.
Comments anyone?

 

[4wd]

You're not alone... probably some millions more

see http://www.sevenforums.com/windows-...rror-80246002-when-clicking-chek-updates.html

 

[Mayank Parmar]

Try to run Trojan Remover, it will replace any bad service or it will create service in case if service is missing!

 

[Ex_Brit]

Thanks guys will try some things as suggested in link. I used to use TR Mayank but ditched it a while ago, but will consider it.

 

[4wd]

Thanks guys will try some things as suggested in link

I'd think there is not much worth to try from our side (with the risking of breaking some additional things), it's up to MS to fix this one. Have tried everything and more, am letting the experiments rest until MS figures out what's going on.

Try to run Trojan Remover, it will replace any bad service or it will create service in case if service is missing!

??
Maybe read the posts about 80246002, on this forum and for example Windows - Microsoft Community

 

[NoelDP]

How about some objective data?? :devil:

Please follow the Windows Update Posting Instructions and post the requested data
If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)


Also, please post the C:\Windows\windowsupdate.log file

 

[Ex_Brit]

There is a simply fix on the Microsoft forums - add DNS 8.8.8.8 and 8.8.4.4 to your Network Adapter Properties, ipv4 settings and it will work.

 

[NoelDP]

... if you trust Google to be your DNS provider

There shouldn't be a need to specify those parameters if the system is functioning properly (and there are possibly good reasons not to use Google as primary DNS, depending on your tin-foil/paranoia ratio )

 

[Ex_Brit]

According to the MVP posting HERE it may even enhance security.

Until Microsoft admit their update department needs firing or a good dose of laxative at least then I see no reason to worry too much. In my case I didn't realise this easy fix was live and had done a repair install of 7 SP1 meaning there were approximately 150 updates to go and I couldn't download any. The second I input those it all worked again.

 

[Layback Bear]

Google enhancing security just sound strange to me.

 

[Ex_Brit]

Well that was my concern too but I would imagine they are pretty hot on security.


I thought I'd post illustrations of what I did:

 

[Ex_Brit]

As a footnote I tried reversing that setting and immediately a WU check failed with the same error code. I'll keep testing it from time to time.

 

[NoelDP]

Try using ipconfig /flushdns and rebooting before changing the DNS back to normal.

 

[Ex_Brit]

I plan on doing just that next time I boot into 7. Must have been a DNS issue and ISP's couldn't reach MS servers as reports are showing up on their forums that it's now working OK anyway.
Thanks

 

[Ex_Brit]

Microsoft's changed DNS must have finally filtered through the world-wide web as I can now poll for updates without getting that error with my DNS set back to the default (Automatic).

So it appears that things are normalizing again.