[Addon] Updates for RVM Update Pack 2.1.11 (R13: 2007-09-06)

[code65536]

This update addon will update the June 2007 RVM Update Pack (2.1.11), which is currently on hiatus, with the updates and hotfixes that have become available since then.

What's in this update addon?

• KB908673 - Replaced KB918005 (KB908673 is v2, dated 2007/07/20)
• KB915377 - Replaced KB899409
• KB921503
• KB923845
• KB925066 - Replaced KB903234
• KB928595 - Partially updated KB917140
• KB932716
• KB933062
• KB933215 - Replaced KB922582
• KB933360 - Replaced KB931836
• KB933579 - Updated MSXML 6
• KB933811 - Updated WS5.6 (superseded if WS5.7 is installed)
• KB935677 - Partially updated KB922668
• KB935708
• KB936021 - Replaced KB924191; Updated MSXML 3
• KB936181 - Replaced KB927978; Updated MSXML 4
• KB936455 - Partially updated KB924270
• KB936678 - Partially updated KB908519
• KB937143 - Replaced KB933566
• KB937930 - Replaced KB923232
• KB938032 - Replaced KB935214
• KB938127 - Replaced KB929969
• KB938828 - Replaced KB918033
• KB938829 - Partially updated KB925902
• KB939252 - Partially updated KB924270
• KB939273 - Replaced KB927891
• KB939884 - Replaced KB935843
• KB940322 - Replaced KB931784
• KB940514 - Replaced KB935192
• KB940541 - Replaced KB918997
• KB941037 - Replaced KB934428
• KB941077 - Replaced KB918118
• KB941598 - Partially updated KB928255
• July 24 Root Certificates Update
• Updated Flash Player to 9.0.47.0 (Security Bulletins: CVE-2007-2022, -3456, and -3457)
• Updated QFECheck to 6.2.29.0
• Updated Microsoft Update and Windows Update to 7.0.6000.381
• Stubbed the Malicious Software Removal Tool (version: 1.32).
• Cosmetic: Localized the build stamps that appear in the registry

Known issues:

• Because of an error in Microsoft's security catalog, installing Windows Script 5.7 will result in digital signature warnings. Until Microsoft fixes this problem, WS5.7 will not be included and will be available only as a separate addon. More info...
• KB933062 was publicly released by Microsoft to reduce the frequency of WMI repository corruptions. However, there have been a few scattered reports that this hotfix may actually be increasing the frequency of these random (i.e., these errors are not reproducible) corruptions during Windows setup (there do not appear to be any problems after setup, however). As of version 2.1.11.13 (R13), this update pack will run a small 1KB utility that will clean up any repository corruptions when setup completes. This should fix the problem, but if there are still reports of such problems after R13, then I may just remove KB933062. More info...

How should I integrate this update addon?

• If you are using the RVM Integrator, there are three different ways to integrate this update addon:
  • To a fresh source: As an "Addon Pack" alongside the main RVM Update Pack (this is the method that I personally use)
  • To a source that already has the RVM Update Pack: As an "Update Pack"
  • To a source that already has the RVM Update Pack: As an "Addon Pack" alongside a dummy update pack
  If you are using nLite (Important: Read this note before using nLite!), there are two different ways to integrate this update addon:
  • To a fresh source: Add both the main RVM Update Pack and this update addon to "Hotfixes, Addons and Update Packs"
  • To a source that already has the RVM Update Pack: Add this update addon to "Hotfixes, Addons and Update Packs"
  In some cases, the order of integration is also important! Usually, you will need to worry about this only when using this update addon with another addon that updates built-in Microsoft components.
  • If you use an IE7 addon, the IE7 addon must be integrated after this update addon, but before Windows Script 5.7 (if installing WS5.7).
  • If you use the WMP11 addon, the WMP11 addon should be integrated before this update addon. (however, if you are using the WMP11 slipstreamer version 0.8.1 or newer, any order should be okay)
  • Because nLite performs version checks on files, the order of integration shouldn't be an issue with nLite, although I have not personally tested this.

