5eraph's post-SP2 Update Pack v2017-06_2

vodacuza · Post by **vodacuza** » Sun Sep 19, 2010 10:44 am

thankyou, I needed the advice of someone dedicated and skillfull into that matter of xp 64...as I became interested in it too.

vodacuza · Post by **vodacuza** » Mon Sep 20, 2010 10:26 am

there was something wrong in my slipstreaming las night, could be because for about 4 repetitive times wmp11 direct integration failed and although the wmp11slipstreamer reported that the source was not corrupted .. I still have doubts always when a process fails and does not go smooth all the way...

After those failings I had to renounce to some updates and keep only these:

windowsmedia11-kb928788-x64-intl.exe
windowsmedia11-kb929399-v2-x64-intl.exe
windowsmedia11-kb929773-x64-intl.exe
windowsmedia11-kb932390-x64-intl.exe
windowsmedia11-kb933547-x64-intl.exe
windowsmedia11-kb935551-x64-intl.exe
windowsmedia11-kb935552-x64-intl.exe
windowsmedia11-kb939209-x64-intl.exe
WindowsMedia11-KB939683-x64-ENU.exe
WindowsMedia11-KB941569-x64-ENU.exe
windowsmedia11-kb944882-x64-intl.exe
windowsmedia11-kb954067-x64-intl.exe
WindowsMedia11-KB954154-x64-ENU.exe
WindowsMedia11-KB954155-x64-ENU.exe
WindowsMedia11-KB973540-x64-ENU.exe
WindowsMedia11-KB978695-x64-ENU.exe

When everything was complete and windows first opened, there was another error... MU did not work, also any attempt to use "Check for updates " both in IE8 and WMP11 was generating an unknown error and retained me from doing that check...
I mention that I use Virtual Box last version ... to install xp sp2 64 bits + current post sp2 pack on a 32 bits platform ... I say it because having no experience with 64.. I do not know the interactions between 32 and 64 when the first is the platform and the second the virtual machine...

So , I'll integrate one by one... after each important step , such as integrating this post sp2 pack, integrating IE8 pack, wmp11, 5MSsigned themes 6.1.2 and so on... I'll do the iso image and see how it is working, if everything goes well, continue integrating the next pack and so on

vodacuza · Post by **vodacuza** » Mon Sep 20, 2010 12:30 pm

5eraph help

After pack integration the MU link from Start Menu...still unavailable...
but I managed to enter the MU through another address...

MU detected 69 high priority updates and
5 optional software updates, 2 optional software updates

the weirdest thing was that meanwhile was installing this slipstreamed 64bits windows... reached the point when it said: Setup will complete in approximately 10 minutes... well there was a problem... it kept struggling there...it was more than obvious... the mouse arrow and the sound (I was watching the online TV into the host where the virtual guest was installing) were altered in both stations, there were strange crackling sounds and the mouse almost not moving on the display surface.. and it stood in that point for a long time...

at the end after opening windows session (by the way it bypassed OOBE by default) MU couldn't be accessed except by another link manually submited, and finally detected 69 high priority updates... I 've checked only one, I mean the first showed there... KB 979309 .. it is of course one claimed to be into the pack

can you tell what was wrong ?

thanx ...

Post by **5eraph** » Mon Sep 20, 2010 12:52 pm

Updated to 2010-09_2. Please read the Changelog for full details.

I haven't seen anything like that here, vodacuza. Are you using RVMi or nLite? What else are you adding to your source?

yumeyao · Post by **yumeyao** » Mon Sep 20, 2010 12:58 pm

Well, I found that WMP11 Slipstream really annoying to compress the driver.cab on xp2k3x64, taking a very long time doing a useless job. I'll probablly help make an addon for x64.

- EDIT -
Starting with my WMP11 addon 3.3.3, it's really a sweet attempting because x64 WMP11 only adds some native x64 files, all syswow files are exactly same as x86 ones.

vodacuza · Post by **vodacuza** » Mon Sep 20, 2010 4:53 pm

I used native:
"en_win_xp_pro_x64_with_sp2_vl_X13-41611.iso" (SHA1 - verified)

to integrate:
"5er_UpdatePack_XPx64SP2_2010-09_1.7z"

