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

[pen25jf]

Thanks Code, I'm sure everyone appreciates your work.

Quick question: I did a clean install with Ryan's and ur .6 pack, with WMP11, some runtimes and last IE6 (with Nlite)- not one glitch. Can I install Ryan's pack, the WMP11, exit Nlite, and then integrate your new pack? Or would that cause issues? I remember someone saying your pack needed to be updated with Ryan's at the same time.

Thanks.

[Lost Soul]

thanks code

[StarChild]

Hey Code,

You still continue to amaze me with your tenacity.
As if Lite-On firmware were not enough of a challenge, you continue to impress.
I've been watching you since your first post in these forums and true to form, you have not disappointed us.

We certainly appreciate your efforts and wish you continued success. Keep up the stellar job.
I don't see you much over at the other forum but I'm glad you have diversified your talents here.

Thanks.
Starchild (aka Nemesys)

[newsposter]

nice, many thanks!

[one7]

muchas gracias!

[code65536]

Okay, I figured out the cause of the WS5.7 WFP errors in R9: Microsoft f*cked up.

1/ There is nothing wrong with the update pack.

2/ The problem is with Microsoft's security catalog for WS5.7; it simply doesn't work. As in, if I install WS5.7 using the official installer from Microsoft on a clean vanilla XPSP2 box (no integrations, no slipstreams, doing everything as Microsoft "intended") and then subsequently run a WFP scan, the WFP errors still crop up.

In other words, until Microsoft fixes their WS5.7 security catalog (or until SP3 comes out and we all use that instead), there is no way to integrate WS5.7 without the WFP errors. It's a f*ckup on Microsoft's end of things, and there isn't any way to work around it.

Which leaves me with these options:

Option A/ Leave things as-is. Given that hardly anyone ever bothers to look at setuperr.log or manually invoke "sfc /scannow", this is an error that the vast majority of people would never even notice. And even if someone does peek at setuperr.log or run "sfc /scannow", the lack of digital signatures does not affect the function or performance of WS5.7; it's only there to make Windows File Protection happy, so these are error messages that have no effects or consequences beyond being error messages.

Option B/ Revert to WS5.6 and create a separate addon for WS5.7.
Edit: This is the option that I have decided on. WS5.6 has been restored in R10, and WS5.7 is now available as a separate download.

Option C/ Keep WS5.7 and create another addon to restore WS5.6.

[newsposter]

Upon further reflection, I vote for option C.

Because.....

It doesn't require any re-work and re-release of .9
It 'fixes' the MSFT screwup from our POV
Lets people move forward with their own image work as soon as possible,

[RogueSpear]

I wouldn't be surprised if MS reissues this before too long with a new cat file. I'd just leave things as is.

[retalion]

I vote for option B

[GasPipeJimmy]

I vote for option "C" followed VERY closely by option "B".

Finally, I want to say I really apperciate the effort you have put into this project code65536.
Thank you!

[begundal]

Upon further reflection, I vote for option C.

Because.....

It doesn't require any re-work and re-release of .9
It 'fixes' the MSFT screwup from our POV
Lets people move forward with their own image work as soon as possible,

i'll 2nd dat

[Zyx_Maiden]

I agree with newsposter on this:

It doesn't require any re-work and re-release of .9
It 'fixes' the MSFT screwup from our POV

And I think it will give you a little less work to update the pack when M$ update WS5.7 to fix the errors they made.

I wouldn't be surprised if MS reissues this before too long with a new cat file. I'd just leave things as is.

So I,ll go with the family
and Vote for the Option C (as it also include option A)

[LilSpann601]

IS anyone have problems with getting internet explorer 7 b and windows media player 11 to install and theres a couple of cpl's that didn't install and when I do qfecheck no available updates...can someone help me out

[roirraWedorehT]

I vote for A since I don't think it's that big a deal.

[code65536]

I'm going to go with option B.

The main reason is to reduce order of integration problems with IE7. If IE7 is integrated before the update pack, then the IE6 updates in the update pack will overwrite the IE7 files. If IE7 is integrated after the update pack, then IE7's version of JScript (5.7.0.5730) will overwrite the version in WS5.7 (5.7.0.16535). So if WS5.7 is included in the update pack, then we have a problem of files being clobbered no matter what order we use. But if WS5.7 is separated from the pack, then people can use the following order: update pack, IE7, WS5.7.

