• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
Sign in to follow this  
Followers 0
Guest

Windows Update Agent - Which version do you have?

122 posts in this topic

These are the cabinet names that contain the aforementioned files:

  • cdm.cab, wuapi.cab, wuapi_en.cab, wuauclt.cab, wuaucomp.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/

wuaucomp.cab gives a 404

0

Share this post


Link to post
Share on other sites

That's ok, -X-. I was mistaken to have listed it. wuaucomp.cab is not needed; in WSUS-KB2720211-x86.exe it only contains wuaucomp.cif. The file is not used by XP. :)

0

Share this post


Link to post
Share on other sites

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.

either that or MS hasn't made WUA version 7.6.7600.256 available through Windows Update yet, especially in my area.

guess we'll have to wait. I can wait patiently for an MS standalone WUA 7.6.7600.256 download rather than use third party WUA 256 installers.

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.

nope Glenn9999. WUA build 256 hasn't come through on my Vista and Seven computers either.

0

Share this post


Link to post
Share on other sites
either that or MS hasn't made WUA version 7.6.7600.256 available through Windows Update yet, especially in my area.

guess we'll have to wait. I can wait patiently for an MS standalone WUA 7.6.7600.256 download rather than use third party WUA 256 installers.

Re-read the thread. It's already a given that the "Standalone" is not available. It is, however, being rolled out via WSUS Servers (see 5eraph's posts). I'm working on "constructing" what you might called a "latest add-on" (replicating Ricktendo64's manual(?) effort via a CMD/WGET directly from MS), same as -X- is doing. I already have the ENU files in place. File Dates are June 2, 2012... Comparing to Ricktendo64's package now... (Still need to re-find the 3 CLIENT cabs apparently for Vista/Win7.)

You might call this an "exercise in obtaining the latest WU"...

@Ricktendo64 -

I did not have to edit the INF, just rename wsus3setup.inf to wusetup.inf
I don't see that in any of the CABS? From KB2720211? Also, how did you get the "self-extract" portion of the Package (hex-out the front-end?)?

@-X- (and anyone else...) Attached is my "work in progress". Feel free! ;)

edit - Attachment removed... See post#63 for the "x86 finished product".

Edited by submix8c
0

Share this post


Link to post
Share on other sites

ALL the necessary files except wusetup.exe can be found in KB2720211 (no need for wget)

@Ricktendo64 -
I did not have to edit the INF, just rename wsus3setup.inf to wusetup.inf
I don't see that in any of the CABS? From KB2720211? Also, how did you get the "self-extract" portion of the Package (hex-out the front-end?)?

wusetup.inf (and wsus3setup.cat): http://download.windowsupdate.com/v9/1/windowsupdate/b/selfupdate/WSUS3/x86/Other/wsus3setup.cab

To remake the installer I used the SFX and instructions by WildBill (7zip SFX can work as well)

Edited by ricktendo64
0

Share this post


Link to post
Share on other sites

I confirm ricktendo64's repacked installer works like clockwork on XPSP3 :yes:

Keep on the great work! :thumbup

BTW, for XPSP3, after updating the WUA to v 7.6.7600.256, all that remains to be done is updating muweb.dll to the same version by hand?

Or are there other updates necessary to also bring MU up to speed?

0

Share this post


Link to post
Share on other sites

I've got everything done (for x86) except

Missing -

WUClient-SelfUpdate-ActiveX.cab

WUClient-SelfUpdate-Aux-TopLevel.cab

WUClient-SelfUpdate-Core-TopLevel.cab

Apparently from some DISM files? (unsure)

Download link to MS SFX is gone... BUT snagging the x0->x89FF seems to get what's needed.

The same Hex-length seems like MAYBE valid for the MU-v7.6.7600.24 (it uses SFX-v6.2.29.0).

note - in Hex-editor, the THIRD "MSCF" string is the actual CAB.

Changing x2000->x6000 BEFORE the "copy /b" (i.e. AFTER the MAKECAB) will work AGAINST THE CREATED CAB. (finding "wusetup.exe"). This would be the "tricky" part in a CMD script.

CABARC is downloadable directly from MS but MAKECAB will also do LZX-21.

Will use CABARC...

@Dencorso - It appears that MUWEB.DLL is from "muweb_site.cab" and is for the ActiveX for Microsoft Update as opposed to Windows Update.