Why is/isn't KBnnnnnn in this update addon?

• All publicly-released (i.e., accessible via either MS Update or MS Download Center) Microsoft updates since the release of the June RVM Update Pack are included. Non-public (request-only) updates are included only if they supersede an update that already exists in the main RVM Update Pack. All other non-public updates are omitted. Finally, IIS updates (e.g., KB939373) and WMP updates (e.g., KB936782) are omitted because they are not included in the main RVM Update Pack. (You may wish to consider using the WMP11 slipstreamer to integrate WMP11 and subsequent WMP patches.)

Other notes

• My testing of this update addon extends only to integration, VPC install, QFECheck, and a cursory check for obvious errors.
• Some files (e.g., msxml4r.dll) found in the hotfix packages have a newer file timestamp, but are omitted because the file is identical to the file in the 2.1.11 base pack (despite the different timestamp on the exterior). In other words, inclusion is based on the file's hash, not on its external timestamp.
• Where applicable (e.g., IMAPIv2), COM registration is done through self-registration and not through the manual adding of registry entries.
• Anyone is free to use this update addon as a base for making a pack of their own, if they so wish.

Download

• RUPUpdates-2.1.11.13-Addon.7z: Download - Mirror
  MD5: c880dd152090031b07dfc0feb5ff4f20
  Size: 15.46 MiB
  
  WScript57-1.0.0-Addon.7z: Download - Mirror - Backup
  MD5: 6264ba1c5655f1878bb8215ee801ad0c
  Size: 0.50 MiB
  Note: Integrating Windows Script 5.7 will result in digital signature warnings in setuperr.log.
  
  (Hosting courtesy of RogueSpear)

DirectX: If you are looking for the August 2007 DirectX update, you can use Nico's addon. I have no desire to maintain a separate DirectX update addon, so my old DirectX addon was only meant to be a temporary stopgap for the time when Nico's pack was temporarily removed.

Changelog:
* 2.1.11.1: Original
* 2.1.11.2: Workaround for a restriction in the RVMI that prohibits the use of drivercab_copy for addons
* 2.1.11.3: Fixed typo in INF
* 2.1.11.4: Added 9 non-public updates that superseded existing files
* 2.1.11.5: Added 6 non-public updates that superseded existing files, updated MRT and Flash
* 2.1.11.6: Added KB935198 and KB939273 and stubbed the MRT
* 2.1.11.7: Microsoft's July 24 updates plus a new kernel (details)
* 2.1.11.8: Very minor updates: replaced KB935198 with KB939884, updated QFECheck, and recompiled the MRT stub to make it even smaller
* 2.1.11.9: Microsoft's August 14 updates (details)
* 2.1.11.10: Split off Windows Script 5.7
* 2.1.11.11: Updated Microsoft Update and Windows Update to 7.0.6000.381
* 2.1.11.12: Replaced KB934428 with KB941037, removed the MU TZ fix (no longer needed), made a minor change to the KB923845 entries
* 2.1.11.13: Added 1 public update and 3 non-public updates (details)

[yumeyao]

Great Work!
It's a hard work pointing which non-public updates supersed existing ones.

[orcoxp]

Great work!
But it seems KB928090 got back in there...I thought all the files got replaced by KB933566?

[code65536]

But it seems KB928090 got back in there...I thought all the files got replaced by KB933566?

Huh? Not sure what you're talking about. This pack doesn't touch any of the files related to either KB928090 or KB933566, and I don't see any problems with KB933566 post-integration or post-install. Are you using an IE7 addon pack? If so, I wonder if it's a problem with the order of integration, since this pack does contain one IE6-specific file (the JScript update), so it's important that it is integrated before IE7.

[banditnich]

Wow great... thanks a lot code65536

[cyberloner]

keep it coming =)

[dougiefresh]

Awesome addon pack!

[motofan]

