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

[HJW]

Code: Select all

2:52:35  -     Gathering txtsetup.sif [SourceDisksFiles] and [WinntDirectories] Entries
22:52:35  - WARNING: Filename Exceeds 8.3 Format - waaclient.dll
22:52:35  - WARNING: Filename Exceeds 8.3 Format - waaclient.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wbitsprx4.dll
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wFlshUtl9.exe
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wimapi2fs.dll
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims401.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims402.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims403.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims404.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims405.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims406.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims407.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims408.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims409.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims40b.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims40c.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims40d.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims40e.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims410.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims411.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims412.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims413.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims414.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims415.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims416.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims418.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims419.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims41a.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims41b.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims41d.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims41e.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims41f.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims422.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims424.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims425.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims426.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims427.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims42a.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims42d.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims804.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims816.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsims81a.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wmsimsc0a.mui
22:52:35  - WARNING: Filename Exceeds 8.3 Format - wtzchange.exe
22:52:35  - WARNING: Filename Exceeds 8.3 Format - ww03a3409.dll

Some issues to fix

[5eraph]

Not really, WINNT.EXE does not exist on an x64 CD, therefore the errors mean nothing.

WINNT32.EXE should have no issues with long file names.

I would love to be proven wrong, however.

EDIT: Microsoft also uses the long file name when the /integrate switch is used, so I must be doing it right.

Code: Select all

[ProductInstall.Slipstream.Hotfix]
    i386\wwininet.dll,SP2QFE\wow\wwininet.dll
[color=white]    i386\ww03a3409.dll,SP2QFE\wow\ww03a3409.dll[/color]
    i386\wurlmon.dll,SP2QFE\wow\wurlmon.dll
    i386\wshdocvw.dll,SP2QFE\wow\wshdocvw.dll
    i386\wmstime.dll,SP2QFE\wow\wmstime.dll
    i386\wmshtml.dll,SP2QFE\wow\wmshtml.dll
    i386\wdxtrans.dll,SP2QFE\wow\wdxtrans.dll
    i386\wdxtmsft.dll,SP2QFE\wow\wdxtmsft.dll
    i386\wbrowseui.dll,SP2QFE\wow\wbrowseui.dll

[HJW]

ok cool

I am currently trying to expand my .NET 20 installer for X64 with 3.0 and 3.5.

Will keep you posted

EDIT: will not work under T13 :S
EDIT: NETfx AIO installer is on its way

[HJW]

.NET framework AIO addon available in addons topic, also uploaded vista bootscreen x64 and logonui xpize black x64

@5eraph; when slipstreaming IE7 the microsoft update shortcut is nog working anymore. It launches in 64bit edition of IE7 and MU requires 32bit. Could the shortcut be edited to fix this issue?

HJW

[5eraph]

Thanks for the addons.

I noticed the strange behavior of the shortcut as well. I'll see what I can do.

[cold95]

Thanks too

[5eraph]

when slipstreaming IE7 the microsoft update shortcut is not working anymore. It launches in 64bit edition of IE7 and MU requires 32bit. Could the shortcut be edited to fix this issue?

After running a few tests I've determined that it's an issue with IE7, not with the Update Pack or nLite. It can be avoided by opening IE7 normally at least once before attempting to use the Microsoft Update shortcut.

However, changing the shortcut as you've suggested, HJW, does solve the problem when the following line in 5erUpPck.inf is changed from

Code: Select all

CmdLine	   = 10,SysWOW64,"rundll32.exe %10%\SysWOW64\muweb.dll,LaunchMUSite"

to

Code: Select all

CmdLine	   = 16426,"Internet Explorer","IExplore.exe ""http://update.microsoft.com/"""

The fix has been implemented in the next Update Pack, which I should be releasing sometime today.

[5eraph]

Updated to 2008-07_1. Please read the Changelog for full details.

Thanks to ricktendo64's help I've managed to work MSXML4 SP2 (KB941833) into the pack. This has the annoying side effect of causing the Microsoft Update site to believe we're interested in MSXML6 SP1 (KB934268). MSXML6 is not likely to ever be included in this Update Pack for the following reasons:

