Hotfixes For Windows XP Professional SP2

[bucketbuster]

I suppose it should be noted that MSXML 4.0 SP2 is still needed for SP2 systems, as it's not included in the package.

http://www.microsoft.com/downloads/details...&displaylang=en

If you guys are interested, I (once again) created a custom install for this which is WAY smaller than the 5MB Microsoft download and includes the KB832414 hotfix files.

http://www.ryanvm.net/msfn/msxml4sp2.exe (805KB)

Like my other installers, it uses the /qb switch on the MSI file. If you want one that uses /qn, send me an instant message.

Not working here.

Not sure why it isn't working. I used the same config for that one as I did all the other (working) installers. Try redownloading, I guess.

No luck. Same error. Tried on different computer and same error. Am I doing it wrong? Probally!

start /wait msxml4sp2.exe /qb

You don't nee any switches.

This is what I have in main_batch.cmd:

ECHO.

ECHO Installing MSXML 4.0 Service Pack 2 (Microsoft XML Core Services)

ECHO Please wait...

start /wait %systemdrive%\install\hotfixes\msxml4sp2.exe

[GreenMachine]

...

Not working here.

What's that picture? It sure looks to me that your StartX is a program named START.EXE, which conflicts with the Command Statement "START". If you do, in fact, have a program named START.EXE, there is your problem ...

[RyanVM]

...

Not working here.

What's that picture? It sure looks to me that your StartX is a program named START.EXE, which conflicts with the Command Statement "START". If you do, in fact, have a program named START.EXE, there is your problem ...

StartX is the program used by the SFX installer to start msiexec (since 7zip can't start EXEs not in the folder it extracted to).

If he's using switches, that's the problem. 7-zip self extractors pass extra switches down to the EXE being executed, and it sounds like it overrides the switches defined - so it's trying to run StartX.exe /qb which will definitely cause problems. THE EXE RUNS SWITCHLESS. THEY ARE PREDEFINED IN THE INSTALLER.

[war59312]

oh ok lol whoops hehe

thanks guys,

will

[GreenMachine]

... EDIT: It looks like that hotfix is for post-SP2 as well. It updates update.sys to build 5.1.2600.2508 (from 5.1.2600.2180)

EDIT2: The /integrate switch works with it too B). The only thing I don't like is that it doesn't compress the file at all. But it does automatically create the svcpack directory with the cat file and exe file in it. Pretty nice.

EDIT3: Here's the SP2 update info (if I read the link you gave me correctly, this version number will be different for SP1):

KB885626
  Date         Version        Size     File name
  ---------------------------------------------------
  01-Sep-2004  5.1.2600.2508  209,280  update.sys

1) It'll work in SP2, but it don't think it adds anything.

2) I know, that's why XPCREATE doesn't use that switch. XPCREATE does it cleaner. (I really wish they'd talk to ME first ... )

... StartX is the program used by the SFX installer to start msiexec (since 7zip can't start EXEs not in the folder it extracted to). ...

Oh well, it was just a guess ... never run into those kind of problems with IEXPRESS ...

[RyanVM]

1) It'll work in SP2, but it don't think it adds anything.

2) I know, that's why XPCREATE doesn't use that switch. XPCREATE does it cleaner. (I really wish they'd talk to ME first ... )

1.) I'm not sure, but it might improve generally compatibility with those processors.

2.) How do you get around the updates showing up on Windows Update with XPCREATE? What annoys me the most is that it makes a copy of every EXE you integrate, so it's essentially doing double time.

Oh well, it was just a guess ... never run into those kind of problems with IEXPRESS ...

3.) Yeah, but I bet you don't get as good of compression either . I will NEVAH be converted .

[CrimsonKain]

I don't fully understand this GDI+ tool. On a fresh install of XPSP2 with .NET 1.1 SP1 and Office2k3 SP1 it still tells me I have affected software. Does anyone know why? I don't mind applying the reg tweak but I'd feel safer if the tool said I was ok.

[DisabledTrucker]

Though this will be a rather long post, I wanted to include what is being said in the FAQ's section for this patch, especially the portions in relation to the O/S and programs that are affected and it's responses. Without further ado:

Frequently asked questions (FAQ) related to this security update 