is it better to integrate this addon instead of MrNxDmX's version? (because it contains more updates)...
and, is this the right way ot integrate - like Addon Pack?


thanks

[code65536]

is it better to integrate this addon instead of MrNxDmX's version? (because it contains more updates)...

I personally think so, but then again, I'm highly biased in this matter.

and, is this the right way ot integrate - like Addon Pack?

* When using the RVM Integrator, you must use this pack either as an Addon alongside the RVM 2.1.11 Update Pack or as an Update Pack applied to a source that already has the RVM 2.1.11 Update Pack integrated. Should work with nLite as well.

In other words, if the pack is in the Addons box, then you had better have the original RVMUP in the Update Pack box at the same time.

[yumeyao]

In other words, if the pack is in the Addons box, then you had better have the original RVMUP in the Update Pack box at the same time.

of course, if you have a source with RVM Update Pack 2.1.11 Integrated, you can leave it out.

[code65536]

of course, if you have a source with RVM Update Pack 2.1.11 Integrated, you can leave it out.

Yes, but in that case, it should be in the Update Pack box instead of the Addon box (this is because the RVMI has a restriction that limits the ability of addons from modifying driver.cab).

[motofan]

@code65536: rvm integrator cannot select your addon like a UpdatePack, only like an AddonPack...so what to do? i have already integrated RVM Update Pack 2.1.11...and waiting

[code65536]

@code65536: rvm integrator cannot select your addon like a UpdatePack, only like an AddonPack...so what to do? i have already integrated RVM Update Pack 2.1.11...and waiting

You will have to manually select it. Type *.7z into the open file dialog box. Or you could integrate it as an Addon, provided that you do the integration at the same time as the main 2.1.11 pack integration (which is how I did it). As I noted in the original post, there are two ways to do this...

[RyanVM]

code65536 - you say you based this on MrNxDmX' pack, but you missed one crucial thing that I specifically asked him to do in his:

Code: Select all

VERSION="Version 2.1.11 (MrNxDmX Modv1)"

I don't mind you doing what you're doing, but you have nothing in your work that tells someone that you're the one who made it. I have a BIG problem with that. Fix it immediately or I will lock this thread and remove the links.

[Siginet]

The reason addons aren't meant to edit driver.cab is because driver repackaging is only meant for updatepacks. Repackaging driver.cab is the process that takes about 10 mins.

Another way to easily do this is to create a blank UpdatePack with a blank entries.ini in it. Then you add this addon as an addon.

[code65536]

code65536 - you say you based this on MrNxDmX' pack, but you missed one crucial thing that I specifically asked him to do in his:

Code: Select all

VERSION="Version 2.1.11 (MrNxDmX Modv1)"

I don't mind you doing what you're doing, but you have nothing in your work that tells someone that you're the one who made it. I have a BIG problem with that. Fix it immediately or I will lock this thread and remove the links.

No, I said that this is an alternative to his. I did not base this off of his (and in fact, the first version of this pack was released a few hours before his). And since I did not base it off of his, I was not aware of the request you made in respect to the format of the version. I respect people's credit, and I would never claim credit for anything that anyone else did. And in fact, I am not big on claiming credit at all, as evidenced by the lack of any sort of tagging within this pack or even in its filename.

Edit: Oh, okay. I understand now. So it's the lack of tagging that is actually the problem. Okay, fixed. The ini/inf files inside the pack are now tagged with "C64K".

[RyanVM]

Either way, please make the change.

[RyanVM]

Also, it shouldn't surprise anybody that I obviously won't guarantee that whatever pack I release next will properly integrate over top of this one. It's not to say anything bad about code65536's work, just that there's no guarantee's that what he includes in his is what I'll include in mine.

[motofan]

ok, i set manually to UpdatePack..integrating now, so i will tell you if it is ok afterall...thx

@Siginet: how long we should wait for Integrator 1.5 to be released?

edit: it's finished...this is log of RVMI (i done this after integrating UP 2.1.11)
is it ok?