1. Known Issues

   • Some people are still having problems installing products which include MSXML6 (such as Visual Studio 2005) due to the presence of the MSXML6 SP1 DLL on the system. The simplest solution for this problem is to download and install the MSXML6 SP1 MSI prior to installing whatever software is trying to install MSXML6.

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

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

3. MSI installers are the toughest to make into true addons, they have some "Update", "Repair" and "Uninstall" features/reg entries that cause lots of problems if not fully entered.
   I made a MSI into a true addon once it caused a "New Hardware Wizard" to launch on 1st login. Since then I quit trying.
   I always use svcpack or WPI (if its not svcpack compatible) to install my MSI based installers, its much less trouble.
   
   P.S. I think RegShot might be the problem, it does not catch all the reg entries. Try InstallWatch.

   rictendo64 +1
   
   I spend a week for integrating MSXML 6 in my french Update pack, the only way i find 100% safe is to use the MSI (administrative install).

4. What's New
   Version 2.2.1

   • ..
   • Removed MSXML 6.0 SP1 due to ongoing installation conflicts.

[HJW]

First of all thank you for the update I know it is sometimes a pain in the ass to create an updatepack.

I got a couple of question;

I forgot to put winnt.sif in my test iso and therefore the installation really was 'standard', just x64+pack+wmp+ie7. I got a popup

Code: Select all

'BATTERY' do you want to install this?

is this related to my setup? or something with the slipstream proces? Also got a popup for Intel Host Controller, USB Root ... for about every device..
Driver problem?

EDIT: WMPslipstreamer did not integrate WMP11 as it should. pretty screwed. I will test again

Second, do you use the following as wbem fix ?
[T-13.KB943729.RunCommand]
"%11%\wbem\mofcomp.exe" "%11%\wbem\polprocl.mof"

[5eraph]

That battery warning seems to be caused by slipstreaming IE7. You may notice some problems with QFECheck throwing random warnings for each Windows install. Yet another symptom is setuperr.log reporting WOW64.CAT couldn't be installed, which causes a ton more errors in setuperr.log. I'm interested in finding a fix, even if it means removing an update that might be conflicting with it, but I haven't had the time yet.

I haven't noticed any problems with other drivers in VMware. I'm hoping your next test clears those up.

I haven't ever needed the WBEM fix for x64. That code is related to KB943729. You'll find that line in the file update_srv2k3.inf, which is included with Microsoft's package.

Code: Select all

[ProcessesToRun]
    "%systemroot%\system32\wbem\mofcomp.exe" "%systemroot%\system32\wbem\polprocl.mof"

[HJW]

WMP is slipstreamed properly now. I dont get any of the popups.

setuperr.log only reports errors related to IE7 files. WOW64.cat is not listed in there. I am thinking of an IE7 x64 addon. There are certain workarounds to keep setuperr.log clean.

Microsoft Update now works with IE7 slipstreamed. However still asks for installing activex control. Registering muweb.dll both in sys32 and syswo64 does not help, still asks for installing activex control.
This problem is also not present when using IE7 addon I think.

What do you think of adding wmp11, directx9 and silverlight to the updatepack?

HJW

[5eraph]

I don't want to duplicate anybody else's work. There's also the question of how many would object to having them included. I'd like to keep people's options open.

I personally prefer WMP11 and DX9, leaving IE7 out until post-install so it can be uninstalled when IE8 is eventually released. Boooggy's slipstreamer has worked perfectly for me so far; if I can't do it better then I see no point. I'm open to trying to create a DX9 addon, but you seem to have a solution for that already.

You'll need tweaks to fix the ActiveX control issue and others. But I don't know how to fit those into IE7 when slipstreamed with nLite.

[5eraph]

Updated to 2008-07_2.

I have split the Update Pack due to a catalog file limitation that occurred in Windows when slipstreaming Internet Explorer 7 on top of the pack with nLite. This is by no means a new problem. I was hoping I'd have a bit more time before I hit the wall.