Why are there several affected programs and components?
Windows XP, Windows XP Service Pack 1, and Windows Server 2003 provide an operating system version of the component that is vulnerable to this issue. Earlier versions of Windows did not provide an operating system version of this component. Therefore, when you install programs that require this functionality on earlier versions of Windows, this component is commonly installed. Typically, when these programs are installed on Windows XP, Windows XP Service Pack 1, or Windows Server 2003 they only use the version that is provided by the operating system, even if they install a copy of the vulnerable component. 

The exceptions to this are Office XP, Visio 2002, Project 2002, Office 2003, Visio 2003, and Project 2003. To make sure that JPEG images are processed consistently across all operating systems, these programs use their own version of the vulnerable component. This version of the vulnerable component is installed on all operating systems that are supported by these programs. If you have installed these programs, you must install the update for these programs. You must also install an operating system update if you use Windows XP, Windows XP Service Pack 1, or Windows Server 2003. 

Microsoft has created a tool that will also assist in detecting if you are running one or more affected products and components. Where can I get more information about this tool?


Microsoft has created the GDI+ Detection tool to assist customers in detecting if they are running one or more affected products that contain a vulnerable version of the JPEG Parsing component on their system. Microsoft Knowledge Base Article 873374 describes this tool as well as provides instructions on how to download this tool.

What does the GDI+ Detection tool do?

The GDI+ Detection tool scans your system for non-operating system products that are known to contain the vulnerable component. It then directs consumers to the appropriate locations for downloading an update to address the vulnerability.

Will the GDI+ Detection tool tell me if my system is at risk from this vulnerability?

No. The tool is only designed to scan the system and detect for certain installed products that are known to contain the vulnerable component. The tool is not able to determine if these products have already been updated to use a secure version of the affected component.

What is GDI+?

GDI+ is a graphics device interface that provides two-dimensional vector graphics, imaging, and typography to applications and programmers.

If I use Windows XP Service Pack 2 and use any of the affected software, what should I do?
Windows XP Service Pack 2 does not contain a vulnerable version of the affected component. However, if you have installed any of the affected Office, Visio, or Project applications you should install the updates for those applications. The easiest way to address this vulnerability is to install the updates provided by Office Update. If you have not installed any of the affected Office, Visio, or Project applications you do not have to install any other security updates because the other affected software and affected components use the operating system version of the vulnerable component on Windows XP Service Pack 2.

The exception for this is if you use Visual Studio .NET 2002 or Visual Studio .NET 2003 to develop applications that redistribute the Gdiplus.dll file. In this case you need to install the security updates for those programs even if you are using Windows XP Service Pack 2. See the Security Update Information section for these updates for more information.

If I use Windows XP, Windows XP Service Pack 1, or Windows Server 2003 and use any of the affected software, what should I do?
If you have installed any of the affected Office, Visio, or Project applications the easiest way to address this vulnerability is to install the updates provided by both Windows Update and Office Update. If you have not installed any of the affected Office, Visio, or Project applications the easiest way to address this vulnerability is to install the updates provided by Windows Update. You do not have to install any other security updates because the other affected software and affected components use the operating system version of the vulnerable component on Windows XP, Windows XP Service Pack 1, and Windows Server 2003. 

The exception for this is if you use Visual Studio .NET 2002 or Visual Studio .NET 2003 to develop applications that redistribute the Gdiplus.dll file. In this case you need to install the security updates for those programs as well as the security update for Windows XP, Windows XP Service Pack 1, or Windows Server 2003. See the Security Update Information Sections for these updates for more information.

If I use Windows 98, Windows 98 Second Edition (SE), Windows Millennium Edition (Me), Windows NT 4.0, or Windows 2000, what should I do?
By default, these operating systems do not natively provide a version of the vulnerable component and are not affected. However, the vulnerable component is installed on these non-affected operating systems when you install any of the software programs or components that are listed in the Affected Software and Affected Components sections of this bulletin. 

If you have installed any of the affected programs or components, you should install the required security updates for those programs or components. For example, if you have Internet Explorer 6 Service Pack 1 and Office XP installed on your Windows 2000 system, you have to install the Internet Explorer 6 Service Pack 1 security update and the Office XP security update. If you have not installed any of the affected programs or components, you do not have to install any security updates.

If I use versions of Internet Explorer that are earlier than Internet Explorer 6 Service Pack 1, am I vulnerable to this issue? 
Internet Explorer 5.01 Service Pack 3, Internet Explorer 5.01 Service Pack 4 on Windows 2000, and Internet Explorer 5.5 Service Pack 2 on Windows Me have been tested and they are not vulnerable. 