05-07-2007 19¦39¦05
Log Startup @ 19:39:05 On 05-07-2007

19:39:05 - System Running: WIN_XP Service Pack 2
19:39:05 - RVMIntegrator v1.4.3
19:39:05 - C:\Documents and Settings\Administrator\Desktop\RVM_Integrator_1.4.3.exe
19:39:49 -
19:39:49 - Source Drive = E:\WXPSP2
19:39:49 - Destination Drive = E:\WXPSP2
19:39:49 - Destination Size = 67193.81640625
19:39:49 - Working Directory = E:\WXPSP2\I386
19:39:49 - Temp Directory = E:\WXPSP2\I386\rvmtemp
19:39:49 -
19:39:49 - Starting Integration
19:39:49 -
19:39:49 - Checking Destination For OS Type.
19:39:49 - Windows XP Professional - Corporate SP2 Found
19:39:49 - Clearing any Read Only Attributes.
19:39:54 -
19:39:54 - Extracting RUPUpdates-2.1.11.4-Addon.7z
19:39:54 - MD5 Hash = dd5ad9c261599439d2d3d598f5a07d9d
19:39:55 -
19:39:55 - Gathering temp files
19:39:55 - Expanding driver.cab
19:40:29 - Compressing Files
19:40:39 - Shifting Stuff Around
19:40:39 -
19:40:40 - Analyzing 1 Entry Files
19:40:40 - Processing Updates for RyanVM Update Pack v2.1.11.4 Build Date: 2007/07/04
19:40:41 - Processing Sysoc.inf
19:40:41 - Processing svcpack.inf
19:40:41 - removing obsolete hotfixes
19:40:41 - adding ProductCatalogsToInstall
19:40:41 - Processing dosnet.inf
19:40:41 - Modifying any SP2.cab areas in dosnet.inf
19:40:42 - Editing [Files]
19:42:46 - Processing txtsetup.sif
19:42:46 - Editing [SourceDisksFiles]
19:42:46 - Modifying any SP2.cab areas in txtsetup.sif
19:42:47 - Entire .ini Processing Completed in 126 Seconds
19:42:47 - Compressing and Moving Edited Files
19:42:48 -
19:42:48 - Processing mmssetup.cab
19:42:48 - Expanding mmssetup.cab
19:42:48 - Processing entries.ini
19:42:48 - Rebuilding mmssetup.cab
19:42:50 - Rebuilding mmssetup.cab Complete.
19:42:50 -
19:42:50 - Copying Files Found In Updates for RyanVM Update Pack
19:42:50 -
19:42:50 - Calculating the amount of files to pack into driver.cab
19:43:13 - Rebuilding driver.cab
19:50:37 - Rebuilding drvindex.inf
19:50:38 - Rebuilding drvindex.inf Complete.
19:50:38 - Moving Files
19:50:38 - Cleaning Up.
19:50:38 - Replacing driver.cab
19:50:39 - Integration is at 100%, Cleaning Up
19:50:39 - Integration Completed.
19:50:39 - Total Integration Time = 650 Seconds
19:50:39 - ==================================================================================
19:50:39 -

Log Shutdown @ 19:51:00 On 05-07-2007

[Siginet]

Edited

Yes you can do it the way you just did it. That will work fine.

What I would do is make a dummy Updatepack users can use.

Dummy_UpdatePack.7z Which basically has a blank entries.ini file in it. In your addon rename entries.ini to something like entries_RUPUpdates-2.1.11.4.ini.

Then if someone wants to use your addon they can either use a real updatepack plus yours as an addon, or use the dummy updatepack and yours as an addon.

I suppose I could allow addons to trigger a recompression of driver.cab. But that probably won't make it into v1.5. v1.5 should be out soon. Trust me I want to release it. I have put so much work into it, it is pathetic. I'm hoping to have it finished this weekend so it can be released sometime next week. But I can't promise. I can assure you that a lot of work is being put into it though. Do to changes in the development of AutoIT a lot of changes had to be made in the core code of the integrator.

