Sign in to follow this  
Followers 0
Guest

Windows Update Agent - Which version do you have?

122 posts in this topic

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

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.

Thanks for testing it on all those systems and letting me know it works for all

Edited by ricktendo64
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

BTW, changing your script to point to "7.4.7600.243" will yield "7.6.7600.243" (see KB2607070).

-X- has apparently not changed the BAT script yet. Patch Tuesday is tomorrow. Really doesn't matter for v226 vs v243, so no biggie...

Read these KB articles to better understand.

v226

v226

v243

The 'latest" v256 one (which is what this topic is about) is not yet available except via WSUS (AFAIK). And yes, they all work on XP/2K3 as well as Vista/Win7/2K8 (look at the "Applies To" in KB#). The KB943144 only refers to XP, the KB946928 refers to All, however KB2607070 only refers to Win7SP1...

MS' "scatter sense"... Clear?

edit -

@dencorso - thx for the tips... working on it. :thumbup Now only need links to 3 Cabs for x64... Do NOT want to bother with loading/restoring the VistaSP1 x64 onto my "new" Dell E521's just yet (has MCE2005 on one and other is still in pieces)... too busy with other things - this and 5 more PC's to "dump".

Edited by submix8c
0

Share this post


Link to post
Share on other sites
Patch Tuesday is tomorrow.

Patch Tuesday was last week

Edit: also check your PM I sent you the x64 cab links

Edited by ricktendo64
0

Share this post


Link to post
Share on other sites
Patch Tuesday was last week
DUHHH!
Patch Tuesday is usually the second Tuesday of each month, on which Microsoft releases security patches.
:lol:

Guess you have to wait 'till next month OR maybe -X- will change it soon OR you can change it yourself before you run it. ;)

0

Share this post


Link to post
Share on other sites

@-X-

KB2607070 contains a direct link to x86/x64 v7.6.7600.243 (the link makes it LOOK like 7.4.7600.243). Rest assured, this is the LATEST Redistributable one (aside from v256)...

Working on a CMD script (functionally the same as .BAT script) to "construct" the v256.

Edited by submix8c
0

Share this post


Link to post
Share on other sites

OH thanks for the link but I'm fine with serving 226 until 256 is released. 243 added some binaries to softwaredistribution which I did not like and anyways, WU serves up 226 to this day if you go visit it with a stock XP.

Can't wait to see the script.

0

Share this post


Link to post
Share on other sites
WU serves up 226 to this day if you go visit it with a stock XP.

Honduras, Central America and I get offered 256

2012-06-15	10:56:45:765	1212	7e8	Setup	Update NOT required for D:\WINDOWS\system32\cdm.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
2012-06-15 10:56:45:765 1212 7e8 Setup Update NOT required for D:\WINDOWS\system32\wuapi.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
2012-06-15 10:56:45:781 1212 7e8 Setup Update NOT required for D:\WINDOWS\system32\wuapi.dll.mui: target version = 7.6.7600.256, required version = 7.6.7600.256
2012-06-15 10:56:45:781 1212 7e8 Setup Update NOT required for D:\WINDOWS\system32\wuauclt.exe: target version = 7.6.7600.256, required version = 7.6.7600.256
2012-06-15 10:56:45:781 1212 7e8 Setup Update NOT required for D:\WINDOWS\system32\wuaucpl.cpl: target version = 7.6.7600.256, required version = 7.6.7600.256
2012-06-15 10:56:45:781 1212 7e8 Setup Update NOT required for D:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.6.7600.256, required version = 7.6.7600.256
2012-06-15 10:56:45:781 1212 7e8 Setup Update NOT required for D:\WINDOWS\system32\wuaueng.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
2012-06-15 10:56:45:781 1212 7e8 Setup Update NOT required for D:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.6.7600.256, required version = 7.6.7600.256
2012-06-15 10:56:45:781 1212 7e8 Setup Update NOT required for D:\WINDOWS\system32\wucltui.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
2012-06-15 10:56:45:796 1212 7e8 Setup Update NOT required for D:\WINDOWS\system32\wucltui.dll.mui: target version = 7.6.7600.256, required version = 7.6.7600.256
2012-06-15 10:56:45:796 1212 7e8 Setup Update NOT required for D:\WINDOWS\system32\wups.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
2012-06-15 10:56:45:812 1212 7e8 Setup Update NOT required for D:\WINDOWS\system32\wups2.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
2012-06-15 10:56:45:812 1212 7e8 Setup Update NOT required for D:\WINDOWS\system32\wuweb.dll: target version = 7.6.7600.256, required version = 7.6.7600.256