Internet Explorer 6 is only supported when using Windows XP, Windows XP Service Pack 1, and Windows Server 2003. Internet Explorer 6 on Windows XP, Windows XP Service Pack 1, and Windows Server 2003 uses the operating system version of the vulnerable component. When the Windows XP, Windows XP Service Pack 1, and Windows Server 2003 operating system update is installed, Internet Explorer 6 is not vulnerable. Windows XP Service Pack 2 includes Internet Explorer 6 Service Pack 2 and is not vulnerable to this issue. Internet Explorer 6 is no longer in support on other operating systems and may be vulnerable to this issue on those operating systems. Customers who do not use Windows XP, Windows XP Service Pack 1, or Windows Server 2003 and who use versions of Internet Explorer 6 that are earlier than Internet Explorer 6 Service Pack 1 should upgrade to Internet Explorer 6 Service Pack 1 and then install the Internet Explorer 6 Service Pack 1 security update provided in this security bulletin, or upgrade to Windows XP Service Pack 2 for Windows XP customers. To install Internet Explorer 6 Service Pack 1, visit the following Web site. For more information about the support lifecycle for Internet Explorer, visit the following Microsoft Support Lifecycle Web site.

If use Visual Studio .NET 2002, Visual Studio .NET 2003, the Microsoft .NET Framework 1.0 SDK Service Pack 2, or the Microsoft Platform SDK Redistributable: GDI+ to develop applications, what should I do?

When these programs are installed on Windows XP, Windows XP Service Pack 1, or Windows Server 2003 they use the operating system version of the vulnerable component. If you are using these programs on Windows XP, Windows XP Service Pack 1, or Windows Server 2003 make sure that you install the operating system version of the security update. If you are using these programs on other operating systems make sure that you install the update for these programs.

However, if you use these programs to create applications that distribute a version of the Gdiplus.dll file you need to install the appropriate security update based on the development tool you use, even if you have installed the Windows XP, Windows XP Service Pack 1, or Windows Server 2003 security update, or are using Windows XP Service Pack 2. If you use the Gdiplus.dll file for JPEG processing you should rebuild and redistribute your application using the updated version of the Gdiplus.dll file. For more information, see the appropriate Security Update Information sections depending on the developer tool you use.

Why is the security update for .NET Framework in a Service Pack?

This issue does not affect customers who have already deployed Microsoft .NET Framework 1.0 Service pack 3 (SP3) and Microsoft .NET Framework 1.1 Service Pack 1 (SP1). These service packs, released prior to the release of this security bulletin, already contain the security update for this issue as well as other security changes for all reported customer issues found after the release of these software components. Therefore, we highly recommended that customers using .NET Framework 1.0 or 1.1 install these Service Packs for increased security not only for this vulnerability but also for all reported customer issues found after the release of the Microsoft .NET Framework.

Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine if this update is required?
Yes. MBSA does detect if the update for this vulnerability is required for Office XP, Office 2003, Project 2002, Project 2003, Visio 2002, and Visio 2003. However, MBSA does not currently support the detection of several of the programs that are listed in the Affected Software and Affected Components section of this security bulletin. For detailed information about the programs that MBSA currently does not detect, see Microsoft Knowledge Base Article 306460. If you have installed any of the programs that are listed in the Affected Software and Affected Components section of this security bulletin you may have to manually determine if you have to install the required update. For example, a Windows 2000 or Windows NT 4.0 system that has installed Internet Explorer 6 Service Pack 1 will need to install the Internet Explorer 6 Service Pack 1 security update and MBSA will not detect the missing update in these configurations. Also, MBSA cannot use the Office Detection Tool to scan remote systems, it will only use this tool to scan a system locally for required security updates. For more information about MBSA, visit the MBSA Web site.

Note After April 20, 2004, the Mssecure.xml file that is used by MBSA 1.1.1 and earlier versions is no longer being updated with new security bulletin data. Therefore, scans that are performed after that date with MBSA 1.1.1 or earlier will be incomplete. All users should upgrade to MBSA 1.2 because it provides more accurate security update detection and supports additional products. Users can download MBSA 1.2 from the MBSA Web site. For more information about MBSA support, visit the Microsoft Baseline Security Analyzer 1.2 Q&A Web site.

