[5eraph]

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

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 forgot to mention: ricktendo64 repacked the installers at your suggestion.

[ricktendo]

I did not have to edit the INF, just rename wsus3setup.inf to wusetup.inf

[submix8c]

Congrats!
-X- what do you think?

I think the "system" has been beat!

edit - Absolutely NO time to test, but from all appearances it looks good! Got a Sound Engineer gig in about 3 hrs (two groups). 90-Proof Twang and Ryan Broshear - "New" Country + originals (up-and-coming groups out of Oxford, OH).

This post has been edited by submix8c: 14 June 2012 - 12:42 PM

[-X-]

I think I'm getting a headache. I'm a noob!

[MagicAndre1981]

yes, the CABs only work for Vista/7. Sorry, I'm no longer using XP for years now.

[-X-]

5eraph, on 14 June 2012 - 10:22 AM, said:

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

[5eraph]

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.

[erpdude8]

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

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.

Glenn9999, on 13 June 2012 - 07:46 AM, said:

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.

[submix8c]

erpdude8, on 15 June 2012 - 12:31 PM, said:

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 -

Quote

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".

This post has been edited by submix8c: 19 June 2012 - 04:36 PM

[ricktendo]

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

submix8c, on 15 June 2012 - 01:14 PM, said:

@Ricktendo64 -

Quote

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.wind.../wsus3setup.cab

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

This post has been edited by ricktendo64: 15 June 2012 - 01:59 PM

[dencorso]

I confirm ricktendo64's repacked installer works like clockwork on XPSP3
Keep on the great work!

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?

[submix8c]

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...

This post has been edited by submix8c: 15 June 2012 - 04:39 PM

[ricktendo]

submix8c, on 15 June 2012 - 03:55 PM, said:

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

submix8c, on 15 June 2012 - 03:55 PM, said:

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

This post has been edited by ricktendo64: 15 June 2012 - 09:41 PM

[dencorso]

submix8c, on 15 June 2012 - 03:55 PM, said:

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

[5eraph]

dencorso, on 15 June 2012 - 03:13 PM, said:

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

[ricktendo]

dencorso, on 16 June 2012 - 12:35 AM, said:

submix8c, on 15 June 2012 - 03:55 PM, said:

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

[tomasz86]

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.

[submix8c]

dencorso, on 16 June 2012 - 12:35 AM, said:

Which version?

submix8c, on 15 June 2012 - 03:55 PM, said:

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? 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.
(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)

This post has been edited by submix8c: 16 June 2012 - 12:04 PM

[-X-]

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

[5eraph]

Sorry for hijacking your thread, -X-.