[-X-]

I'm trying to pin down what is going on with MS in regards to the newest Windows Update Agent.

They released a new WUA (v 7.6.7600.256) to deal with the Flame virus a bit ago and I haven't seen it come through on any of my systems or my relatives system. I can only guess that MS pulled it.

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

Can you check your system and see if it's come through? For those less inclined peeps just navigate to System32, scroll down past the folders and click one file, press x, scroll up a bit until you see files that start with wua, click properties on one of the wua files and post what version you have. Post your OS also and if it came through when did it come through?

Also if you are on Vista I guess or Windows 7 and it has come through, can you post a screenshot of what it looks like here...

 installedupdates.png (42.26K)
Number of downloads: 33

Thanks

This post has been edited by -X-: 13 June 2012 - 08:26 AM

[Glenn9999]

I read a version of 226 on WIndows XP. I even pulled up the site and don't see it come through. My guess is that they've quit *explicitly* supporting Windows XP on this if it's coming through on Vista and Seven. Hopefully they'll at least come up with a stand-alone installer soon if it is a *security* problem.

This post has been edited by Glenn9999: 13 June 2012 - 07:51 AM

[Tripredacus]

-X-, on 13 June 2012 - 07:12 AM, said:

They released a new WUA (v 7.6.7600.256)

Well that is the XP versioning. The Windows 7 one already has a 5 digit version number as opposed to the (256) 3 in your example. My netbook doesn't seem to have it. It has v7.5.7601.17514 from January 24, 2012.... although the file date that appears in Explorer is 2010...

I don't see an update for WUA in the updates list there.

Anyways, what is the problem you are having? You left that part out of your post.

[-X-]

I'm not having a problem per se. I'm just concerned about the lack of them releasing a redistributable for unattended installations. I'm actually kinda hoping they stay with .226 for XP.

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

Quote

Notice
There is no standalone installer of the latest version of the Windows Update Agent (7.6.7600.256). The following are instructions on how to obtain version 7.4.7600.226 of the Windows Update Agent.

[tomasz86]

Isn't .243 the newest available to download?

http://download.wind...Agent30-x86.exe

[submix8c]

Here's an oddball - I found this, installed in on an XP-SP3 (the x86 one) in VPC and is seemed to work. (wuapi.dll "7.6.7600.243")

DOH! You beat me!!!

This post has been edited by submix8c: 13 June 2012 - 11:23 AM

[MagicAndre1981]

I've installed the 256 a fewdays ago. it is part of the WSUS Update which is available in the Downloadcenter.

[submix8c]

MagicAndre1981, on 13 June 2012 - 12:12 PM, said:

I've installed the 256 a fewdays ago. it is part of the WSUS Update which is available in the Downloadcenter.

WSUS 3.0 SP2 (KB972455)? Doesn't that still "install" via WSUS and not allow for "manual"/standalone? MBSA does the same (similar) type of thing when you install it...
edit - do you mean this? (more)

Google translate. Absolutely no "standalone" available. It would have to be "captured"... SOMEWHERE there must be a "direct link"...

More info.

Quote

WU Agent v7.6.7600.256 is being rolled-out over time to avoid overwhelming the update servers. Until it's offered to your computer, 7.4.7600.226 is perfectly safe assuming KB2718704 & all other updates are installed and your anti-virus application is installed & working properly.

edit - somebody fudge-built an installer...

edit - apparently 3 CABS get downloaded? A CMD can be used to install.
AND... is this just good for Vista/Windows7??? What I have FOUND appears to be just an Update of the 3 CABS... (not a complete package).

This post has been edited by submix8c: 13 June 2012 - 03:20 PM

[5eraph]

Thanks for the links, submix8c.

Capturing isn't necessary if you know how to extract the update.

This post has been edited by 5eraph: 14 June 2012 - 06:41 AM

[5eraph]

It is possible to force the Windows Update website to upgrade to v7.6.7600.256, if desired.

[submix8c]

Did you mean to include the x86 "muweb.cab" with the x64 set? For the purpose of using the x86 version of IE on an x64 OS?

Note: This doesn't include ALL of the files listed in KB949104... some appear to be missing for the non-Vista/Win7... (UNLESS the "force" variation "collects" them all...)

This post has been edited by submix8c: 14 June 2012 - 08:57 AM

[5eraph]

Yes, the x86 file is necessary for XPx64; it is installed to SysWOW64.

The directions for forcing the upgrade to r256 will not work for Vista/Win7. Newer versions of Windows seem to have better system file protection. By replacing that one key file in XP, wuweb.dll, the Windows Update website will push the rest of the files to the client for installation.

This post has been edited by 5eraph: 14 June 2012 - 09:14 AM

[submix8c]

@5eraph - Gotcha! Then (in theory) one could "construct" a full package pre-release... perhaps using the prior version's Setup Package as an example?

BTW, good further investigation!

edit - and I assume that the x86 version of WSUS update will work on an x86 as well? (you didn't mention that in instructions - only the WSUS-KB2720211-x64.exe)

I guess I should mention I'm kinda tied up with Grandkids, so I may not be totally understanding/coherent...

This post has been edited by submix8c: 14 June 2012 - 09:31 AM

[5eraph]

Thanks.

Repackaging is not my strong suit. My motivation for investigating is mainly for including the files in update packs for use witn nLite and RVMi.

[submix8c]

@5seraph - added another question

And my interest lies also in -X-'s listings (no offense, just another method of integration). It appears that with the "add-on" that he creates (just a CAB with an ENTRIES.INI and the WUA.EXE) that IN THEORY this could be done BUT one would have to obtain the REMAINDER from MS on a "live" OS and constructed on your PERSONAL computer (to keep from violating the EULA's vis-a-vis redistribution) on-the-fly (since all files are downloaded directly from the "source").