edit - OOPS! see this. It can be obtained...

Edited by submix8c
0

Share this post


Link to post
Share on other sites
I've got everything done (for x86) except

Missing -

WUClient-SelfUpdate-ActiveX.cab

WUClient-SelfUpdate-Aux-TopLevel.cab

WUClient-SelfUpdate-Core-TopLevel.cab

Apparently from some DISM files? (unsure)

Why dont you try looking in WindowsUpdate.log for the direct download links and yes, they are used with dism

Download link to MS SFX is gone... BUT snagging the x0->x89FF seems to get what's needed.

I had no idea it was this easy to retrieve the SFXCAB

BTW I updated my WUA repack with MSCF.sfx v6.3.15.0

Edited by ricktendo64
0

Share this post


Link to post
Share on other sites
Download link to MS SFX is gone... BUT snagging the x0->x89FF seems to get what's needed.

Which version?

v. 6.1.22.4 ---- x0->x93FF

v. 6.3.15.0 ---- x0->x95FF

:)

0

Share this post


Link to post
Share on other sites
BTW, for XPSP3, after updating the WUA to v 7.6.7600.256, all that remains to be done is updating muweb.dll to the same version by hand?

Or are there other updates necessary to also bring MU up to speed?

Enable Automatic Updates in Windows and enable Microsoft Update on the Windows Update website. Then run the following command to have the client update mucltui.dll, mucltui.dll.mui and muweb.dll.

wuauclt.exe /detectnow

0

Share this post


Link to post
Share on other sites
Download link to MS SFX is gone... BUT snagging the x0->x89FF seems to get what's needed.

Which version?

v. 6.1.22.4 ---- x0->x93FF

v. 6.3.15.0 ---- x0->x95FF

:)

v6.2.29.0

0

Share this post


Link to post
Share on other sites

The SFXCAB version won't really matter unless you're doing some advanced stuff like using extended conditionals or running processes before uninstalling the archive, etc. Then the newer it is, the better. For basic stuff even old versions, ex. 5.x.x.x are enough.

0

Share this post


Link to post
Share on other sites
Which version?
note - in Hex-editor, the THIRD "MSCF" string is the actual CAB.
...and everything before that is the SFX (regardless). Hmm... maybe just look for LAST one and "collect" everything preceding? :sneaky: And, no, it apparently doesn't matter which version, as stated above - as long as it's an unsigned non-IE package (apparently but unsure). Just correcting the "can't get to work" thread (can't remember which one) that WildBill originally posted "how-to" that everyone apparently didn't understand...

edit -

(No, I have no clue what the other 2 MSCF sections are - maybe single-file compressed something.XX_?) Nope... apparently just a Character String used by the SFX (any.XX_ has a single real-expanded-name inside).

Still have to find out (just got back onto this) which free hex editor will "rip" the SFX from the "official WU". The solution to the x2000->x6000 is obviously to CAB the Setup program FIRST to a known location (also will need hex-edited). Got "Extract" from the downloadable Win2k RK (an MSI inside - ugh!). Nearly complete...

@-X-, this is for you if you really want it. ;)

@all, I appreciate it all. :thumbup

(too broke to donate $ to anyone, so contribute via effort)

side note - the "package" isn't too shabby time-wise to "construct" but it's a looong CMD script. Will probably "replace" the one in prior post.

edit - Responding to next post - Wait for it! As soon as you see the "finished" CMD you'll go "OHHHHH! I see!" ;)

edit2 - DUH!!! Wildbill suggested... xvi32 (has script interface)

Edited by submix8c
0

Share this post


Link to post
Share on other sites

I don't know what you guys are doing. Way over my head.

0

Share this post


Link to post
Share on other sites

The third "MSCF", seems to always be aligned at a paragraph (= has an initial offset xxx0) and should be found after the VS_VERSION_INFO structure (in UNICODE, not ASCII). Inside that structure is the "OriginalFilename" field, which must be "SFXCAB.EXE"... so, if the script searches for "SFXCAB.EXE" in UNICODE, and then searches for "MSCF" in ASCII, the right point is always reached, whatever the version. Then it's just a matter of copying everything from offset 0 up to, but not including, the offset of that "MSCF" string, and there you are. :)