Can I use Systems Management Server (SMS) to determine if this update is required?
Yes. SMS can help detect and deploy this security update. For information about SMS, visit the SMS Web site. SMS uses MBSA for detection; therefore, SMS has the same limitation listed earlier in this bulletin related to programs that MBSA does not detect. However, SMS can also use the Microsoft Office Inventory Tool to detect for required updates for Microsoft Office components.

Can I use SMS to determine if programs are installed that have to be updated?
Yes. SMS can help detect if any of the affected programs or affected components are installed that may have installed a version of the vulnerable component. SMS can search for the existence of the file Gdiplus.dll. For the affected programs and components listed in this bulletin you need to update all versions of Gdiplus.dll that are earlier than version 5.1.3102.1355. See the ‘Could I still be vulnerable even after I have installed all required security updates?’ FAQ in this bulletin for more information about other applications that may have installed the Gdiplus.dll file.

However, it is important to note that you should install the available security updates instead of manually updating the affected component. Manually updating the affected component could create application compatibility issues and is not supported. Also, applications that feature ‘Detect and Repair’ functionality will not receive the necessary information required to prevent these features from potentially introducing the vulnerability upon execution if the affected component is manually updated.

Installations of Office XP, Visio 2002, Project 2002, and Internet Explorer 6 Service Pack 1 (SP1) combine the features of the vulnerable component with other files. For Office XP and Project 2002 you would also have to search for the existence of the Mso.dll file. Update all versions of Mso.dll that are earlier than version 10.0.6714.0. For Visio 2002, you have to search for the existence of the Mso.dll file and the Gdiplus.dll file because Visio 2002 distributes both files, except on Windows XP, or Windows Server 2003 where it only distributes the Mso.dll file.

For installations of Internet Explorer 6 Service Pack 1 that are not running on the Windows XP or Windows Server 2003 operating systems, search for the Vgx.dll file. Update all versions of Vgx.dll that are earlier than version 6.0.2800.1411. Internet Explorer 6 Service Pack 1 uses the operating system version of the vulnerable component on Windows XP and Windows Server 2003. You do not have to update Internet Explorer 6 Service Pack 1 for those operating systems. These .dll files are documented in the Security Update Information section of this security bulletin. You can also deploy the updates provided in this bulletin using the Inventory and Software Distribution feature of SMS.

I use Software Update Services (SUS) to deploy security updates in my enterprise. Should I deploy the GDI+ Detection Tool to all of my systems?

While it is possible to deploy the GDI+ Detection Tool via SUS to all of the systems in an enterprise, it is not recommended or supported. The GDI+ Detection Tool will direct end users back to the Microsoft Windows Update site to scan their machines for updates. 

What security updates will Windows Update offer to help address this vulnerability?
Windows Update will offer the required operating system updates for Windows XP, Windows XP Service Pack 1, and Windows Server 2003. Windows XP Service Pack 2 does not require an update because it does not contain a vulnerable version of the affected component. Windows Update will offer the Internet Explorer 6 Service Pack 1 security update to Windows 98, Windows 98 SE, Windows Me, Windows NT 4.0 and Windows 2000 operating systems. Windows Update will offer the .NET Framework, version 1.0 Service Pack 2 (SP3) and the .NET Framework, version 1.1 Service Pack 1 to Windows NT 4.0 and Windows 2000 operating systems. These security updates are not offered to Windows XP or Windows Server 2003 systems because these components use the operating system version of the component on Window XP and Windows Server 2003.

What security updates will Office Update offer to help address this vulnerability?
Office Update will offer the required updates for Office XP, Office 2003, Project 2002, Project 2003, Visio 2002, and Visio 2003. These security updates are required on all operating systems where these products are installed. Office 2003 Service Pack 1, Visio 2003 Service Pack 1, and Project 2003 Service Pack 1 are not affected and will be offered to customers using Office 2003, Project 2003, and Visio 2003 instead of the individual updates. Customers who have installed these service packs are not affected by this vulnerability from these applications.