edit - WOW! Becoming a semi-hot topic! (see Ricktendo64 comment below)
One might also note the the actual older v243 Package has everything in it to install (i.e. WUSETUP.EXE/INF?). What would be "missing" is all the latest MUI files for non-English, correct (ref. the KB article)? (could be obtained directly, though, according to Languages)
edit2 - errr... the WUSETUP.EXE would have an erroneous version, BUT the INF could be modified to "fit" the Correct Version?

This post has been edited by submix8c: 14 June 2012 - 09:48 AM

[ricktendo]

submix8c, on 14 June 2012 - 09:17 AM, said:

one could "construct" a full package pre-release... perhaps using the prior version's Setup Package as an example?

Thats actually a great idea, I might do that

This post has been edited by ricktendo64: 14 June 2012 - 12:24 PM

[submix8c]

@Ricktendo64 - what's a great idea? Getting tied up BY Grandkids?

edit - see previous posts ramblings...

edit2 - OH!!!! I just looked inside the "blah-blah - rename to CAB" cab!!! DUH!!!
"I can see clearly now, the rain has gone..." (old-skool song)

This post has been edited by submix8c: 14 June 2012 - 10:01 AM

[5eraph]

You're right about WSUS-KB2720211-x64.exe, submix8c. I forgot about the x86 version. The general procedure for extraction still applies--the file "f_7d330e57.BE2E96D2_4460_4371_84DE_4148273456C7" has the same SHA1 hash in both installers (they're identical).

I won't touch EULA questions with a 10-foot pole. I'm no lawyer.

But -X-'s script could be modified to download all of the necessary files directly from Microsoft.

These are the needed files: (files ending in "_en" should have that suffix removed when installing the files)

cdm.dll, wuapi.dll, wuapi.dll.mui_en, wuau.adm, wuauclt.exe, wuaucpl.cpl, wuaucpl.cpl.mui_en, wuaueng.dll, wuaueng.dll.mui_en, wuauhelp.chm_en, wuauserv.dll, wucltui.dll, wucltui.dll.mui_en, wups.dll, wups2.dll, wuweb.dll

These are the cabinet names that contain the aforementioned files:

cdm.cab, wuapi.cab, wuapi_en.cab, wuauclt.cab, wuaucpl.cab, wuaucpl_en.cab, wuaueng.cab, wuaueng_en.cab, wuauserv.cab, wucltui.cab, wucltui_en.cab, wups.cab, wups2.cab, wuweb.cab

And this is the URL path where the aforementioned cabinets can be found:

http://download.windowsupdate.com/v9/1/windowsupdate/b/selfupdate/WSUS3/x86/Other/

Directly linking Microsoft files is prohibited on this forum. All that needs to be done for the script is to add the CAB name to be downloaded to the end of the URL path. These are the URLs that the Windows Update client uses to download the files.

This post has been edited by 5eraph: 15 June 2012 - 12:32 PM

[submix8c]

...and I would venture to say that the other LANG files could be obtained.

Appears that all you need is the latest Standalone (Extracted), replace all files for the downloaded above into Extracted, modify the INF, repack, and run the SETUP via the ENTRIES.INI. Not really sure about that, but APPEARS to work that way. This could be a "workaround" until (and IF) MS decides to release the "StandAlone". (WUSETUP in this case appears to be irrelevant per the Version? Only appears in PreFetch and "came from" the Generated Folder Name during install).

I don't want to even bother with the MU-part; I had apparently "Stepped Up To" once, then, "disabled" it (apparently that's what happened during the "Customize/Use Windows Updates Only), and used your method in a VPC to "force" Update WU, and it "collected" everything into the correct places. Afterward, I "Stepped Up to MU" and it appears that all it did was re-enable the ActiveX that already existed (v7.4.7600.226, BTW).

Side note - I had Installed (over top of the v226) v7.6.7600.243 before I pulled your "stunt"... I guess I should try (later) a Clean Install, then v2.43, then your "stunt" to confirm a few things. Won't be able to today because BUSY BEE!

edit - As far as -X- is concerned, he only does ENU anyway...

This post has been edited by submix8c: 14 June 2012 - 11:00 AM

[5eraph]

submix8c, on 14 June 2012 - 10:59 AM, said:

I don't want to even bother with the MU-part; I had apparently "Stepped Up To" once, then, "disabled" it (apparently that's what happened during the "Customize/Use Windows Updates Only), and used your method in a VPC to "force" Update WU, and it "collected" everything into the correct places. Afterward, I "Stepped Up to MU" and it appears that all it did was re-enable the ActiveX that already existed (v7.4.7600.226, BTW).

Despite the file names, they're actually used for Automatic Updates. If you have AU enabled or set to notify then the MU files will be updated to r256 if the WU files are r256.

submix8c, on 14 June 2012 - 10:59 AM, said:

Side note - I had Installed (over top of the v226) v7.6.7600.243 before I pulled your "stunt"... I guess I should try (later) a Clean Install, then v2.43, then your "stunt" to confirm a few things. Won't be able to today because BUSY BEE!

Just tried from a clean Windows install myself. It seems to work fine from Windows Update Agent v5.4.3790.5512 (the version included with XP x86 SP3).

submix8c, on 14 June 2012 - 10:59 AM, said:

...and I would venture to say that the other LANG files could be obtained.
[...]
edit - As far as -X- is concerned, he only does ENU anyway...

Other localizations can be obtained just by changing the file name suffix from _en to another two letter suffix. For example, it could be changed to _es for Spanish or _it for Italian.