0

Share this post


Link to post
Share on other sites

Re-read the thread. It's already a given that the "Standalone" is not available. It is, however, being rolled out via WSUS Servers (see 5eraph's posts). I'm working on "constructing" what you might called a "latest add-on" (replicating Ricktendo64's manual(?) effort via a CMD/WGET directly from MS), same as -X- is doing. I already have the ENU files in place. File Dates are June 2, 2012... Comparing to Ricktendo64's package now... (Still need to re-find the 3 CLIENT cabs apparently for Vista/Win7.)

You might call this an "exercise in obtaining the latest WU"...

@Ricktendo64 -

I did not have to edit the INF, just rename wsus3setup.inf to wusetup.inf
I don't see that in any of the CABS? From KB2720211? Also, how did you get the "self-extract" portion of the Package (hex-out the front-end?)?

@-X- (and anyone else...) Attached is my "work in progress". Feel free! ;)

you should read the following threads:

http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/why-doesnt-my-windows-update-agent-update-to/283f4edf-aab6-4348-907d-984a1661e2a7?auth=1

http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/is-the-windows-update-agent-listed-to-be-updated/2c15f15b-15ae-495f-be21-834b37f2d827?auth=1

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, <EDIT> 7.4.7600.226 </EDIT> is perfectly safe assuming KB2718704 & all other updates are installed and your anti-virus application is installed & working properly.

yes, it may be rolled out via WSUS Servers BUT not everyone's getting it at the same time. that avoids the WU servers being overloaded. the KEY WORDS are "OVER TIME"

if WUA 7.6.7600.256 isn't offered to me yet, than I can wait for it. some people will get it, others won't. Until Microsoft themselves update ALL their WU servers with the latest WUA, I don't need to rush in for the latest WUA update.

Edited by erpdude8
0

Share this post


Link to post
Share on other sites

http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/why-doesnt-my-windows-update-agent-update-to/283f4edf-aab6-4348-907d-984a1661e2a7?auth=1

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, <EDIT> 7.4.7600.226 </EDIT> is perfectly safe assuming KB2718704 & all other updates are installed and your anti-virus application is installed & working properly.

That answer given at the MS forum is pure BS. I started that thread.

Sorry for hijacking your thread, -X-. :)

No problem. I think I have deduced the answer to my question...they sorta pulled the update.

Edited by -X-
0

Share this post


Link to post
Share on other sites

@erpdude8 - You should reread this thread... I quoted that exact same phrase from that exact same "Answer" thread.

@-X-

I have everything except the 3 CABS (BUT that are irrelevant to XP) built into a script. The last problem is how to get XVI32 to "chop" the CAB portion off of the original/older (v243) MS WU-file programmatically.

BTW, changing your script to point to "7.4.7600.243" will yield "7.6.7600.243" (see KB2607070). The KB949104 in question actually claims the last one is "7.4.7600.226" and KB946928 point to the "v226" as well. MS is really confusing the issue on this matter. Maybe this all has to do with the Win8 Rollout (noting the "v256" WU files appears in the "v9" download set)?

(some info/links courtesy of "chasers" 5eraph and ricktendo64)