[code65536]

@Siginet

Huh? My entries.ini isn't named entries.ini, and so it does work in its current form as an add-on with the update pack.

@Everyone else...

I suspect my posts earlier on this topic may have been poorly worded and unnecessarily vague, so I shall attempt to clarify now:

In its current form, this pack could be integrated in either one of three ways:
1) To a fresh source: As an addon alongside the RVM Update Pack
2) To a source that already has the RVM Pack: As an update pack
3) To a source that already has the RVM Pack: As an addon alongside a dummy update pack

I've personally tested methods #1 and #2 and designed the pack with those two in mind. It didn't occur to me that #3 was also a possibility, but Siginet has since pointed that out.

Method #1 is what I use and what I had expected that most people would use.

[RyanVM]

Thanks for updating the addon, code65536

[frequenzy]

I just want to ask if it's ok to overwrite an update pack. let's say i've already integrated 2.1.10 to a CD. Could I use that CD and update it 2.1.11 or do I have to use a CD without an update?

[Siginet]

@code65536 woops sorry I must have been looking at another log when I was replying here. My bad. It would still be a good idea to provide a dummy UpdatePack as well though. For those who want to add your addon to their existing 2.1.11 disks.

[RickSteele]

@code65536

The [Release] RVM Update Pack 2.1.11 Update R4 (2.1.11.4) slipsreamed, and the install, all went perfectly-real time; absolutely no concerns.
All done with nlite 1.4b
Thanks a million

[RyanVM]

I just want to ask if it's ok to overwrite an update pack. let's say i've already integrated 2.1.10 to a CD. Could I use that CD and update it 2.1.11 or do I have to use a CD without an update?

It's been asked many times over, and yes, you can update over top of an old one. If you weren't able to, the Integrator wouldn't allow it. Since you're asking in this thread, however, I'm assuming you think that what's posted here is a full 2.1.11 pack, however. Read more carefully - it isn't. It's an update to 2.1.11, so you'd need to integrate both the regular 2.1.11 package and the addon in this thread.

[Fragbert]

How do I, if possible, ensure this addon gets integrated and installed first if I am also using MrNx's IE7 addon? When selecting addons to use in the integrator, is simply clicking the addons in a particular order make it the sequence of integration when running an XP install?

[RickSteele]

How do I, if possible, ensure this addon gets integrated and installed first if I am also using MrNx's IE7 addon? When selecting addons to use in the integrator, is simply clicking the addons in a particular order make it the sequence of integration when running an XP install?

You must integrate separate and alone first, then, reopen Integrator and slipstream MrNx's IE7 addon.
Also, ensure that all pre IE7 anything is slipsteamed before the IE7-do it last and alone.

[ilu4life]

thanks a lot....was hoping someone continues Ryan's good work

[OuTman]

the RVMI has a restriction that limits the ability of addons from modifying driver.cab

I integrate update packs and addons with nLite. Can I integrate RyanVM update pack, then your addon (not at the same time)?
It should be OK, anyone already tested?

[Master Wolfe]

Getting errors in FGCBA and the hashes don't match.

**** FGCBA 0.897 * by n7Epsilon * http://tinyurl.com/lslmm ****

*** Extracting "RUPUpdates-2.1.11.4-Addon.7z" to a temporary folder...
** Temporary Folder is: "%TEMP%\FGCBA139140305"

7-Zip 4.48 beta Copyright (c) 1999-2007 Igor Pavlov 2007-06-26

Processing archive: E:\XP Discs\RUPUpdates-2.1.11.4-Addon.7z