It should be pretty easy to restore WS5.6. And the amount of work needed to reinstate WS5.7 back into the pack will be about the same as the amount of work needed to update the current WS5.7 to a newer WS5.7 (which isn't much).

So unless anyone comes up with a really, really good reason otherwise, I think I'll do R10 using option B either tonight or some time tomorrow.

Thanks for the feedback...

[orcoxp]

Why not just put IE7 and the WS 5.7 in the pack?

*ducks*

[bbmak]

This update pack 9 is killing my initial group policy applying. During the first time OS start up, the new computer should be applied group policy from the server.

However, when i am using update pack 11.9, the new computer cannot get to the dhcp server during the first time startup. Computer cannot obtain an IP address from server. This process also kills my post command line configuration of the new os.

In order to applied the gpo, I need to restart the computer.

When i am using 11.8, it works fine.

I hope someone can look into this problem

I am always using WDS(Windows Deployment Service) to deploy new OS.

[code65536]

@bbmak

If I had to take a guess, I'd guess that it's related to KB939252. Unzip R9, delete netapi32.dll and netlogon.dll from the pack, and zip it back up; that should revert those files to the previous versions. Then try the integration/install again. If that doesn't work, then repeat the process with the other files that changed from R8->R9 until you find the culprit.

[code65536]

Changelog for R9->R10:

• Split Windows Script 5.7 from the pack
• There are no other changes from R9 to R10. Therefore, unless you wanted to remove WS5.7, there is no need to download R10 if you already have R9.

Changelog for R8->R10:

• KB921503
• KB933360 - Replaced KB931836
• KB933579 - Replaced KB930012; Updated MSXML 6
• KB936021 - Replaced KB933251; Updated MSXML 3
• KB936181 - Replaced KB927978; Updated MSXML 4
• KB937143 - Replaced KB933566
• KB938127 - Replaced KB929969
• KB938829 - Partially updated KB925902
• KB939252 - Partially updated KB924270
• KB940514 - Replaced KB935192
• KB940541 - Replaced KB918997
• Updated Malicious Software Removal Tool version signature to 1.32

Order of integration: If integrating IE7 with the RVM Integrator, you must integrate this update addon before IE7, and you must integrate Windows Script 5.7 (if you choose to; WS5.7 is optional) after IE7.

The download links are in the first post.

[runningfool87]

hey code...dumb question: is integrating WS5.7 after IE7 simply a matter of having it come later alphabetically, or do i need to start a whole new RVM session after ive integrated IE7?

[newsposter]

excellent..........

[presuhn]

Will it matter where in integration I'm using your new DX9 addon?

was gonna look like this:

wmp11
RVM 2.1.11
WGAN
DX9
.NET 2
2.1.11.10
IE 7

[code65536]

Will it matter where in integration I'm using your new DX9 addon?

No, it will not matter.

And unlike the update pack update addon, the DX9 addon is standalone and replaces the old addon.

[roirraWedorehT]

Thanks much for your work, code65536!

[dougiefresh]

I noticed that in the changelog R8->R10 that the order of intergration for WMP11 was not listed. Does this mean that the information in the first post is still valid, or can I merge WMP11, RyanVM Update Pack 2.1.11 and your add-on in one step? Thanks in advance!

EDIT: If WMP11 needs to be integrated seperately, why? (I looked for explanation in previous posts, could not find the answer.... Maybe I need to reread, I am tired....)

[code65536]

Short answer: The information in the first post is always the most accurate and up-to-date, so just do what the first post tells you to do.

Long answer: WMP11 contains some older non-WMP Windows files that happens to overwrite some of the files in KB928595. This is why WMP11 needs to be integrated before this update addon. However, the latest versions of the WMP11 slipstreamer (not the WMP11 addon) will check for this to avoid overwriting the files, so if you are using the latest version of the WMP11 slipstreamer (and by latest, I mean that this was fixed in the slipstreamer only two days ago), then you don't need to run that before this update addon. However, to avoid confusing people more than necessary with the slipstreamer vs. addon distinction, I'm just telling them to do WMP11 first. Besides, if you're using the slipstreamer, then you'll be integrating WMP11 separately anyway.

[RyanVM]

FWIW, nLite checks file versions before overwriting files in i386, so R9 should in theory have worked fine with IE7 integration in that.

[yumeyao]

thanks to brain-dead MS, it doesn't have released windows script 5.7 in other languages.

[dougiefresh]

Thanks for your answer as well as your hard work, code65536!!!

[skinnyJM]

thanks to brain-dead MS, it doesn't have released windows script 5.7 in other languages.

"This is like deja vu all over again."
- Yogi Berra


[code65536]
Thanks for the updates.

[SoKoOLz]

U've done very good job.
Cheers

[origin1net]

In some cases, the order of integration is also important! Usually, you will need to worry about this only when using this update pack with another add-on that updates built-in Microsoft components.
* If you use an IE7 add-on, the IE7 add-on must be integrated after this update pack, but before Windows Script 5.7 (if installing WS5.7).
* If you use the WMP11 add-on, the WMP11 add-on must be integrated before this update pack.
* Because nLite performs version checks on files, order of integration shouldn't be an issue with nLite, though I have not personally tested this.

I get "KB937143 - This hotfix should be reinstalled" error from qfecheck.

Code: Select all

KB937143:  This hotfix should be reinstalled.

        The following files are incorrect for this hotfix:
                C:\WINDOWS\SYSTEM32\BROWSEUI.DLL
                C:\WINDOWS\SYSTEM32\SHDOCVW.DLL
                C:\WINDOWS\SYSTEM32\SHLWAPI.DLL

#1. I've tried both RVM Integrator as well as nLite 1.4b, still no go.
#2. Tried with and without WMP11 Slipstreamer in the mix. Made no difference.
#3.Tried number of different installation orders.
example : a) RVM Update 2.1.11 + code65536's Addon --> IE7 Addon --> WS5.7 Addon
b) WMP11 Slipsteramer --> RVM Update 2.1.11 + code65536's Addon --> IE7 Addon --> WS5.7 Addon
c) RVM Update 2.1.11 + code65536's Addon --> IE7 Addon --> WS5.7 Addon --> WMP11 Slipsteramer
etc..etc..