with:
"RVM_Integrator_1.6.1b2.1.exe"

then went to nlite cause I like to use the "Hide Pages" option with all the detailes such as : serial number and WORKGROUP workgroup already supplied in it...

and minor legit adjustments that nlite itself allows, borrowed from X86 nlite ini-es ...

no other packs, nor drivers used especially after the first failure I've encountered...
there is something in the process of slipstreaming the post sp2 x64 pack in my environment...

yumeyao thanks for considering the x64 project... these days I was dreaming to have a similar addon for wmp11 x64 like yours for x86...but yet not registering enough personal failures... to give me the courage proposing you that

5eraph do not bother it must be my mistake somehow, I trust people saying they got this working well... I'll post the remedy, the solution to my problem, soon

yumeyao · Post by **yumeyao** » Tue Sep 21, 2010 5:20 am

I have to admit that x64 is far more difficult than I imagined. I know about that wmp on xp/2k3 is nearly all x86 components, that's why I toughout it was not hard. But I was wrong. There are many things new to me - I should consider replacing nearly all %11% to %16425%. That's only the start.. Ok. I think I'll have a deep look into it... before I could make an x64 wmp11 addon.

Post by **5eraph** » Tue Sep 21, 2010 6:01 am

I appreciate the effort, yumeyao. IE8 took me a while to do. WMP11 seems at least twice as hard to me with several installers rolled into one.

yumeyao · Post by **yumeyao** » Tue Sep 21, 2010 9:20 am

It's not the point that several installers that blocks me, but really the x64 and x86 files/registries. I decide that there must be some(or even many) "official" mistakes that M$ makes. I'll give you 2 easy shots:

1. the wmdm.inf(i386\wwmdm.inf)
The [DelayReg.OCX] section in this file is totally wrong. These files are x86 files but M$ gives them a registration of "%11%\regsvr32.exe /s %11%\*.dll", which is definatively wrong. The T-13 Registry shows too that the %11% are translated to C:\Windows\System32 - so these files dont even exist in that system32 - they're in syswow64.

2. Portable device icon
I have my mobilephone attached to the VM, then I found the device icon is missing from My Computer. So I tried explorer.exe x86 version, then the icon is there.

I'm still not sure whether it's because a file(dll) missing, or a group of registry entries missing, but I'll look into it.

So I decide to make the addon with the knowledge I own despite how M$ makes it:
every dll is registered in its own architecture(x64/x86), every registry entry that is not exclusively used by wmp is duplicated in x86 and x64 forms.

-- EDIT --
After installing wmp11, the Audio Device Icon is fine. Glad that M$ didn't make fault again in their wmp11 package.

-- EDIT2 --
The Audio Device Icon is missing in *32 explorer.exe instead..

Post by **5eraph** » Sat Oct 16, 2010 3:06 am

Updated to 2010-10_1. Please read the Changelog for full details.

Nethan · Post by **Nethan** » Sun Oct 17, 2010 2:52 pm

I have a question about this line :

High priority update KB979687 replaced high priority update KB923561 and additional update KB961180.

The 923561 update includes also four files called Mswrd8.wpc & Sysmain.sdb with for each their W declinaisons. The 979687 don't include them.

I don't know if they are useful or not. Has 979687 really replaced the 923561 ?

Post by **5eraph** » Sun Oct 17, 2010 3:30 pm

KB979867 replaces the final remaining files from KB923561. Here's the complete file list from KB923561 along with the current list of relevant packages:

w03a3409.dll, ww03a3409.dll - currently replaced by KB2345886 and KB2360131, but are not counted as critical files.
SysMain.sdb, wSysMain.sdb - replaced by KB955759 in 2009-12_1.
MSWrd8.wpc, wMSWrd8.wpc - replaced by KB2259922 in 2010-09_1.
WordPad.exe, wWordPad.exe - replaced by KB979687 in 2010-10_1.

It is too tedious for me to track each file in this way for the changelog, but each file in each package is flagged with an OBSOLETE comment in 5erUpPck.inf for me to keep track informally. For the changelog it is far easier to list only the final update that removes the need for a superseded update.

If you have similar questions regarding other updates in the pack, please feel free to ask.

Nethan · Post by **Nethan** » Tue Oct 19, 2010 6:16 pm