Extracting entries_rupup.ini
Extracting svcpack\KB915377.cat
Extracting svcpack\KB923845.cat
Extracting svcpack\KB925066.cat
Extracting svcpack\KB925528.cat
Extracting svcpack\KB932039.cat
Extracting svcpack\KB932716.cat
Extracting svcpack\KB933062.cat
Extracting svcpack\KB933215.cat
Extracting svcpack\KB933811.cat
Extracting svcpack\KB934428.cat
Extracting svcpack\KB935677.cat
Extracting svcpack\KB937930.cat
Extracting RVMUpPck.inf
Extracting explorer.exe
Extracting rootsupd.exe
Extracting bitsprx2.dll
Extracting bitsprx3.dll
Extracting bitsprx4.dll
Extracting imapi2.dll
Extracting imapi2fs.dll
Extracting jscript.dll Data Error
Extracting msxml6.dll Data Error
Extracting msxml6r.dll Data Error
Extracting ntlanman.dll Data Error
Extracting ole32.dll Data Error
Extracting qmgr.dll Data Error
Extracting qmgrprxy.dll Data Error
Extracting repdrvfs.dll Data Error
Extracting rpcss.dll Data Error
Extracting twext.dll Data Error
Extracting cdrom.sys Data Error
Extracting fltmgr.sys Data Error
Extracting sdbus.sys Data Error
Extracting sffdisk.sys Data Error
Extracting sffp_mmc.sys Data Error
Extracting sffp_sd.sys Data Error
Extracting usbehci.sys Data Error
Extracting usbohci.sys Data Error
Extracting usbport.sys Data Error
Extracting usbuhci.sys Data Error
Extracting videoprt.sys Data Error
Extracting svcpack

Sub items Errors: 21
!!- An error occured while extracting RUPUpdates-2.1.11.4-Addon.7z 7z.exe exited
with code: 2

*** Press any key to terminate . . .

[code65536]

and the hashes don't match.

If the MD5 hash doesn't match what I have in my post, then you have a corrupted/incomplete download. Try downloading it again.

[Master Wolfe]

and the hashes don't match.

If the MD5 hash doesn't match what I have in my post, then you have a corrupted/incomplete download. Try downloading it again.

That's about the fourth time over the last 2 days I've done so. Not using a download accelerator or any such. No biggy though, using mrdmx's version instead.

[Mavericks choice]

thanks a lot....was hoping someone continues Ryan's good work

Hey listen the man has not passed on, so lets not talk that way...

[Siginet]

I know Ryan appreciates addons like these. Especially in times like now when life is very busy for him. code65536 and MrNxDmX are doing a great job. Ryan is the master of UpdatePacks and very difficult switchless installers. He never ceases to amaze us. But we all need help sometimes.

So thanks guys!

[Master Wolfe]

I know Ryan appreciates addons like these. Especially in times like now when life is very busy for him. code65536 and MrNxDmX are doing a great job. Ryan is the master of UpdatePacks and very difficult switchless installers. He never ceases to amaze us. But we all need help sometimes.

So thanks guys!

Agreed!

[RickSteele]

code65536; small update to R4

KB930012 - The update for MSXML 6.0 SP1 did not get slipstreamed; I run 0_ROGUESPEARSRUNTIMESCF.EXE at T13 and 010_RogueSpearsRuntimesPart2.exe at GUI RunOnce, along with RyanVM's 2.1.11 of course.

[code65536]

That's about the fourth time over the last 2 days I've done so. Not using a download accelerator or any such. No biggy though, using mrdmx's version instead.

Don't know what to say... I've tried downloading the files, and the files that I get from both links check out fine. Sometimes, a web browser will store a corrupted download in its cache and then fetch the file from cache for subsequent downloads, which may lead to repeated download failures...

KB930012 - The update for MSXML 6.0 SP1 did not get slipstreamed; I run 0_ROGUESPEARSRUNTIMESCF.EXE at T13 and 010_RogueSpearsRuntimesPart2.exe at GUI RunOnce, along with RyanVM's 2.1.11 of course.

Check the version of system32\msxml6.dll. It should be build 1132. This is one of those updates that won't show up on QFECheck, but it's still there.

[Master Wolfe]

Weird, indeed. I was just now able to download it, from both servers and with both IE 7 and Firefox 2.0.0.4, but sure as heck couldn't before. Anyhow, thanks!