If I leave IE7 Addon out of the mix like..
RVM Update 2.1.11 + code65536's Addon + WMP11 Slipstreamer, I don't get this KB937143 error. But then, the XP CD is not up to date without IE7.

Any ideas??

Code: Select all

Current Service Pack Level:  Service Pack 2

Hotfixes Identified:
IE7:  Current on system.
KB928090-IE7:  Current on system.
KB929969-IE7:  Current on system.
KB933566-IE7:  Current on system.
KB938127-IE7:  Current on system.
KB873339:  Current on system.
KB884575:  Current on system.
KB885836:  Current on system.
KB886677:  Current on system.
KB887472:  Current on system.
KB888111:  Current on system.
KB889016:  Current on system.
KB889320:  Current on system.
KB889673:  Current on system.
KB892489:  Current on system.
KB893008:  Current on system.
KB893756:  Current on system.
KB893803:  Current on system.
KB894395:  Current on system.
KB895961:  Current on system.
KB896256:  Current on system.
KB896344:  Current on system.
KB896358:  Current on system.
KB896423:  Current on system.
KB896428:  Current on system.
KB896626:  Current on system.
KB897338:  Current on system.
KB897663:  Current on system.
KB898461:  Current on system.
KB898543:  Current on system.
KB899271:  Current on system.
KB899591:  Current on system.
KB900485:  Current on system.
KB901017:  Current on system.
KB901190:  Current on system.
KB901214:  Current on system.
KB902149:  Current on system.
KB902845:  Current on system.
KB902853:  Current on system.
KB903250:  Current on system.
KB904412:  Current on system.
KB905414:  Current on system.
KB905749:  Current on system.
KB906216:  Current on system.
KB906569:  Current on system.
KB906866:  Current on system.
KB907865:  Current on system.
KB908519:  Current on system.
KB908531:  Current on system.
KB908536:  Current on system.
KB909441:  Current on system.
KB909520:  Current on system.
KB909608:  Current on system.
KB909667:  Current on system.
KB910437:  Current on system.
KB911280:  Current on system.
KB911562:  Current on system.
KB911927:  Current on system.
KB911990:  Current on system.
KB912024:  Current on system.
KB912461:  Current on system.
KB913296:  Current on system.
KB913580:  Current on system.
KB913808:  Current on system.
KB914388:  Current on system.
KB914440:  Current on system.
KB914463:  Current on system.
KB914841:  Current on system.
KB914906:  Current on system.
KB915377:  Current on system.
KB915378:  Current on system.
KB915865:  Current on system.
KB916595:  Current on system.
KB917140:  Current on system.
KB917275:  Current on system.
KB917730:  Current on system.
KB918118:  Current on system.
KB918334:  Current on system.
KB918439:  Current on system.
KB919007:  Current on system.
KB920213:  Current on system.
KB920342:  Current on system.
KB920670:  Current on system.
KB920683:  Current on system.
KB920685:  Current on system.
KB920872:  Current on system.
KB921401:  Current on system.
KB921411:  Current on system.
KB921503:  Current on system.
KB922120:  Current on system.
KB922668:  Current on system.
KB922819:  Current on system.
KB923154:  Current on system.
KB923191:  Current on system.
KB923414:  Current on system.
KB923845:  Current on system.
KB923980:  Current on system.
KB924270:  Current on system.
KB924667:  Current on system.
KB924941:  Current on system.
KB925066:  Current on system.
KB925528:  Current on system.
KB925623:  Current on system.
KB925720:  Current on system.
KB925876:  Current on system.
KB925902:  Current on system.
KB925922:  Current on system.
KB926239:  Current on system.
KB926255:  Current on system.
KB926436:  Current on system.
KB926646:  Current on system.
KB927544:  Current on system.
KB927779:  Current on system.
KB927802:  Current on system.
KB927880:  Current on system.
KB928255:  Current on system.
KB928595:  Current on system.
KB929123:  Current on system.
KB929280:  Current on system.
KB930178:  Current on system.
KB931192:  Current on system.
KB931261:  Current on system.
KB932168:  Current on system.
KB932590:  Current on system.
KB932597:  Current on system.
KB932662:  Current on system.
KB932716:  Current on system.
KB933062:  Current on system.
KB933215:  Current on system.
KB933360:  Current on system.
KB933811:  This hotfix should be reinstalled.

        The following files are not valid in the system catalog:
                C:\WINDOWS\SYSTEM32\JSCRIPT.DLL