Thanks for your response

I don't have similar questions for the moment

Keefa · Post by **Keefa** » Thu Oct 21, 2010 4:33 am

As usual, thank you so very much for both the Windows update pack and the IE8 update pack!

Post by **5eraph** » Thu Oct 21, 2010 6:33 am

You're welcome.

markfuture · Post by **markfuture** » Fri Oct 22, 2010 2:00 pm

Many, many THANKS !!!!! I have been searching for this a long time.

mark strelecki · Post by **mark strelecki** » Fri Oct 22, 2010 5:07 pm

5eraph -

Thank You!

The Acer Core2Duo laptop is singing your praises and working like a TOP!

Soon, a Core i7-920 desktop will be doing the same.

ONLY YOU help secure the future for XP64, and I am grateful for your talent, kindness and generosity, now and always.

Many thanks from your friend in Atlanta, GA.

MARK STRELECKI

Post by **5eraph** » Wed Oct 27, 2010 8:14 pm

You're welcome.

Updated to 2010-10_2. Please read the Changelog for full details.

Post by **5eraph** » Wed Nov 10, 2010 10:05 pm

Updated to 2010-11_1. Please read the Changelog for full details.

Keefa · Post by **Keefa** » Wed Nov 17, 2010 7:12 am

It's the time of the month when I pop in and say "Thank you, 5eraph!".

The packs will go to good use.

Post by **5eraph** » Wed Nov 17, 2010 7:17 am

Your appreciation is appreciated.

Post by **5eraph** » Fri Nov 26, 2010 2:38 am

Updated to 2010-11_2. Please read the Changelog for full details.

maur0 · Post by **maur0** » Fri Dec 03, 2010 7:11 am

hi im using last addon 02_11 and missing 1 update
KB981332

are plan to create addon alll frameworks 2.0 3.0 and 4.0 for xp x64 include updates?

Post by **5eraph** » Fri Dec 03, 2010 10:37 pm

KB981332 should only be needed with IE8. It's included in the updated addon.

Unfortunately, I don't plan on making a .NET addon. It seems far too complicated for something I would rarely if ever use.

Post by **5eraph** » Wed Dec 15, 2010 7:23 pm

Updated to 2010-12_1. Please read the Changelog for full details.

Keefa · Post by **Keefa** » Thu Dec 16, 2010 10:18 am

An early Christmas present from 5eraph? Excellent.

Thanks for all of the update packs over the year 2010. Merry Christmas and a happy new year!

User · Post by **User** » Thu Dec 16, 2010 10:26 am

I second that.