What security updates will not be offered through Windows Update or Office Update to help address this vulnerability and should be manually installed?
Windows Update and Office Update do not provide support for the remaining programs. This includes the security updates for Visual Studio .NET 2002 (and all included programs), Visual Studio .NET 2003 (and all included programs), Greetings 2002, Picture It! (all versions), Digital Image (all versions), the Microsoft .NET Framework version 1.0 SDK Service Pack 2, Producer for Microsoft Office PowerPoint (all versions), and the Platform SDK Redistributable: GDI+. These security updates are required on Windows 98, Windows 98 SE, Windows Me, Windows NT 4.0 and Windows 2000 operating systems where these products are installed. Note Visual Studio .NET 2002 Enterprise Architect and Visual Studio .NET 2003 Enterprise Architect include Visio 2002. Visio 2002 is supported by Office Update. 

Could I still be vulnerable even after I have installed all required security updates?
Yes. There are cases in which you might be vulnerable to this issue even after you install the required operating system update and the updates for programs or components that are listed in the Affected Software and Affected Components sections of this bulletin. The following examples document some of the possible cases: 

• You may have installed a third-party program that has installed the affected component. If the Gdiplus.dll file is installed on your system, you may have to install an update for that program. It is possible that not every program that installs this file is vulnerable to this issue because it may not use the Gdiplus.dll file to process JPEG images. However, only the manufacturer of that program can make that determination. This could include third party applications that were developed using Visual Studio .NET 2002, Visual Studio .NET 2003, or the Microsoft .NET Framework 1.0 SDK Service Pack 2. Typically, even if the affected component is installed on a system that is running Windows XP or Windows Server 2003, the program still uses the operating system version of the affected component.

• On Windows XP or Windows Server 2003, it is possible for a developer or administrator to force a program to bypass the vulnerable operating system component and instead use a version that they supply. This feature is not likely to be used in most circumstances. You may want to consider contacting the third-party application manufacturer for an updated version of their program, if they verify that their program uses this bypass feature. Steps to determine if you are using such a program are located in Microsoft Knowledge Base Article 835322.


In these cases, you would only be vulnerable to this issue while using the affected program to process images. Installing the operating system update and the updates for the affected programs and components listed in this bulletin will help reduce the chance that you will be attacked from the most common attack vectors an attacker could use to exploit this vulnerability. 

It is important to note that you should install the available security updates instead of manually updating the affected component, if possible. Manually updating the affected component could create application compatibility issues and is not supported. Also, applications that feature ‘Detect and Repair’ functionality will not receive the necessary information required to prevent these features from potentially introducing the vulnerability upon execution if the affected component is manually updated.

Can I manually script and deploy the required security updates?
Yes. We have released Microsoft Knowledge Base Article 885885 to assist with the manual installation of some of the available security updates. This article does not provide instructions for the installation of all available security updates and is provided only as a guide in the creation of custom scripts.

From what I gather what it says, is you should install this patch, but keep in mind that programs other than what is mentioned here can overwrite the files in question and thus trigger the responses you all are getting. It also goes on to describe which files are in question so you can take appropiate actions to replacing the files if the program itself wont. It also says that it can be triggered even if you have the updated patches of those programs, probably because it's finding newer versions than what it's actually checking for, so it's going to report that it's needing an upgrade which shouldn't be the case. If you have all the latest updates for all your software, then you shouldn't have a need for this patch. Though you could go back and check the files in question and assure that they are the correct versions and if not, upgrade them to the correct versions and thus not have that problem in the first place. Correct me if I am wrong here.

Edited September 16, 2004 by DisabledTrucker

[GreenMachine]

1) It'll work in SP2, but it don't think it adds anything.

2) I know, that's why XPCREATE doesn't use that switch. XPCREATE does it cleaner. (I really wish they'd talk to ME first ... )

1.) I'm not sure, but it might improve generally compatibility with those processors.

2.) How do you get around the updates showing up on Windows Update with XPCREATE? What annoys me the most is that it makes a copy of every EXE you integrate, so it's essentially doing double time.

Oh well, it was just a guess ... never run into those kind of problems with IEXPRESS ...

3.) Yeah, but I bet you don't get as good of compression either . I will NEVAH be converted .

1) I don't think it matters, as a hotfix will use it's own UPDATE.EXE. I think ... In any event, that file is continually updated, and they are always backwards compatible.

2) I don't, yet, get around the GDI+ update showing, and it CANNOT be installed silently. Still, I do not consider it an update: it just sends you to a web page. I'm hoping some that this was just a quick gap-stop, and they come up with something a tad bit more respectable ... soon. For now, I will just use a CMD file with REG to update the registry: I know what XPCREATE installs to the OS (by default), so I know if there are any vulnerabilities.

