Windows General

[dave in pa]

Yesterday (06/24/2014) Microsoft issued an update for windows update, which they said was required in order to receive new updates. It installed without any problems,except it doesn't work.

I tried the fixit tool but that doesn't find any errors. To make matters worse, it appears that windows update installed a different version of the update agent than is appropriate for my system (Windows 7 Home Premium). Windows support websie for this update says the correct version is Windows update agent 7.6.7600.256, but windows update installed version 7.6.7600.320, and you can see the result from the image as to what happens when I try to check for updates.

I would prefer not to do a system restore, but how do I fix this?

Is this this the same issue corrected / posted by LoginBroken on Feb 23 2011?

[PudgyOne]

e003sb,

The little command was just re-registering the dll's for Windows Update. There were 7 dll's for Windows XP that needed re-registered after installing some systems. I had to research this a few years ago. Once the dll's were re-registered, Windows Updates works with no problems. Not all the dll's were used on Windows 7.

Rick

[delluser004]

I had the same problem when windows update agent was updated to version 7.6.7600.320 with error code 80246002.

I'm using Win7 Home premium 64 bit on Dell Inspiron n5110

 I solved the problem from the instructions from here:

http://mikemstech.blogspot.com/2011/12/how-to-perform-offline-system-integrity.html

This will show you how to use your win7 installation disc to check and repair critical system files.  BTW I skipped the "chkdsk" part and it still worked.  And remember to put the correct drive letters for system boot and windows OS partition.  You can find more info here: 

http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html

Hope that helps.

[e003sb]

Thanks Rick. I figured the command line probably registered the "dll" files but wasn't sure. The older "wuaueng.dll" file dated 06/02/2012 was backed by Windows on my system if you do a search for it via Win Explorer and makes for satisfactory replacement. Of the four files noted in your command file, three are dated 05/14/2014 and "wuaueng.dll" is now dated 06/02/2012 via my Win Explorer. But hey, Update works! All one has to do is replace the newer one with the older one and then re-register it. At least that technique works on my system. It is a temporary fix. It's a shame about the new Update Agent as it is touted to be more bullet-proof. MS claims (as the poster above states) that the Update Agent is on a "gradual rollout". Windows Update: A service designed to protect your OS from grief.... is causing quite a bit of grief! :>) Scott

[dave in pa]

Thanks Rick, that worked and so does windows update.

I don't know what those dynamic link libraries do, but it appears everything is operating properly.

You really do rock.

Thanks again.

[PudgyOne]

dave in pa,

Glad you got it working! :emotion-21: Thanks for posting back.

Take care,

Rick

[e003sb]

Thanks from me too Rick. I used your command and now WU is working with the newer "dll" file. Must have been user error, or something specific to my system. Appreciate you. Scott

[PudgyOne]

Scott,

Glad you got it working! :emotion-21: Thanks for posting back.

Take care,

Rick

[idalv]

Rick, thanks for your instructions.

Windows Update on my Win 7 work again

Idalv

[idalv]

Rick, thanks for your instructions.

Windows Update on my Win 7 64 bit SP1 work again well.

Thank you

Idalv

[PudgyOne]

idalv,

Glad you got it working! :emotion-21: Thanks for posting back.

Take care,

Rick