Hotfixes For Windows XP Professional SP2

[cybpsych]

on my uA in VMware, WScript 8825 didn't install.

my scripts' DLLs still show 8820

am i missing something here?

[bucketbuster]

@cybpsych,

did you put qchain in your svcpack.inf and in your update folder?

It assures that the file with the highest version number gets installed.

Download qchain here:

http://download.microsoft.com/download/9/5..._spl_X86_EN.exe

Simply extract the file and you get qchain.exe.

[CrashUK]

Where did all the SP1 hot fixs go..

I dont like SP2 its not a update its a new os..

[RyanVM]

Where did all the SP1 hot fixs go..

I dont like SP2 its not a update its a new os..

Did you even bother to search?

http://www.msfn.org/board/index.php?showto...hl=sp1+hotfixes

[cybpsych]

@cybpsych,

did you put qchain in your svcpack.inf and in your update folder?

It assures that the file with the highest version number gets installed.

Download qchain here:

http://download.microsoft.com/download/9/5..._spl_X86_EN.exe

Simply extract the file and you get qchain.exe.

yes, bucketbuster

here's my svcpack.inf:

[Version]
Signature="$Windows NT$"

[SetupData]
CatalogSubDir="i386\Update"

[ProductCatalogsToInstall]

[SetupHotfixesToRun]
script8825.exe /Q:A /R:N
qchain.exe

fyi, i've added:

[OptionalSrcDirs]
Update

in my DOSNET.INF too ...

[RyanVM]

on my uA in VMware, WScript 8825 didn't install.

my scripts' DLLs still show 8820

am i missing something here?

I can't confirm. I run wscript56.exe (my name for it ) from cmdlines.txt with the same switches and the file versions show build 8825. Double check your spelling to make sure the exe is named like you think it is.

EDIT: For the record, these are the file versions you should be having:

 Date         Version     Size     File name
  ------------------------------------------------
  09-Aug-2004  5.6.0.8825  98,304   cscript.exe
  09-Aug-2004  5.6.0.8825  28,672   dispex.dll
  09-Aug-2004  5.6.0.8825  466,944  jscript.dll
  09-Aug-2004  5.6.0.8825  151,552  scrobj.dll
  09-Aug-2004  5.6.0.8825  151,552  scrrun.dll
  09-Aug-2004  5.6.0.8825  438,272  vbscript.dll
  09-Aug-2004  5.6.0.8825  114,688  wscript.exe
  26-Jun-2001              8,847    wscript.hlp
  09-Aug-2004  5.6.0.8825  28,672   wshcon.dll
  09-Aug-2004  5.6.0.8825  65,536   wshext.dll
  09-Aug-2004  5.6.0.8825  98,304   wshom.ocx

[cybpsych]

thanks RyanVM!

if it didn't execute on my svcpack.inf, well i'm going run it on cmdlines.txt ...

will feedback later =)

Updates: it finally installed when run through cmdlines.txt, inside a batch file,

script8825.cmd (my preferred )

@echo off

echo.
echo Installing MS Windows Script v5.6.0.8825
start /wait %systemdrive%\install\Xtra\script8825.exe /Q:A /R:N
echo.

exit

[koszopal]

hmm

after sp2 installation on windows update i ve got now

one more critical kb873374 (if i remember it was something ab gdi+ update and office)

koszopal

[GreenMachine]

Which is about the stupidest update I've seen yet. It is not really an update, it just runs a tool that will tell you, via a message box, if you should run an update or not. It definitly throws a wrench in the Unattended Installations unattended aspect.

At first glance, it looks like a registry setting can show this update as installed. To be continued ...

I just wish they'd talk to me before releasing this kind of stuff ...

It also looks like update WindowsServer2003-KB833987-x86-ENU.EXE is needed for Windows Server 2003, and IE6.0sp1-KB833989-x86-ENU.exe for Windows 2000, but I guess that should be in another thread.

[ToBe]

*oops* deleted.

Edited September 15, 2004 by ToBe

[cybpsych]

Critical Update for Windows XP (KB885626)

This non-security critical update helps resolve an issue where a limited number of systems running a BIOS without production support for Intel Pentium 4 and Intel Celeron D processors based on Prescott C-0 stepping can potentially hang on Windows XP Service Pack 2 installation. After you install this update, you may have to restart your computer.

http://www.microsoft.com/downloads/details.aspx?FamilyID=9b99c199-5d75-454f-ae07-b620727be8d8&DisplayLang=en

[creopard]

also see this link for the post above

http://support.microsoft.com/default.aspx?scid=kb;en;885626

[DisabledTrucker]

also see this link for the post above

http://support.microsoft.com/default.aspx?scid=kb;en;885626

Thank GOD for AMD!

Also, I noticed that people were using:

script8825.exe /Q:A /R:N

Is this a necessity or is this not one of the quiet install files? Also, where are they getting this script8825.exe file from or am I missing something here, as I don't see mention of the download for this one, or was it scripten.exe that is being referenced?

Edited September 15, 2004 by DisabledTrucker

[ToBe]

At first glance, it looks like a registry setting can show this update as installed. To be continued ...

Confirmed..

Adding this to the registry fools WU to think that the "hotfix" 873374 is installed:

HKLM,"Software\Microsoft\GdiDetectionTool","GDITool",0x00010001,0x1

I've attached a little exe that can be installed via svcpack.inf:

[Version] 
Signature="$Windows NT$"
MajorVersion=5
MinorVersion=1
BuildNumber=2600

[SetupData]
CatalogSubDir="\i386\Hotfixes"

[ProductCatalogsToInstall]

[SetupHotfixesToRun]
Q873374.exe /Q:A /R:N
Q885626.exe /Q /O /N /Z
qchain.exe

What it does is executing this inf adding the regdata

[Version]
Signature="$Chicago$"

[DefaultInstall]
AddReg=AddDetectionReg

[AddDetectionReg]
HKLM,"Software\Microsoft\GdiDetectionTool","GDITool",0x00010001,0x1

If you have any program listed under the two sections of Affected Software/components here:

http://www.microsoft.com/technet/security/...n/ms04-028.mspx

You need to install that specific hotfix, but this works with a clean WinXP SP2 install.

Q873374.exe

[enuffsaid]

with regard to the GDI+ Detection Tool (KB873374)....

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\GdiDetectionTool]
"GDITool"=dword:00000001

...will have Windows Update NOT show the GDI tool Critical Update. Delete this key and it will show again on WU.\

Oh bugger, somebody beat me to it.