As for "double install", that has always been the Microsoft Company Line. You add the files to the source, and then need to run te hotfix to update the registry and whatnot. Adding the files to the source simply insures that you never have the outdated version. Updating the registry may, or may not, be required depending on the hotfix. It is usually required for tools that search the registry to determine if a hotfix has been installed, as Windows Update has been known to do on occasion.

3) Actually, the compression is quite comparable.

Lastly: NEVAH I didn't realize you were from Boston, home of No Mo Nomah! Go Sox Go! See you in October!

[RyanVM]

1) I don't think it matters, as a hotfix will use it's own UPDATE.EXE. I think ... In any event, that file is continually updated, and they are always backwards compatible.

That's pretty much my thought - it's not going to hurt to have the updated version even if isn't 100% necessary.

2) I don't, yet, get around the GDI+ update showing, and it CANNOT be installed silently. Still, I do not consider it an update: it just sends you to a web page. I'm hoping some that this was just a quick gap-stop, and they come up with something a tad bit more respectable ... soon. For now, I will just use a CMD file with REG to update the registry: I know what XPCREATE installs to the OS (by default), so I know if there are any vulnerabilities.

What registry entry is that? I'd like to add that to my registry tweaks.

As for "double install", that has always been the Microsoft Company Line. You add the files to the source, and then need to run te hotfix to update the registry and whatnot. Adding the files to the source simply insures that you never have the outdated version. Updating the registry may, or may not, be required depending on the hotfix. It is usually required for tools that search the registry to determine if a hotfix has been installed, as Windows Update has been known to do on occasion.

I can't believe there isn't a better way to do that.

3) Actually, the compression is quite comparable.

Lastly: NEVAH I didn't realize you were from Boston, home of No Mo Nomah! Go Sox Go! See you in October!

Actually, I'm from Michigan originally and now live in Philadelphia . Go Yanks!

Meh, for what it's worth, baseball is the sport I'm least interested in. I wore my Yzerman jersey to work today in mourning of the lost NHL season (and the likely end of his career) .

[GreenMachine]

@RyanVM: Go Yanks? Aw come on! Tigers, Phillies, even the Pirates and Orioles would be better. I mean, that's like rooting for Microsoft over Sun, IEXPRESS over 7ZIP!

The registry entry for GDI Tool is here:

http://www.msfn.org/board/index.php?showto...ndpost&p=189947

As for a better way for the hotfixes, one option would be just to extract the relevent part of the hotfixes' INF file, and run that without the extraction, copying, etc. Another would be to merge the different hotfixes, a la security rollup. Neither would be that complicated, but unless Microsoft does it, both would still be unsupported. In fact, many of the hotfixes can just have the files copied and work as designed, except for missing, often useless, information in the registy (e.g. add/remove).

[Sanjay]

"Microsoft GDI+ Detection Tool (KB873374)" <--- This is so stupid.

First of all Windows Update tells me that I need this update. When I install the update, it turns out that is not really an update but rather it takes me to a page for me to decide if I need the update. Anyhow based on the Applicable and Not Applicable lists, I determine that I don't need this update. This is because I have a clean installation of Win XP SP2 slipstreamed, clean Office 2003 SP1 slipstreamed, .NET Framework 1.1 SP1 Therefore as per their FAQ I should not need this update. I also run 'Office Update' and it tells me I don't need any updates but for some reason the program installed from Windows Update tells me I need the update. So I go ahead and download the 'Security Update for Internet Explorer 6 Service Pack 1 (KB833989)' which turns out is only for Windows 2000. Then I download 'Office 2003 Security Update KB838905' but when I run it, I get a message that "The update has already been applied or is included in an update that has already been applied.' Only Microsoft is capable of something like this. :angrym:

[Sanjay]

Can someone please explain how to install the "Update for Windows XP HighMAT Support in CD Writing Wizard (KB831240)" via the svcpack.inf method.

Thanks

[RyanVM]

start /wait %CDROM%\Updates\apps\HMTCDWizard.msi /quiet /norestart

It's an MSI file, though, so I'm pretty sure you won't be able to install it until the RunOnceEx (or GuiRunOnce) part of setup.

[GreenMachine]

Actually ... It installs fine from SVCPACK.INF, and it is delivered in an .EXE wrapper.

This should work:

HMTCDWizard_enu.EXE /QN

(**** Yankees!)