I know the December pack is available now so most people will forget about November, but (and I don't know what causes this) when I integrated the November pack "5er_UpdatePack_XPx64SP2_2010-11_2.7z" then installed XP x64 (all I added after the addon pack was a WINNT.SIF to AMD64 to make it unattended for faster testing) I noticed the Ethernet Controller driver wasn't installed. I then just installed a clean XP x64 SP2 with nothing added at all except the WINNT.SIF file and it was fine, the driver was installed.

The reason?

The service "Windows Management Instrumentation" seemed to get removed when integrating the November pack. This had a knock on effect making the drivers not install.

Anyone else had the WMI service "vanish" when using nLite to integrate the November pack? Check services.msc to see, I don't know how a service can get removed but it does. All I did in nLite was simply integrate the November addon, no tweaks, no options changed, nothing removed.

I am now integrating the December pack, I will report back.

maybe its because I am doing this on XP x86? Although that seems unlikely.

User · Post by **User** » Thu Dec 16, 2010 11:17 am

Yes, integrating this December pack makes the service "Windows Management Instrumentation" disappear out of the services list and driver installers pop up messages like...

This software requires the Windows Management Instrumentation service. This service is not currently running. Please start the service and then restart the installation.

I cannot start the service because it is not there in the list in services.msc!

It. Has. Vanished.

Post by **5eraph** » Thu Dec 16, 2010 2:32 pm

You're welcome.

The service "Windows Management Instrumentation" exists for me when running services.msc in VirtualBox with the latest pack integrated with nLite 1.4.9.1 under XPx64. IE8 and WMP11 are also integrated. I'll give it a try under XPx86 in a few.

To test further here, User, I'll need your "Last Session.ini" and perhaps your WinNT.sif (without your key or personal info, just replace with Xs).

User · Post by **User** » Thu Dec 16, 2010 3:46 pm

OK but I can try without the WINNT.SIF myself and let you know.

Last Session.ini just has the update pack addon...

Code: Select all

[Main]
Env = 1.4.9.1 - 2.0.50727.42.Microsoft Windows NT 5.1.2600 Service Pack 3
Target = Windows XP Professional x64 Edition SP2 - 5.2.3790.3959 - English (United States)

[Tasks]
Hotfixes and Update Packs

[Components]
;# Compatibility #

[KeepFiles]
msconfig.exe

[RemoveFiles]
clock.avi
yahoo.bmp
swtchbrd.bmp

[Options]
ProfilesDir = "%SystemDrive%\Documents and Settings"
TargetPath = "WINDOWS"
temp_dir = %USERPROFILE%\Local Settings\Temp

[Patches]

[Services2]

[Tweaks]

[Unattended]
ComputerType = Automatic
MaximumDataStorePercentOfDisk = 12
RestorePointLife = 30
DesktopTheme = Default||
AutoUDay = 5
AutoUHour = 15
ProgFilesPath = "\Program Files"

[NetAdapter1]
connname = ""
macaddress = ""
ipaddress = "192.168.0.1"
subnetmask = "255.255.255.0"
defaultgateway = ""
dnsserver1 = ""
dnsserver2 = ""
winsserver = ""
netbiossetting = "0"
ipxnetworknumber = "00000000"
ipxnetworkframetype = "0xFF"

[GuiRunOnce]

[Drivers]

[Hotfixes]
D:\ADDONS\XP\x64\5er_UpdatePack_XPx64SP2_2010-12_1.7z

User · Post by **User** » Thu Dec 16, 2010 5:25 pm

Sorry man its fine without the WINNT.SIF

WMI is there now I removed WINNT.SIF

I guess using the x86 WINNT.SIF does that, be warned, anyone, everyone.

Well it is a documented bug by Nuhi here:

Code: Select all

http://www.msfn.org/board/topic/120885-setting-iis-smtpon-in-winntsif-makes-the-wmi-service-disappear/

So the WMI service vanishes if:

- you run the XP x64 through nLite
- then use a WINNT.SIF to make it unattended

Maybe the WINNT.SIF is fully useless and cannot even have the basics, I have not dug deeper yet.

Maybe if I use Ryan's integrator (avoiding nLite) it might work, its an idea.

I know I did try the clean SP2 with WINNT.SIF and had no problem. It must be caused by nLite.

This bug of course has nothing to do with this addon which works perfectly.

Post by **5eraph** » Thu Dec 16, 2010 9:38 pm

I'm glad you got it sorted. I also drop in my own WinNT.sif. These are the components I use to test:

Code: Select all

[Components]
    iis_asp="On"
    iis_common="On"
    iis_ftp="On"
    iis_inetmgr="On"
    iis_internetdataconnector="On"
    iis_nntp="On"
    iis_serversideincludes="On"
    iis_webdav="On"
    iis_www="On"
    inetprint="On"

sathanas65 · Post by **sathanas65** » Mon Dec 20, 2010 12:42 pm

Thanks for this. I notice after using just this and IE8 add on, when I install in VMware, I am unable to access Windows Updates. I use WPA and WGA cracks that are okay for X64. It never says I am not genuine, just throws me an error message:

The website has encountered a problem and cannot display the page you are trying to view. The options provided below might help you solve the problem. [Error number: 0x80004005]
For self-help options:

Frequently Asked Questions

Find Solutions

Windows Update Newsgroup
For assisted support options:

Microsoft Online Assisted Support (no-cost for Windows Update issues)

The date and time are correct. Not sure if this is due to crack or what, but I'm not requiring an activation crack, just for testing. This is being made for someone with license. Thanks.

Post by **5eraph** » Mon Dec 20, 2010 3:36 pm

Try without the cracks. There should be no WGA crack for XPx64 because WGA has not been implemented for XPx64 by Microsoft; this could be your problem.

Beyond that, I shouldn't support cracks here.

sathanas65 · Post by **sathanas65** » Mon Dec 20, 2010 8:05 pm

Thanks. I will try. Personally, I hate XP 64.I think it is inferior OS. Apparently most people agree since there is so little support for it. Can't even get driver packs. But I need to try to get this disk together for a PC tech to do reinstalls with on licensed machines.

sathanas65 · Post by **sathanas65** » Mon Dec 20, 2010 9:14 pm

Yup, it was the crack. Problem solved, thanks so much.

Post by **5eraph** » Mon Dec 20, 2010 11:26 pm

You're welcome.

I respect your opinion, but I don't agree with it.

GregFL · Post by **GregFL** » Fri Dec 24, 2010 2:13 am

5eraph,

I appreciate the work you do on this XPx64 Update Pack, and it still shocks me when I have to install a non-updated (and modified) disk just how much these things save in labor. I've downloaded several over the past couple of years. It shocks me even more when I have to use Win7, however - the wasted screen space, the dummified interface... Ah, well, to each his own.

I have noticed, however, that as time goes by the creators of some of the Update Packs lose interest and the packs languish. One example of this would be the Server 2003 pack from Ryan. OP maintains one but it contains items we don't want or need. So I painstakingly downloaded 101 QFEs + 4 updates from MS only to find that DXUPAC expects components we don't want. :-\

I've looked and looked for a tool or something to assist in creating an Update Pack of my own, but to no avail. And manually creating the files necessary is obviously prohibitive. What am I missing here...?

Thanks again!
Greg

Post by **5eraph** » Sat Dec 25, 2010 6:42 pm

I don't know exactly how DXUPAC works, so I can't advise on its use.

It's not terribly difficult to create an update pack, but it can be tedious. I learned by looking into Ryan's and Xable's update packs and searched for similarities between them. All update packs have a main INF which contains the registry entries each update installs, and an Entries.ini file for RVMi and nLite to use. All other files are extracted from update packages downloaded from Microsoft.

That should be enough basic information to get you started. If you have more specific questions, I'd be happy to answer them.

GregFL · Post by **GregFL** » Mon Dec 27, 2010 4:25 am

Wow, thanks for the quick response - and on Christmas, no less.

DXUPAC is a scripted pack generator, unfortunately hard coded to include managerial tools, .NET, and other such thing I'd rather apply separately or not at all. And in compiled form, impossible to alter the script.

I'm somewhat familiar with INF files, enough so to have added modern era drivers for aging hardware such as CL Live! and LSI SCSI cards, plus Microtek E3 scanners to XPx64/SVR2k3 (bastards), but the thought of manually compiling 120+ QFEs breaks my mind. I looked into the structure of the Entries.ini and 5eraph.inf files before commenting and, if I'm reading this correctly, you are manually compiling these QFEs INFs into one consolidated INF? If so, you deserve far more credit than you recieve here for that task. I thought for sure there was a "secret" script or pseudo-automated tool for such a task as that's what computers do best. Adding a couple QFEs wouldn't be that prohibitive, but several hundred? Unless done incrementally over the course of years, I see madness at the end of that tunnel; for me anyway.

With that in mind, I doubley thank you for the XPx64 pack and if I ever get the SVR2k3x32 pack going I'll forward a link for anyone interested.

As an aside, and just out of curiosity (considering how closely these two OS's parallel each other), I applied your Update Pack against a SVR2k3x64 image, installed it, and it appears to work fine. Haven't checked out every aspect of the Server's operation yet, but it tagged only one Critical Update from Microsoft Update (other that IE8 and .NET).

Anyway, if there is no script/prg to be had for this task I'll dive into this thing and endeavour to figure it out on my own.

Thanks again!

Post by **5eraph** » Tue Dec 28, 2010 1:37 pm

n7Epsilon has released a REG to INF tool that is useful. I wrote a very simple script around it which helps me create the file list in the registry from an exported REG file. But it doesn't do all the work due to limitations in my batch scripting ability and with REG2INF.exe.

I also wrote a script to help with extracting the downloaded update packages. You can get them below if you'd like to examine, improve or modify them to your needs. The archive includes n7Epsilon's latest version of REG2INF.

Download:

Link: 5er_UpdatePackageScripts_2009-12-01.7z
Size: 60.8 KB
MD5: 5aae2eeee883d82f5f192d4cb2477934

yumeyao · Post by **yumeyao** » Tue Dec 28, 2010 9:43 pm

Adding my script for downloading request-only hotfixes.

http://www.ryanvm.net/forum/viewtopic.php?p=107605

BTW, I'm coding some helper functions for update pack making in my spare time, I'll share them out when I think they are done and stable.

yumeyao · Post by **yumeyao** » Wed Dec 29, 2010 8:56 am

Hi 5eraph,
just took a look at your scripts, wondering what reg files are needed for your R2I script. Should I moniter each and export the reg difference?

BTW, I wrote a simple dll which helps the big-2 of file information: CheckSum and BuildTime. I also wrote a wrapper of autoitv3, hoping it helps you use this dll.

http://yumeyao.xpdnc.org/code/HotFixLib/
C Source, header file, lib file and au3 wrapper - and of course, dll file - included.

--EDIT--
Regarding BuildTime:
This dll returns LOCAL build time. Since DST is not used in China, I don't know how it is treated in windows updates. I mean, when an update is being installed, is whether the BuildTime in registry is DST or not judged by the current time or the file build time. However, I choose the latter here, hoping it's correct.

--EDIT2--
changed the link to my dashboard.

Post by **5eraph** » Wed Dec 29, 2010 11:10 pm

yumeyao wrote:Hi 5eraph,
just took a look at your scripts, wondering what reg files are needed for your R2I script. Should I moniter each and export the reg difference?

I export the file list under "HKLM\SOFTWARE\Microsoft\Updates\<OS_Name>\<SP_Level>\<KB_Article_Number>", as shown below.

In this case I save the exported registry entries to a file named KB2401588.reg. The script uses the number in the file name, so you must make certain to name the REG file correctly. After manually correcting the output (since I'm not good enough to write a script to do it for me yet), the registry entries specific to the update found in update_SP2QFE.inf under [Product.Add.Reg] should be added manually. I don't use registry comparing utilities such as InstallRite or RegShot for this.

yumeyao wrote:BTW, I wrote a simple dll which helps the big-2 of file information: CheckSum and BuildTime. I also wrote a wrapper of autoitv3, hoping it helps you use this dll.

Will this work with 64-bit files? The only reliable method for me so far has been to install the package and pull the information out of the registry. I have tried Siginet's tool without success for x64.

yumeyao wrote:Regarding BuildTime:
This dll returns LOCAL build time. Since DST is not used in China, I don't know how it is treated in windows updates. I mean, when an update is being installed, is whether the BuildTime in registry is DST or not judged by the current time or the file build time. However, I choose the latter here, hoping it's correct.

What time information is in the registry when installing a package, local or GMT? Whichever it is, I never adjust it. If I can't get the information for whatever reason then I don't include it. I know of no application that uses it. QFECheck ignores BuildDate and BuildCheckSum when checking installed updates.

yumeyao · Post by **yumeyao** » Thu Dec 30, 2010 12:45 am

I see. Thanks for the help on registry. However my dll is aiming at getting the files' info too(HKLM\SOFTWARE\Microsoft\Updates\<OS_Name>\<SP_Level>\<KB_Article_Number>). Well, it's because i'm now using win7 but maintenance a xp update pack, so I have to read directly from the PE file, not from registry after install.

I don't know whether it works with 64-bit files, it's a 32-bit dll. However, it uses windows APIs to do the job, so as long as the 2 important APIs(MapFileAndCheckSum and GetTimestampForLoadedLibrary) used by this dll could acquire the useful info from the PE header(I know that x64 PE header is slightly different from x86 PE header, but the checksum and timestamp offset should be same).

I'll later consider making a native x64 dll. But I'm still a noob in x64 programming. It doesn't harm since the time conversion I used is in assembly because int-64 is not natively supported on 32-bit OS, but is natively supported on x64.

The time information is in the registry is local while the timestamp stored in the PE file is GMT(A 32-bit integer is stored indicating seconds elapsed since 00:00:00 Jan 1 1970, i.e. Unix Time). Yes I know that BuildDate and BuildCheckSum is useless but better keep it, huh?

yumeyao · Post by **yumeyao** » Thu Dec 30, 2010 9:53 am

Just tried it with a x64 dll file, it's ok.

yumeyao · Post by **yumeyao** » Fri Dec 31, 2010 12:52 am

please visit http://yumeyao.xpdnc.org/code/HotFixLib/ to acquire the latest version.

Passion · Post by **Passion** » Tue Jan 04, 2011 2:49 pm

5eraph wrote:In this case I save the exported registry entries to a file named KB2401588.reg. The script uses the number in the file name, so you must make certain to name the REG file correctly. After manually correcting the output (since I'm not good enough to write a script to do it for me yet), the registry entries specific to the update found in update_SP2QFE.inf under [Product.Add.Reg] should be added manually.

Perhaps this usenet thread is useful for hints on scripting that. I know I made use of it several times anyway.
The only difference is pulling the string from the correct registry export, I guess..

Post by **5eraph** » Tue Jan 04, 2011 11:28 pm

Thanks for checking 64-bit files, yumeyao. I still have some learning to do before trying the DLL for myself.

And thanks for the link, Passion. I already have some experience with FOR loops like that. But you did just give me the idea to try the "REG EXPORT" command instead of manually exporting each key myself. I should have thought of it long before. From there I can think about better parsing since I have more experience now.

Of course, if I can make use of yumeyao's DLL then exporting registry entries may not be necessary for most updates. Much of my scripting would need rewriting for such a change.

It's been a year since I've revised my scripts. Maybe it's time for some rewriting and simplification if I can find the time.

yumeyao · Post by **yumeyao** » Wed Jan 05, 2011 12:30 am

The main problem exposed now is we should make up the file sequence, i.e. HKLM\SOFTWARE\Microsoft\Updates\<OS_Name>\<SP_Level>\<KB_Article_Number>\Filelist\x, this "x".

I have some colusions but not complete:
1. The file sequence follows per section's list in update.inf
2. For multiple filecopy sections appeared in update.inf, the sequence follows how these sections are arranged in [ProductInstall.ReplaceFilesIfExist] and [ProductInstall.CopyFilesAlways].

I don't know any other more tricks M$ play on this.

For example: IE8-WindowsXP-KB2416400-x86:
First we find:

Code: Select all

[ProductInstall.ReplaceFilesIfExist]
    CopyFiles=System32.files
    CopyFiles=program_files.internet_explorer

[ProductInstall.CopyFilesAlways]
    CopyFiles=CopyAlways.System32.files
    CopyFiles=CopyAlways.Cache.files

Despite CopyAlways.Cache.files(which we don't need), we lookup all other 3 sections:

Code: Select all

[System32.files]
    wininet.dll,SP3QFE\wininet.dll
    urlmon.dll,SP3QFE\urlmon.dll
    occache.dll,SP3QFE\occache.dll
    mstime.dll,SP3QFE\mstime.dll
    mshtmled.dll,SP3QFE\mshtmled.dll
    mshtml.dll,SP3QFE\mshtml.dll,,8
    msfeedsbs.dll,SP3QFE\msfeedsbs.dll,,8
    msfeeds.dll,SP3QFE\msfeeds.dll,,8
    licmgr10.dll,SP3QFE\licmgr10.dll
    jsproxy.dll,SP3QFE\jsproxy.dll
    inetcpl.cpl,SP3QFE\inetcpl.cpl
    iertutil.dll,SP3QFE\iertutil.dll,,8
    iepeers.dll,SP3QFE\iepeers.dll
    ieframe.dll,SP3QFE\ieframe.dll,,8
    iedkcs32.dll,SP3QFE\iedkcs32.dll
    ie4uinit.exe,SP3QFE\ie4uinit.exe

[program_files.internet_explorer]
    xpshims.dll,SP3QFE\xpshims.dll
    ieproxy.dll,SP3QFE\ieproxy.dll
    iedvtool.dll,SP3QFE\iedvtool.dll

[CopyAlways.System32.files]
    ieuinit.inf,SP3QFE\ieuinit.inf
    html.iec,SP3QFE\html.iec

So the final sequence is just like this....

I'm very poor at text parsing programming, so I don't intend to write such a code now....

RyanVM.net Discussion Board

5eraph's post-SP2 Update Pack v2017-06_2

Thank You Again, 5eraph!