[RickSteele]

code65536

I ran the KB930012 msi extracted with WinRAR and it stated I had a "lower version of MSXML 6........." (6.0SP1); funny though, MU did not single the update as not installed.......

[RyanVM]

I'm totally taking MSXML6 out of my next release. It's too much of a headache to deal with.

[RickSteele]

I'm totally taking MSXML6 out of my next release. It's too much of a headache to deal with.

Nooooooo..........I have never had any concerns with your addons...all the DotNets etc. 6.0SP1 is installed, just code65536's update pack addon's MSXML KB, but, it did everything else flawlessly...so we just have to install the MSXML KB manually; no biggy.

[code65536]

Just did a test install with MSXML6... I didn't a "lower version of MSXML 6" message when I tried to run the installer. Maybe I missed the message? I haven't noticed any issues with build 1132 of MSXML 6 (aside from the usual MSXML 6 things, of course).

MU won't list this update because it's not a critical update. It's also not a core Windows component. It's an optional component that was installed for the sake of convenience because there are other apps that depend on it. As for Ryan's decision to excise it from future version, there are other issues with MSXML 6 (with the original RVM packs) with things like installing Visual Studio. I'm guessing that the problem mostly has to do with Microsoft's use of MSI.

(And doing a registry diff right before and after installing the MSI atop an XP install with 1132 of MSXML 6 integrated yields only MSI-related entries, which suggests that MSXML itself was integrated just fine--just that MSI is, well, MSI)

[newsposter]

what's the definitive version of MSXML and can lower/older versions be deleted??

[code65536]

what's the definitive version of MSXML and can lower/older versions be deleted??

There isn't one. Just like there isn't one definitive version of .NET. In other words, MSXML4 doesn't supersede 3, which doesn't supersede 2, etc. My computer, for example, has 2, 3, 4, and 6 all sitting alongside each other. Some apps will use 3, some 6, etc.

[code65536]

It's a quiet July. Very quiet, in fact. According to Microsoft's summary of the July updates, there are no security updates for XP this month (well, except for an update for IIS 5.1, but not really an XP update and since, AFAIK, Ryan doesn't update IIS files, neither will I).

Adobe, however, released a new Flash player, r47 (9.0.47.0) today that addresses three security bulletins (CVE-2007-2022, -3456, and -3457). This is not the same as the r60 version that's still in beta testing.

So there's really not much to update. A new MRT, the Flash security fix, and some non-public hotfixes (ones that updated files already in Ryan's pack, of course).

Changelog:
* KB928595 - Partially updated KB917140
* KB933251 - Replaced KB924191
* KB935989 - Partially updated KB928255
* KB936455 - Partially updated KB924270
* KB936678 - Partially updated KB908519
* KB938032 - Replaced KB935214
* Updated Malicious Software Removal Tool to version 1.31.
* Updated Flash Player to 9.0.47.0
* Localized the build stamps that appear in the registry (**)

(**) Okay, this is totally a cosmetic thing. Basically, the build timestamps of slipstreamed files that are stored in the registry will appear in your local time instead of US Eastern Time. What effect will this have? AFAIK, absolutely nothing beyond cosmetic consistency. But I had the code for it, so why the heck not? This is what the "tsreg" that I added does (it corrects the timestamps at install time). You can remove it if you want.

I'll add the download links to the first post.

[RickSteele]

code65536,

awesome, thanks much!

[Kelsenellenelvian]

YOU SON OF A *&%#@

I just and I mean JUST built a DVD for my lappy and you release a Update!!!

HOW DARE YOU!!!!

LOL Hey great work I like the upate\addon job you're doing here!!!!

I was just kidding around you just came an hour late with your addon dang it.

[waleed_wwn]

Excelent code65536 Again

Very Speed Update addon , thanks too much.

Sure I will try today and Feedback

[banditnich]

Kewl... Will make a new one from scratch tonight with the new addons...
Thanks a bunch code65536