Just to add more confusion (post#44) and last page (post#53) in particular. Also note that this and this strangely both point back to KB949104 (LinkID's from those that actually got the v256). Also here (references to WSUS rollout of v256 and the KB2720211).

Still, probably just an "exercise" in "how to download from MS and construct it". "They sorta pulled the update" may make it irrelevant.

0

Share this post


Link to post
Share on other sites

Check WindowsUpdate.log for the cab links (here are the x86)

2012-06-17	13:50:56:676	 924	d3c	Setup	Downloading setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256"
2012-06-17 13:50:56:676 924 d3c Setup Downloading setup package WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256.cab from http://download.windowsupdate.com/v9/1/windowsupdate/b/selfupdate/WSUS3/x86/Vista
2012-06-17 13:50:57:276 924 d3c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Packages\WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256\WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256.cab:
2012-06-17 13:50:57:286 924 d3c Misc Microsoft signed: Yes
2012-06-17 13:50:57:286 924 d3c Setup Downloading setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
2012-06-17 13:50:57:286 924 d3c Setup Downloading setup package WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256.cab from http://download.windowsupdate.com/v9/1/windowsupdate/b/selfupdate/WSUS3/x86/Vista
2012-06-17 13:50:58:646 924 d3c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256.cab:
2012-06-17 13:50:58:960 924 d3c Misc Microsoft signed: Yes
2012-06-17 13:50:58:960 924 d3c Setup Downloading setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
2012-06-17 13:50:58:960 924 d3c Setup Downloading setup package WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256.cab from http://download.windowsupdate.com/v9/1/windowsupdate/b/selfupdate/WSUS3/x86/Vista
2012-06-17 13:51:04:322 924 d3c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Packages\WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256\WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256.cab:
2012-06-17 13:51:04:962 924 d3c Misc Microsoft signed: Yes

Edited by ricktendo64
0

Share this post


Link to post
Share on other sites
http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/why-doesnt-my-windows-update-agent-update-to/283f4edf-aab6-4348-907d-984a1661e2a7?auth=1

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, <EDIT> 7.4.7600.226 </EDIT> is perfectly safe assuming KB2718704 & all other updates are installed and your anti-virus application is installed & working properly.

That answer given at the MS forum is pure BS. I started that thread.

Still, it sounds sensible to me. Since the files are downloadable from the Windows Update servers, I'd take them at their word... this time. It's being deployed through WSUS clients first, as submix8c points out with the last link of the next quote. They really want this sent to their corporate customers first.

MS is really confusing the issue on this matter. Maybe this all has to do with the Win8 Rollout (noting the "v256" WU files appears in the "v9" download set)?

(some info/links courtesy of "chasers" 5eraph and ricktendo64)

Just to add more confusion (post#44) and last page (post#53) in particular. Also note that this and this strangely both point back to KB949104 (LinkID's from those that actually got the v256). Also here (references to WSUS rollout of v256 and the KB2720211).

Microsoft's versioning has never made much sense to me. Most Vista files have a version of 6.0, so you'd think most Win7 files would be v7.0--they're not.

0

Share this post


Link to post
Share on other sites

A patch Tuesday uses 100 fold, 1000 fold, 10,000 fold, who knows as much bandwidth as rolling out a few cabs. This last one had a cumulative security update for IE which is quite large.

0

Share this post


Link to post
Share on other sites
The last problem is how to get XVI32 to "chop" the CAB portion off of the original/older (v243) MS WU-file programmatically.

You may use MS FILEVER (extract it with 7-zip from inside the old mpedp.exe package) to confirm the SFXCAB.EXE version, and then use the offsets we have posted some posts above, then split it using PARTCOPY.

From batch, you use a DOS file splitter, like PARTCOPY: pcopy02.zip

(courtesy of the Wayback Machine)

complementarily, for versions in which the offset is not yet known, you can

use GSAR to find occurence of "MSCF"

The 3rd occurrence, of course.

XVI32 is a good way to find the offset, too, but less easy to automate, IMHO. :yes:

P.S.: Here's a sample output from filever:

N:\INSTALL\MS_UPDXP\WUA>filever *.* /a /b /d
W32i APP ENU 6.2.29.0 shp e:\install\ms_updxp\20120611\windowsupdateagent30-x86_7_4_7600_226.exe
W32i APP ENU 6.2.29.0 shp e:\install\ms_updxp\20120611\windowsupdateagent30-x86_7_6_7600_243.exe

BTW, just tested it. For 7.6.7600.243 the command should be:

partcopy Window~1.exe 0 8A00  SFXCAB.EXE

provided that WindowsUpdateAgent30-x86.exe be in the same folder from which partcopy is run, and that there's just one file which long-name begins in "window" in the said folder, since partcopy requires the use of short-names. Of course, SFXCAB.EXE is aka MSCF.SFX.

0

Share this post


Link to post
Share on other sites

Sweet and thanks to the guys who created the convenient standalone installer. :thumbup Just installed this on Windows 2000 SP4, XP SP3 x86, XP SP2 x64, Vista SP2 and W7 SP1.

0

Share this post


Link to post
Share on other sites

I visited this site http://xdot.tk/updates.html which you posted to get all the latest updates for nLite and XP Pro SP3 and got v. 7.4.7600.226

I would guess that MS will release the latest version batch by batch and you will just have to wait until your number comes up.

It is the same version on all the other computers here.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.