Using both the Update Pack and the IE6 Updates Addon will not cause Windows to hit the limit. They are meant to be used together unless you plan to slipstream IE7. In that case you can use the Update Pack and IE7 (and IE7's updates) in the same session in nLite.

[HJW]

Updated to 2008-07_2. Please read the Notes section of the first post for an explanation of the resolved issue.

Thanks for the update

[bphlpt]

[*]Does not include Internet Explorer 7

... snip ...

I have split the pack due to a catalog file limitation in Windows when slipstreaming Internet Explorer 7

I assume you meant to say Internet Explorer 6 in the second part of above? Otherwise I don't understand what IE7 has do do with your Pack when you don't include it. Just trying to be helpful.

Cheers and Regards.

[5eraph]

I meant what I posted.

The problem only occured when somebody slipstreamed IE7 on top of Pack 2008-07_1 with nLite. I split the pack to make it more compatible with this process.

EDIT: I have added that bit of information to the first post for clarity. Thanks for bringing it to my attention.

I have split the pack due to a catalog file limitation that occurred in Windows when slipstreaming Internet Explorer 7 on top of the pack with nLite.

[bphlpt]

No problem. Thanks for the clarification so quickly.

Cheers and Regards.

[RickSteele]

fresh realtime install and absolutely flawless using the pack without the IE6 updates-IE7 slipstreamed.
Beautiful 5eraph

[LuisiLe]

servus 5eraph your work is very good but you work is misisng updates
I mean this:
938759
948496
922706
925066
938680
932762
927891
926122
932596
933729
943460
941644
943485
943055
941693
951072

Can you include this updates in your pack?
You do a very god job with this pack.
please emeil me if yes luisile@azet.sk

[5eraph]

After going through your list, here's what I have determined:

• KB922706 - Only appears to be useful if you're hosting websites in an organization.
  KB925066 - Only appears to be useful in a domain environment. But I'm thinking about it anyway.
  KB926122 - WinXP x64 SP2 is not affected by this vulnerability.
  KB927891 - Obsoleted by additional update KB942288.
  KB932596 - Obsoleted by additional update KB953600. Also obsoleted by additional update KB944984-v2, which will be in the next release.
  KB932762 - This will be included in the next release. Thanks for bringing it to my attention.
  KB933729 - Obsoleted by additional update KB952145.
  KB938680 - Obsoleted by high priority update KB951748.
  KB938759 - Already included.
  KB941644 - Obsoleted by high priority update KB951748.
  KB941693 - Obsoleted by additional update KB952679.
  KB943055 - Obsoleted by additional update KB948570.
  KB943460 - Obsoleted by additional update KB945272.
  KB943485 - Obsoleted by additional update KB944043.
  KB948496 - Seems to apply to server hardware. The hotfix contains no files to install, only the registry entries described in Method 3 of the KB article.
  KB951072 - This is already scheduled to be in the next release.

Email sent.

[LuisiLe]

OK! Thanks you are good i wait for the next release Thanks!

[5eraph]

Updated to 2008-07_3.

[RickSteele]

man, you are on an exceptional role 5eraph; fresh realtime install, absolutely stellar

[runningfool87]

very impressive, sir.

[retalion]

Latest Version 2008-07_3 integrated and installed, works flawless.

Thank you for this, time to completely switch to x64 now.

[ENU_user]

how do i slipstream the sp2 server version on a 32-bit system
funny i cant find reference for this ...

so yet, i haven't gone through using the hardware adviser for 64 bit but i intend to
once i can test an img on 32-bit if isn't of imposing a problem to do so. seems like forever Ive been waiting to try this...

this looks like a great 64-bit pack ,5eraph

thanks

[5eraph]

oao and I are discussing the slipstreaming of x64 components within x86 environments in the following thread:

• Integrating the service packs themselves

You can find a link to a matching thread on MSFN there as well.

[RickSteele]

Two updates available publically for you to consider 5eraph:

http://support.microsoft.com/kb/931125

...at Microsoft®Update Catalog: http://test.catalog.update.microsoft.co ... /Home.aspx

....according to the KB article valid for XP (64) as well

and

http://www.microsoft.com/downloads/deta ... layLang=en

..for Windows XP x64 Edition KB955417

Also, Windows Messenger 5.1.715 available here:

http://support.microsoft.com/kb/899283

Thanks

[5eraph]

Updated to 2008-08_1.

I seriously considered adding Windows Messenger 5.1.715, RickSteele, but manipulating the MSI is simply too much work for something I don't use. I much prefer Windows Live Messenger 8.5 even though the powers that be say it's not supported in x64. Works perfectly for me with a modified installer.

Your other two suggestions (KB931125 and KB955417) are worth looking at, but not worth holding back this release. We'll see.

[RickSteele]

Thanks 5eraph

[RickSteele]

latest is another complete winner 5eraph...Thanks

[retalion]

Also Thanks again from me for this pack.

[RickSteele]

Vulnerability in Vector Markup Language Could Allow Remote Code Execution (938127)

has been updated Aug. 28, 2008

IE7 here: Link

and IE6 here: Link

[5eraph]

I'm not seeing it. I believe the recent update was to include IE7 for XP x86 SP3. No relevant changes for us.

Revisions

• ..
• V2.0 (August 26, 2008): Bulletin revised to include Internet Explorer 7 for Windows XP Service Pack 3.

[RickSteele]

You're right , sorry about that. Thanks

[5eraph]

Updated to 2008-09_1. Please read the Changelog for full details.

Special thanks to TranceEnergy of MSFN for compiling a list of new and outdated update packages. It saved me a lot of time researching, and I'm not even done reading through it.

[ricktendo64]

Thanks...did not notice that comma missing from KB943326

[RickSteele]

Version: 2008-09_1, as always it seems, works perfectly-fresh, realtime install; thanks very much 5eraph.

[TranceEnergy]

Good work on this list/pack!

As i see on this list 5eraph marks things as optional, im not going to do that for the complete list, it needs to stay that way it is, since the mantra is to have every system files updated. There's nothing to stop any user from removing a component anyway, and it also would help nlite in making new removals possibly for nlite if something doesnt truly go away.

I'm thinking about doing research into creating a custom Service pack for xp x64. What u guys think? Would that be very hard to do or just lots of work?

If it needs much knowledge i dont know if i can do it, but i can do lots of editing. Just created a batch file which does 4827 lines of deleting files after Adobe cs3 master install (removes around 20 000 files).

[5eraph]

Thanks.

I use "High Priority" and "Optional" in my list to refer to how they're listed on the Microsoft Update website.

• 

"Additional Updates" are updates that do not fall into either of the other two categories and may include QFE updates (hotfixes) that are not generally available through the Microsoft Download Center.

I don't know how hard it would be to create a custom service pack. AutoPatcher can provide very similar functionality for systems that already have Windows installed.

[TranceEnergy]

I see. Sorry for misinterpreting that. I thought Autopatcher died more or less. Well glad to see it alive again!

I read something about creating 32bit service pack, but dont know if things apply same way for 64bit, probably tho i guess.

What's lead me to the thought of an eventual sp3 x64 is that even though the complete list contains 164 KB's/355mb, it only comes in at an 130mb something, additional data when integrated with nlite. I cant say i have noticed any slower boot time or such either.

[5eraph]

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

Thanks again to TranceEnergy for his list. I'm still borrowing heavily from it.

[HJW]

Thanks for the update.

a tip for those who are interested:

Remove Windows Search 4.0 from MU, just add following reg entries

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search]
"CurrentVersion"="04.00.6001.503"
"SetupCompletedSuccessfully"=dword:00000001