Edited by ricktendo64
0

Share this post


Link to post
Share on other sites

I just visited WU with a Honduran address and did not get 256 offered. Confused.

honduras.png

0

Share this post


Link to post
Share on other sites

@-X-

ricktendo64 already installed the latest and it's checking for what it already has (apparently).

Also, the "softwaredistribution" folder you see (above post, whichever one) was to get the 3 "missing" CABS, which ARE in the v226 package, but NEWER (with a different "generated" name)... Compare contents of v226 with v243 - same files, different contents(newer)...

Maybe I'M confused...

243 added some binaries to softwaredistribution
A clean install? I'll have to test that...

??

Two folders - Windows\SoftwareDistribution (the "normal" one) and this one -

 Directory of C:\WINDOWS\system32\SoftwareDistribution
08/22/2009 01:55 PM <DIR> .
08/22/2009 01:55 PM <DIR> ..
08/22/2009 01:55 PM <DIR> Setup
Directory of C:\WINDOWS\system32\SoftwareDistribution\Setup
08/22/2009 01:55 PM <DIR> .
08/22/2009 01:55 PM <DIR> ..
06/14/2012 12:13 PM <DIR> ServiceStartup
Directory of C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup
06/14/2012 12:13 PM <DIR> .
06/14/2012 12:13 PM <DIR> ..
06/14/2012 12:13 PM <DIR> wuapi.dll
06/14/2012 12:13 PM <DIR> wups.dll
06/14/2012 12:13 PM <DIR> wups2.dll
Directory of C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wuapi.dll
06/14/2012 12:13 PM <DIR> .
06/14/2012 12:13 PM <DIR> ..
06/15/2012 06:01 PM <DIR> 7.6.7600.256
Directory of C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wuapi.dll\7.6.7600.256
06/15/2012 06:01 PM <DIR> .
06/15/2012 06:01 PM <DIR> ..
06/02/2012 03:19 PM 577,048 wuapi.dll
Directory of C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wups.dll
06/14/2012 12:13 PM <DIR> .
06/14/2012 12:13 PM <DIR> ..
08/22/2009 01:55 PM <DIR> 7.2.6001.788
06/12/2012 03:22 PM <DIR> 7.6.7600.243
06/14/2012 12:13 PM <DIR> 7.6.7600.256
Directory of C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wups.dll\7.2.6001.788
08/22/2009 01:55 PM <DIR> .
08/22/2009 01:55 PM <DIR> ..
10/16/2008 02:08 PM 34,328 wups.dll
Directory of C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wups.dll\7.6.7600.243
06/12/2012 03:22 PM <DIR> .
06/12/2012 03:22 PM <DIR> ..
08/11/2011 02:36 PM 35,320 wups.dll
Directory of C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wups.dll\7.6.7600.256
06/14/2012 12:13 PM <DIR> .
06/14/2012 12:13 PM <DIR> ..
06/02/2012 03:19 PM 35,864 wups.dll
Directory of C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wups2.dll
06/14/2012 12:13 PM <DIR> .
06/14/2012 12:13 PM <DIR> ..
06/12/2012 03:22 PM <DIR> 7.6.7600.243
06/14/2012 12:13 PM <DIR> 7.6.7600.256
Directory of C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wups2.dll\7.6.7600.243
06/12/2012 03:22 PM <DIR> .
06/12/2012 03:22 PM <DIR> ..
08/11/2011 02:37 PM 44,536 wups2.dll
Directory of C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wups2.dll\7.6.7600.256
06/14/2012 12:13 PM <DIR> .
06/14/2012 12:13 PM <DIR> ..
06/02/2012 03:19 PM 45,080 wups2.dll

Note the dates... These were here WAY before (at least WUPS was already there...)

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.