KB933876:  Current on system.
KB934161:  Current on system.
KB934428:  Current on system.
KB935448:  Current on system.
KB935677:  Current on system.
KB935839:  Current on system.
KB935840:  Current on system.
KB935989:  Current on system.
KB936021:  Current on system.
KB936357:  Current on system.
KB936455:  Current on system.
KB936678:  Current on system.
KB937143:  This hotfix should be reinstalled.

        The following files are incorrect for this hotfix:
                C:\WINDOWS\SYSTEM32\BROWSEUI.DLL
                C:\WINDOWS\SYSTEM32\SHDOCVW.DLL
                C:\WINDOWS\SYSTEM32\SHLWAPI.DLL

KB937930:  Current on system.
KB938032:  Current on system.
KB938127:  Current on system.
KB938828:  Current on system.
KB938829:  Current on system.
KB939252:  Current on system.
KB939273:  Current on system.
KB939884:  Current on system.
KB940322:  Current on system.
KB940514:  Current on system.
KB940541:  Current on system.

[code65536]

If you're using MrNxDmX's IE7 addon, his addon doesn't include KB937143 yet.

[runningfool87]

he could probably use nlite to slipstream those hotfixes after hes used the rvm integrator.

[aliumalik]

code65536 can you start a thread for your non public addons pack also? I think many people will be interested

[RickSteele]

The r10 works very well, no issues, error free-used nlite 1.4b to do all slipstream/customizations-including IE7 and IE7 hotfixes.
Thanks so much

[origin1net]

Thanks, guys. Finally got it working.

WMP11 slipstramer (without WMP11 hotfix) --> RVM Update 2.1.11 + code65536's Addon (using RVM Integrator) --> WMP11 hotfixes (using nLite 1.4b) --> IE7 (using nLite 1.4b) --> IE7 hotfixes (using nLite1.4b)

It worked great.

Cheers.

[code65536]

@origin1net

Just out of curiosity, why did you have nLite do the WMP11 hotfixes instead of the WMP11 slipstreamer? Also, since it looks like you're using nLite a lot, I should note that it is be possible to integrate 2.1.11 and my update addon using nLite (though I haven't tested this in a while). And as Ryan pointed out, order of integration is really only an issue if you use the RVM Integrator as nLite will try to automatically select an appropriate "order".