[5eraph]

Thanks for that, HJW.

[oao]

Hi,

KB901105 was the hotfix for high definition audio. Do you know if it is included in your pack, or if it was made obsolete by SP2?

Thanks.

[5eraph]

According to Microsoft's list, it's included in SP2. The version available for download at KB901105 only contains an SP1QFE branch, which seems to confirm this.

[TranceEnergy]

I already told oao this, what's the point of repeating this question?

[oao]

I asked simultaneously in two places because I did not know who would know and respond.

Thanks.

[RickSteele]

....just to confirm what you already know....latest update pack works perfectly-fresh realtime install; integrator and nlite

[TranceEnergy]

Hi guys! I have imported a lot of tweaks for internet explorer, and long story short, some webpages were behaving weird. So i thought i'd try the Internet Options/Internet Properties/Advanced and Reset.

Which has a warning only to use if browser is in a unstable state. Which i reckon it was.
Things seems to work a bit better now, but Windows update is reset to v4 (not v6 or such) and i've tried a few things, but it's simply just stuck at v4 (old windows update).

I dont know about you guys, but i think that "that" shouldnt be possible. What ought to have happened is that the "Reset" should revert to a default of the latest version of windows update.

I'm not using 5erap's update pack, but i am using IE7 integrated with nlite, so nothing different there, that i know of.

Any thoughts on this ? In any case, at least this is a warning not to mess with that "reset" option.