
[Addon] Updates for RVM Update Pack 2.1.11 (R13: 2007-09-06)
- Kelsenellenelvian
- Moderator
- Posts: 4383
- Joined: Tue Nov 30, 2004 8:32 pm
- Location: Pocatello, ID
- Contact:
- cyberloner
- Posts: 315
- Joined: Tue Sep 20, 2005 2:13 am
- Location: http://www.cybermania.ws
- Contact:
Hey all, quick question about the order of integration. Since this pack is brand new, I'm not really sure what order to integrate. I'm using nLite 1.4 and this is the order that I'm using:
Ryan's Update Pack 2.1.11
Update 2.1.11.5 from code65535
Ryan DX 9 addon
Ryan's WGA addon
boooggy's WMP 11 tweaked
MrNxDmx IE11 1.06a Alternative
I'm just wondering if I should integrate the new 2.1.11.5 pack after all the others since it has newer updates? I believe I read in another thread that nLite will automatically choose the correct order, but I just wanted the experts' opinions before I go ahead with this.
Btw, I've been using nLite/RVM Integrator and these update packs for a while now, and never posted. Just wanted to say thanks to all the people who take the time to do this stuff. It makes my life easier. So thanks for the effort!
Ryan's Update Pack 2.1.11
Update 2.1.11.5 from code65535
Ryan DX 9 addon
Ryan's WGA addon
boooggy's WMP 11 tweaked
MrNxDmx IE11 1.06a Alternative
I'm just wondering if I should integrate the new 2.1.11.5 pack after all the others since it has newer updates? I believe I read in another thread that nLite will automatically choose the correct order, but I just wanted the experts' opinions before I go ahead with this.
Btw, I've been using nLite/RVM Integrator and these update packs for a while now, and never posted. Just wanted to say thanks to all the people who take the time to do this stuff. It makes my life easier. So thanks for the effort!
Here's an excerpt from the first post in this thread:presuhn wrote:Hey all, quick question about the order of integration.
Except in the case of IE (where Ryan's pack and my pack use IE6 files which obviously should go before IE7 files), I don't think the order matters much. When in doubt, do this pack before others.code65536 wrote:There are some add-ons (such as the IE7 add-on) that have files that replace files in this pack and thus must be placed later in the order of integration.
I am getting application event log errors regarding SecurityCenter and Userenv after installing this pack.
"The Windows Security Center Service was unable to establish event queries with WMI to monitor third party AntiVirus and Firewall."
"Windows couldn't log the RSoP (Resultant Set of Policies) session status. An attempt to connect to WMI failed. No more RSoP logging will be done for this application of policy.
"
i have tryed doing a clean install with just
Ryan's Update Pack 2.1.11
and after testing with no errors i then integrate
Update 2.1.11.5 from code65535
and get the errors.
Can someone check to see if they get the same errors after integrating this pack, or if it is something i am doing wrong.
thank you
"The Windows Security Center Service was unable to establish event queries with WMI to monitor third party AntiVirus and Firewall."
"Windows couldn't log the RSoP (Resultant Set of Policies) session status. An attempt to connect to WMI failed. No more RSoP logging will be done for this application of policy.
"
i have tryed doing a clean install with just
Ryan's Update Pack 2.1.11
and after testing with no errors i then integrate
Update 2.1.11.5 from code65535
and get the errors.
Can someone check to see if they get the same errors after integrating this pack, or if it is something i am doing wrong.
thank you
-
- Posts: 67
- Joined: Thu Jun 14, 2007 2:56 am
That sure sounds like an odd order to integrate it? But if it works for you then that's all that matters.banditnich wrote:My order of inegrations is :
- all themes, UAP, cursor and some goodies first
- Booogy WMP11
- RyanVM update pack
- code65535 Update
- IE7 addons
- and some addon like DX9, Kels runtime, etc
all in one go with nlite, never gave me a hard time

I can't reproduce your error. Fresh SP2 source + RVM 2.1.11 + 2.1.11.5 update, integrated with RVMI. No errors after install and logon. No errors after installing a virus scanner. Security Center appears to interact with the virus scanner correctly. The June 26 WMI update was in the original version of my pack (2.1.11.1), so it's been around for a while, and AFAIK, nobody else has reported this. Make sure you're working with a clean source and that you're using the RVM Integrator (nLite can produce some weird errors sometimes if I try to use certain features).jessjcee wrote:Can someone check to see if they get the same errors after integrating this pack, or if it is something i am doing wrong.
Last edited by code65536 on Thu Jul 12, 2007 4:50 pm, edited 1 time in total.
-
- Posts: 3
- Joined: Sun Jan 14, 2007 1:56 pm
I tried the component removal feature twice. Got a framedyn error once and some other error another time. Never bothered to figure out what's wrong or to try to fix it since I was just playing around. nLite's fine if I just use the basic features like driver integration, hotfixes, and unattended options, and in fact, I used to use nLite because it's "one-stop".OuTman wrote:can you give details? just curiouscode65536 wrote:nLite can produce some weird errors sometimes if I try to use certain features
Aside from those weird problems with that feature, I'm also not too fond of nLite's "footprint"--that it leaves an extra inf around, that it hacks files like syssteup.dll without me telling it to do so, and that it will modify all the text files like the hives even if no edit was needed (it's mostly cosmetic, I know, but wreaks havoc when I do a diff of two sources to make sure that the cumulative changes made were what I wanted). Yes, I'm a control freak.

Okay, this is only tangentially related, but doesn't it bother anyone else that nLite and RVMI will leave the timestamp of newly compressed files as they are? Windows Setup is dumb enough that it will set the file time of uncompressed files to whatever the timestamp of the compressed version is, which means that, for example, tcpip.sys will be dated to whenever you did the integration instead of 2006/09/26, which, needless to say, wreaks havoc in sorting through system files and comparing that to times that MSKB lists. Anyway, one of the reasons I quit using nLite was that I wrote a script to do automated integrations by calling RVMI via command line, doing driver integration my own custom way, and retouching all compressed files post-integration to what their correct timestamps are, which made nLite's "one-stop" advantage moot for me.
Last edited by code65536 on Fri Jul 13, 2007 5:58 pm, edited 1 time in total.
Ryan's packs consciously omit IIS fixes, and since this is more of an update to his pack than it is an update of Windows, I'm going to omit them as well.arabianhorse wrote:WindowsXP-KB917537-x86
WindowsXP-KB939373-x86
And since I personally don't use IIS (mostly because there is no way anyone is ever going to convince me to use that instead of Apache--even if it is a Windows version of Apache

Sorry...
Seriously, though, have you considered using a proper web server instead? (Yes, I know, IIS also does SMTP and FTP, but few use IIS for that, and FileZilla is a better FTP server--though FTP is soooooo 1990's; why haven't we all moved to SFTP by now?)
- Mavericks choice
- Posts: 273
- Joined: Wed Nov 24, 2004 3:39 am
- Location: Downunder
Agreed.code65536 wrote:Ryan's packs consciously omit IIS fixes, and since this is more of an update to his pack than it is an update of Windows, I'm going to omit them as well.arabianhorse wrote:WindowsXP-KB917537-x86
WindowsXP-KB939373-x86
And since I personally don't use IIS (mostly because there is no way anyone is ever going to convince me to use that instead of Apache--even if it is a Windows version of Apache), I have neither the desire nor the motivation to include IIS fixes.
Sorry...
Seriously, though, have you considered using a proper web server instead? (Yes, I know, IIS also does SMTP and FTP, but few use IIS for that, and FileZilla is a better FTP server--though FTP is soooooo 1990's; why haven't we all moved to SFTP by now?)
Cheers
MC.
The Man from Aus
-
- Posts: 3
- Joined: Sun Jan 14, 2007 1:56 pm
Thanks very much I appreciate your work. i respect your decision . however, i managed to add them to the pack by myself luckiliy. it was interseting to read your points and it was very useful to hear it from your perspectivecode65536 wrote:Ryan's packs consciously omit IIS fixes, and since this is more of an update to his pack than it is an update of Windows, I'm going to omit them as well.arabianhorse wrote:WindowsXP-KB917537-x86
WindowsXP-KB939373-x86
And since I personally don't use IIS (mostly because there is no way anyone is ever going to convince me to use that instead of Apache--even if it is a Windows version of Apache), I have neither the desire nor the motivation to include IIS fixes.
Sorry...
Seriously, though, have you considered using a proper web server instead? (Yes, I know, IIS also does SMTP and FTP, but few use IIS for that, and FileZilla is a better FTP server--though FTP is soooooo 1990's; why haven't we all moved to SFTP by now?)
All the best you guys. I just requested out of curiosity to find out unless you were not aware of those updates but i guess you knew it all already. your comments were satisfactory and appreciated.
Many thanks

I get
I am using IE7 MP11 and DX9 addons but checked the ms articles and i dont think they affect these files
Code: Select all
KB928595: This hotfix should be reinstalled.
KB909608: This hotfix should be reinstalled.
After a lot of testing with both packs and having the rsop errors, i have found it is something to do with the INTL.inf file in RVM 2.1.11 pack
after changing this file back to the original file from SP2, the errors seem to be gone.
so not sure whats going on and why it only seems to have problems after also integrating 2.1.11.5 update.
any thoughts??
Thank you
Jesse
Investigating it even more, it seems the new flash9d file has an impact on this error too... still trying different things at the moment, but will get back to you when i find exactly what maybe causing this error.
ok, after replacing INTL.inf back to it's original file from a clean windows xp sp2 disc and downloading a new copy of flash9 version 9.0.47, i seem to have no more problems at this time. i will try it out on a live system for a couple of days and get back to ya's if i have any further issues.
thanks
jess
after changing this file back to the original file from SP2, the errors seem to be gone.
so not sure whats going on and why it only seems to have problems after also integrating 2.1.11.5 update.
any thoughts??
Thank you
Jesse
Investigating it even more, it seems the new flash9d file has an impact on this error too... still trying different things at the moment, but will get back to you when i find exactly what maybe causing this error.
ok, after replacing INTL.inf back to it's original file from a clean windows xp sp2 disc and downloading a new copy of flash9 version 9.0.47, i seem to have no more problems at this time. i will try it out on a live system for a couple of days and get back to ya's if i have any further issues.
thanks
jess
Last edited by jessjcee on Mon Jul 16, 2007 11:50 am, edited 1 time in total.
hm, there seem to be something seriously wrong with 2.1.11
services seem to take forever to start until after a min or so. after removing code's addon pack, the same issue happens (and that happened randomly after 1-3 restarts from fresh installation)...
ok, i am gonna do more testing.. but ya, something is very wrong
services seem to take forever to start until after a min or so. after removing code's addon pack, the same issue happens (and that happened randomly after 1-3 restarts from fresh installation)...
ok, i am gonna do more testing.. but ya, something is very wrong
how comme ryans update pack inf is in here?
XP theme source patcher
patches/overwrites ure default xp visual resources
patches/overwrites ure default xp visual resources
Which services? Was this a clean, unadulterated source? What else did you integrate? How did you integrate? Etc.biatche wrote:services seem to take forever to start until after a min or so
Because replacing the INF is the only way to prevent registry entries from obsolete hotfixes from registering.bober101 wrote:how comme ryans update pack inf is in here?
yes but isint the point of ure pack to add the newer ones, when integrating with ryans pack alongside this,the 2.1.1 hotfixes get processed 1st and after ure pack updates the obsolete files,the way i see it, then the 2nd rvm inf in ure pack would get processed a 2nd time for nothing...i dunno maybe im just not seeing this the way you are.
XP theme source patcher
patches/overwrites ure default xp visual resources
patches/overwrites ure default xp visual resources
Methinks you don't understand how integration and the Windows install works. INF files are used by the Windows setup API, and as such, they are processed at install time. And as I made clear in my post, I am replacing his INF; i.e., I'm updating his INF by replacing it with a newer version.bober101 wrote:yes but isint the point of ure pack to add the newer ones, when integrating with ryans pack alongside this,the 2.1.1 hotfixes get processed 1st and after ure pack updates the obsolete files,the way i see it, then the 2nd rvm inf in ure pack would get processed a 2nd time for nothing...i dunno maybe im just not seeing this the way you are.
ok i thought,it was identical as the old one in his pack.thus why i was asking,sorry to have bothered you.i have an other question,why are you registering ure files via an exe in svcpack ?
XP theme source patcher
patches/overwrites ure default xp visual resources
patches/overwrites ure default xp visual resources
Read the thread:bober101 wrote:ok i thought,it was identical as the old one in his pack.thus why i was asking,sorry to have bothered you.i have an other question,why are you registering ure files via an exe in svcpack ?
http://www.ryanvm.net/forum/viewtopic.php?p=56060#56060
OK, ill try fill in as much details as possible later since im lazy
there are 3 things that varied in comparison to my last stable rvm setup.
1. rvm 2.1.10 vs 2.1.11
2. added in your addon pack right after integrating .11 ( but happened regardless of your pack anyway)
3.different pc - gotta test on 2 machines at least to be sure
but everything else is pretty much the same.
there are 3 things that varied in comparison to my last stable rvm setup.
1. rvm 2.1.10 vs 2.1.11
2. added in your addon pack right after integrating .11 ( but happened regardless of your pack anyway)
3.different pc - gotta test on 2 machines at least to be sure
but everything else is pretty much the same.
-
- Posts: 1131
- Joined: Wed Sep 14, 2005 11:31 am
Probably what he said earlier in the thread about this happening even without my update pack (in which case, this is really a discussion for Ryan's thread, not this thread)...newsposter wrote:and what do you mean by "( but happened regardless of your pack anyway)"???
Ryan's standard response to these sorts of posts is to instruct the user to install the previous pack (2.1.10) and manually download and install the hotfixes found in his 2.1.11 changelog and see which one's the culprit.biatche wrote:rvm 2.1.10 vs 2.1.11
As noted in some of the posts above, I have also had some issue with the 2.1.11 Update Pack. I entered a lengthy post over in the main Update Pack thread that details several scenarios under which success and failure of the pack occurred - at least for me.
Bottom line: It does appear that there is something that occured between the 2.1.10 and 2.1.11 versions that is resulting in BSOD issues during the actual Windows Setup.
Anyone's thoughts would be appreciated.
Bottom line: It does appear that there is something that occured between the 2.1.10 and 2.1.11 versions that is resulting in BSOD issues during the actual Windows Setup.
Anyone's thoughts would be appreciated.
Automation makes life easier.yumeyao wrote:wow , code65536, you're always so fast when new hotfixes are out!

Did you know that my post explaining all this wasn't all that far above yours in the thread?...the_guy wrote:Just by having a look at the changelog, it looks like you're missing KB939373 (MS07-041).
He posted in the right place (Ryan's thread)yumeyao wrote:any link please?

@jessjcee
I just got the same errors on a test install that I did last night. According to Microsoft, one of the causes of the error is a corruption of the WMI repository. This can be solved by stopping the WMI service, deleting the stuff found in %windir%\system32\wbem\repository, and restarting WMI. This will cause WMI to rebuild the repository.
Repository corruptions seem to happen randomly, and it seems that repository corruptions has been a problem for years now. I did another test install with the exact same image as before and did the install in the exact same way, and the WMI error did not occur, so at least for me, it seems to be a random thing.
Amusingly, one of the fixes in my update pack (KB933062) was designed specifically to address this problem. From the MSKB: "It is designed to reduce the probability that the repository could be corrupted by a problem on the computer." Well, I guess it didn't do a very good job of that, now did it?
Edit: Solution is here.
I just got the same errors on a test install that I did last night. According to Microsoft, one of the causes of the error is a corruption of the WMI repository. This can be solved by stopping the WMI service, deleting the stuff found in %windir%\system32\wbem\repository, and restarting WMI. This will cause WMI to rebuild the repository.
Repository corruptions seem to happen randomly, and it seems that repository corruptions has been a problem for years now. I did another test install with the exact same image as before and did the install in the exact same way, and the WMI error did not occur, so at least for me, it seems to be a random thing.
Amusingly, one of the fixes in my update pack (KB933062) was designed specifically to address this problem. From the MSKB: "It is designed to reduce the probability that the repository could be corrupted by a problem on the computer." Well, I guess it didn't do a very good job of that, now did it?

Edit: Solution is here.
Last edited by code65536 on Wed Aug 29, 2007 10:11 am, edited 1 time in total.
- dougiefresh
- Posts: 948
- Joined: Wed May 11, 2005 5:05 pm
- Location: Murfreesboro, Tennessee
- Contact:
code65536, when you say "partially updated" a particular KB, does that mean that you've only replaced files that are updated? Or that the replacement of the previous KB hotfix isn't complete? I'm asking because RyanVM's changelogs state that a particular hotfix is replaced, never "partially updated"....
If A partially updates B, then the files updated by A represent only a subset of the files updated by B. In other words, some--not all--of the files updated by B are now superseded by files in A. Please refer to the KB articles linked in the changelog for details about which files are affected by which hotfix.dougiefresh wrote:code65536, when you say "partially updated" a particular KB, does that mean that you've only replaced files that are updated? Or that the replacement of the previous KB hotfix isn't complete?
- dougiefresh
- Posts: 948
- Joined: Wed May 11, 2005 5:05 pm
- Location: Murfreesboro, Tennessee
- Contact:
-
- Posts: 288
- Joined: Mon Oct 02, 2006 6:32 am
- Location: Ottawa, Ontario, Canada
According to MS KB939273 does not replace KB927891; the KB articles also display two types/versions of msi for XP x86; KB939273 is Msi.dll (3.1.4000.4104) , KB927891 is Msi31.dll (3.1.4000.4039); both for XP 32-bit (X86).
The Msi31.dll is absent from my system after fresh install while Msi.dll is at the version stated in KB939273.
A google and MS Technet search of Msi31.dll reveals only KB927891;
http://msdn2.microsoft.com/EN-US/library/aa371185.aspx
One interesting anomoly I have noticed on two fresh installs using the RUPUpdates-2.1.11.6-Addon is the DotNet 2 runtime optimization does not run at all, the application and system logs confirm this; two days later and several reboots, the optimization routine still has not run at all; all this as it normally has done before 2.1.11.6-ie: 2.1.11.5 and prior.
So, am I missing something?
Other than this the RUPUpdates-2.1.11.6-Addon along with RyanVM's RVM 2.1.11 Update Pack using nlite 1.4b and both RougeSpear's DotNet addons- complete, install without issue.
Awesome effort and much appreciated, thankyou.
The Msi31.dll is absent from my system after fresh install while Msi.dll is at the version stated in KB939273.
A google and MS Technet search of Msi31.dll reveals only KB927891;
http://msdn2.microsoft.com/EN-US/library/aa371185.aspx
One interesting anomoly I have noticed on two fresh installs using the RUPUpdates-2.1.11.6-Addon is the DotNet 2 runtime optimization does not run at all, the application and system logs confirm this; two days later and several reboots, the optimization routine still has not run at all; all this as it normally has done before 2.1.11.6-ie: 2.1.11.5 and prior.
So, am I missing something?
Other than this the RUPUpdates-2.1.11.6-Addon along with RyanVM's RVM 2.1.11 Update Pack using nlite 1.4b and both RougeSpear's DotNet addons- complete, install without issue.
Awesome effort and much appreciated, thankyou.
-
- Posts: 288
- Joined: Mon Oct 02, 2006 6:32 am
- Location: Ottawa, Ontario, Canada
-
- Posts: 1131
- Joined: Wed Sep 14, 2005 11:31 am
That's just the MSKB being inconsistent. Ignore what what KB article says and pay attention to what is actually found within the hotfix. In *both* hotfixes, the file included is named "msi31.dll". And in *both* hotfixes, Microsoft's installation script renames the file from "msi31.dll" to "msi.dll" during the file copy operation. MSKB is inconsistent in that sometimes it lists the final filename, and sometimes, it lists an intermediate filename (and sometimes, it lists the raw delta compression part "files"; obviously an automation script gone awry).RickSteele wrote:According to MS KB939273 does not replace KB927891; the KB articles also display two types/versions of msi for XP x86; KB939273 is Msi.dll (3.1.4000.4104) , KB927891 is Msi31.dll (3.1.4000.4039); both for XP 32-bit (X86).
The Msi31.dll is absent from my system after fresh install while Msi.dll is at the version stated in KB939273.
A google and MS Technet search of Msi31.dll reveals only KB927891;
http://msdn2.microsoft.com/EN-US/library/aa371185.aspx
Oh, and the two versions listed in KB927891 correspond to the mutually exclusive GDR and QFE versions; most hotfixes only have a QFE version. In any case, I prefer and use QFE over GDR in cases where such a choice is presented (and as it so happens, Ryan's pack also uses QFE instead of GDR).
I haven't tested .NET with my pack because I try to avoid polluting my system with that junk (call me old-fashionedOne interesting anomoly I have noticed on two fresh installs using the RUPUpdates-2.1.11.6-Addon is the DotNet 2 runtime optimization does not run at all, the application and system logs confirm this; two days later and several reboots, the optimization routine still has not run at all; all this as it normally has done before 2.1.11.6-ie: 2.1.11.5 and prior.

-
- Posts: 288
- Joined: Mon Oct 02, 2006 6:32 am
- Location: Ottawa, Ontario, Canada
Microsoft posted three public updates yesterday: KB928595, KB938828, and yet another update of the root certificates. There's also a new kernel (from a non-public update). So, here's the changelog for R7:
* KB928595 - Updated to v5
* KB938828 - Replaced KB932039
* KB940322 - Replaced KB931784
* July 24 Root Certificates Update
* KB928595 - Updated to v5
* KB938828 - Replaced KB932039
* KB940322 - Replaced KB931784
* July 24 Root Certificates Update
-
- Posts: 2
- Joined: Wed Jul 04, 2007 2:20 am