[newsposter]

Although I integrate WMP11 FIRST (including hotfixes) using boooggys utility, for everything else I now use nlite exclusivly without problem.

I have to add that I use nlite as a personal choice for my workflow. The RVM Integrator works just fine and does some things better, such as proper ordering of addons) than nlite does.

[origin1net]

@origin1net

Just out of curiosity, why did you have nLite do the WMP11 hotfixes instead of the WMP11 slipstreamer?

Hi code65536
Interesting point you raised. I used nLite 1.4b for WMP11 hotfixes because if use WMP11 slipstreamer v0.82 to integrate WMP11 as well as hotfixes all together, I see none of WMP11 hotfixes listed by qfecheck for some reason. I double checked this by using WinUpdateList as well. None of them showed WMP11 hotfixes for some reason.

Using nLite 1.4b for WMP11 hotfixes, solved this. But a strange thing is that using qfecheck in cmd showed no hotfixes for WMP11. However, WinUpdateList showed WMP11 hotfixes in place.
This is just beyond me.

[code65536]

People should not rely on QFECheck or most of the other tools that list installed hotfixes. This is because they all rely on registry entries left by the hotfix installers to determine what hotfixes are present and what files were installed (and once they have the hotfix and file list, they can then check to see if the files are actually the right versions). Ryan's pack and my addon add these entries to the registry so that tools like QFECheck can enumerate the hotfixes. However, these registry entries are not necessary because what matters is that the files are updated, and these registry entries don't do much more beyond enabling the enumeration of hotfixes. The WMP11 slipstreamer takes a shortcut and omits these entries, so these hotfixes are not enumerated by QFECheck or other checkers, but the hotfixes are indeed installed. You can tell that they are installed because Windows Update, unlike other update checkers, checks for hotfixes by checking the actual files and not by relying on the registry (at least this is true for most hotfixes; there are some exceptions like TZ updates, but that's beyond the scope of this discussion), and so if WU doesn't offer the hotfix, then it's installed.

[origin1net]

Thanks for the explanation, code65536.

You can tell that they are installed because Windows Update, unlike other update checkers, checks for hotfixes by checking the actual files and not by relying on the registry

How about non-public hotfixes? By non-public, I mean hotfixes that are not offered on Windows (Microsoft) Update such as KB896256-v4, KB888111 and so on. There must be other method to verify those are installed correctly if QFECheck is not 100% reliable.

[code65536]

There must be other method to verify those are installed correctly if QFECheck is not 100% reliable.

You either check the file versions manually against what's listed in the KB article or you make sure that the proper registry entries are present for QFECheck to work (and this is why I go through the trouble of adding those registry entries even though they are not necessary).

[TechnoHunter]

on that note.. is there a tool around that would do that ? (add reg entries for hotfixes that are installed)

or is it a big ol' manual mess still?

TechnoHunter

[code65536]

on that note.. is there a tool around that would do that ? (add reg entries for hotfixes that are installed)

AFAIK, no, there is not. However, I do partially automate the process of generating the entries used in this addon.

[origin1net]

Very informative.

Thanks for the info.

[Rudi1]

Thanx for your work,I will try it!

[Mavericks choice]

@code65536

Integrated & all working fine here as expected.
Thanks.

[RogueSpear]

In some cases, the order of integration is also important! Usually, you will need to worry about this only when using this update pack with another add-on that updates built-in Microsoft components.
* If you use an IE7 add-on, the IE7 add-on must be integrated after this update pack, but before Windows Script 5.7 (if installing WS5.7).
* If you use the WMP11 add-on, the WMP11 add-on must be integrated before this update pack.

Well this seems to have fixed some issues for me. Plus I discovered something kinda cool about my program AutoImage - it was really easy to go back to my previous configurations and just shuffle the addons into the appropriate order.

[code65536]

Updated with the latest Windows/Microsoft Update (7.0.6000.381)


BTW, in case people haven't noticed, I like to do frequent small updates. It's a lot easier for me than waiting to have everything piled into a few huge updates (plus, it's easier schedule-wise to spend small trivial slices of time but more frequently than to try to find a big chunk of time needed to do a big update). As a result, people really should hold off on downloading this pack until they actually need to use it, because there's always going to be that chance that by the time you actually use it, it may have already been superseded. Plus, this would help conserve the bandwidth that RogueSpear has donated.