Windows Update Agent 7.6.7600.320

There is no stand-alone Windows Update Agent available to download. If you have automatic updating turned on, the latest version of the Windows Update Agent is downloaded and installed automatically on your computer.

http://support.microsoft.com/kb/949104

Also: Information for network administrators about how to obtain the latest Windows Update Agent

http://support.microsoft.com/kb/946928

I could find no information what problems version 7.6.7600.320 fixes.

J W Stuart: http://www.pagestart.com

@JW

Why not just provide the seminal reason and basis for the Windows Update agent/serivce updating itself without user intervention.

Windows EULA

<qp>

 Consent for Internet-Based Services.

The software features described below and in the Windows 7 Privacy Statement

connect to Microsoft or service provider computer systems over the Internet.

Windows Update. To enable the proper functioning of the Windows Update service in the software (if you use it),updates or downloads to the Windows Update service will be required from time to time and downloaded and installed without further notice to you.

</qp>

i.e. by use of Windows on any pc the user has already agreed to allow Microsoft to download and install updates (without notification) for the Windows Update service.

Defender will update in the background as well as the update agent.  These a/v file updates are designed to install in the background (as do other a/v updates that is normal for a/v updates)  None of these however will kick a reboot.  Can you post your windowsupdate.log file on a onedrive/skydrive as I can check to see what exactly did kick a reboot - as I will state that it wasn't the windows update agent nor was it the def file that would make a system reboot.

Here's the relevant portion of it: 

2014-08-02    16:02:04:883     836    518    Shutdwn    user declined update at shutdown

2014-08-02    16:02:04:883     836    518    AU    Successfully wrote event for AU health state:0

2014-08-02    16:02:04:883     836    518    AU    AU initiates service shutdown

2014-08-02    16:02:04:883     836    518    AU    ###########  AU: Uninitializing Automatic Updates  ###########

2014-08-02    16:02:04:898     836    518    Setup    Performing pre-shutdown installation of agent

2014-08-02    16:02:04:898     836    518    Report    CWERReporter finishing event handling. (00000000)

2014-08-02    16:02:04:898     836    518    Setup    Installing setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"

2014-08-02    16:02:12:417     836    518    Setup    Install of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" succeeded and requires reboot

2014-08-02    16:02:12:527     836    518    Service    *********

2014-08-02    16:02:12:527     836    518    Service    **  END  **  Service: Service exit [Exit code = 0x240001]

2014-08-02    16:02:12:527     836    518    Service    *************

2014-08-02    16:20:42:832     548    6b8    Misc    ===========  Logging initialized (build: 7.6.7600.256, tz: -0400)  ===========

2014-08-02    16:20:42:832     548    6b8    Misc      = Process: C:\Windows\system32\rstrui.exe

2014-08-02    16:20:42:832     548    6b8    Misc      = Module: C:\Windows\system32\wuapi.dll

2014-08-02    16:20:42:832     548    6b8    COMAPI    FATAL: Unable to connect to the service (hr=8007043C)

2014-08-02    16:20:42:832     548    6b8    COMAPI    WARNING: Unable to establish connection to the service. (hr=8007043C)

2014-08-02    19:53:44:845     900    19bc    Misc    ===========  Logging initialized (build: 7.6.7600.320, tz: -0400)  ===========

That 3hr gap in the timing is where I freaked out thinking I had a virus.  It did indeed reboot itself.  Shutting down the window I was actively typing in.  I have no idea what that "user declined update at shutdown" is.....

When I contacted MS tech support I was basically told there was nothing wrong.  Which, sorry, there IS something wrong.  Even if this is exactly how MS programmed these software/updates to behave the reaction of people on here shows how wrong it is.  How many more people are freaking out thinking they've picked up a virus cause MS couldn't be bothered to tell people that an update was being forced through??  How many more have interrupted or forced stop on this update and others thinking it was a virus??

I will also add, I have seen no error messages about not being able to install updates, but according to that log there HAVE been attempts to download updates, which have failed.  Even though when I tell windows to check for updates it says that there are none.  Nor does it appear to have installed any on its own.

I have Windows Update turned off by default. I always create an Image Backup before installing Windows Updates, Software Updates, installing or un-installing software, Etc.!

I checked Windows Update the other day and the update to the WU engine is not listed as being available or installed at this time, same with my other computer and a friend's computer.

It would appear this is not going to an overnight thing for everybody as there are some reports of this version of the WU engine being installed as early as June of this year.

J W Stuart: http://www.pagestart.com

Defender will update in the background as well as the update agent.  These a/v file updates are designed to install in the background (as do other a/v updates that is normal for a/v updates)  None of these however will kick a reboot.  Can you post your windowsupdate.log file on a onedrive/skydrive as I can check to see what exactly did kick a reboot - as I will state that it wasn't the windows update agent nor was it the def file that would make a system reboot.

<sigh>  and that support rep should be educated that this is expected and has occurred many times in the past.  This behavior is expected and if he uses a Windows computer, he should know that this is normal.

As long as you have windows update turned on - even if it's merely to check for updates but not to install them, this WU engine/plumbing update will occur.

If you totally turn off updates completely, the minute you manually check for updates the computer system will check as it's very first step that this WU engine is up to date and will make it update.

Again, this is expected and documented and how the WU engine works.  Every time it connects up with Microsoft update it always checks to make sure you are up to date with the 'plumbing' it needs.  If it did not do this, your system would be at risk.

This plumbing update is not impacting any programs and quite honestly I've never seen this back end update fail in any way.  It's quiet, it works, it's there to keep your system able to talk at all times to Microsoft update.