• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
Incroyable HULK

HOTFIXES: Windows XP SP2 & Windows 2000 SP4

1,597 posts in this topic

Okay Incroyable HULK

P.S.

my nick is netquik not netquick.

just like NesquiK Neslè

:P

0

Share this post


Link to post
Share on other sites

The switches for those hotfixes are the same as all the rest of the post-SP2 hotfixes.

0

Share this post


Link to post
Share on other sites

So let me get things straight. According to the first page, there are only two critical upgrades for a XP SP2 system? While all other released patches are non-critical?

0

Share this post


Link to post
Share on other sites

@netquik

sorry, I will add Nestle in front of your nick :lol:

@RyanVM

Switches done!

@Sgt_Strider

Yep, you got it right!

0

Share this post


Link to post
Share on other sites

KB887742 -› You receive the Stop error "Stop 0x05 (INVALID_PROCESS_ATTACH_ATTEMPT)" in Windows XP Service Pack 2 or Windows Server 2003

Download -› 447 KB (November 22, 2004)

0

Share this post


Link to post
Share on other sites

I'm seeing the KB836528 MyDoom removal tool in WindowsUpdate on fresh installs in VirtualPC now. Anybody else seeing this?

Needless to say, I'm already working on a GDItool-style fix for my next release :D

EDIT: I'm having no luck tricking Windows into thinking the MyDoom checker already ran with registry entries. This is a tough nut to crack.

0

Share this post


Link to post
Share on other sites

Ok on the GDITool,

I wanted a silent Install switch for it. It was a little tough but heres what I came up with.

that thing is so weird, doesn't copy the dll or .inf no where, basically it creates some reg entries and a few minor files

E:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb

E:\WINDOWS\SoftwareDistribution\DataStore\Logs\edb.chk

E:\WINDOWS\SoftwareDistribution\DataStore\Logs\edb.log

E:\WINDOWS\system32\config\system.LOG

E:\WINDOWS\system32\wbem\Logs\wbemess.log

and a few others it modifies or creates

I ran that on a clean Install of Pro with Dotnet I had to Install also. It requires Dotnet, Office or a few other things in order for it even to install. I'm thinking if those files needed update then possibly it would copy the oudetect.dll, msiutil2.exe, gditool.inf, gdidet.cif files and replace the old ones.

Modifies this reg key

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServiceCurrent]
@=dword:0000000a

Adds This

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_MSISERVER\0000\Control]
"ActiveService"="MSIServer"

I did determine that running it by clicking on it that it extracts it to the same exact %TEMP% dir I used in the commandline below

So heres what I'm thinking

The commandline I pasted is correct to install it silent.

Anyone got any thoughts on it?

SVCPACK.INF

[setupHotfixesToRun]

873374.exe /Q /T:%TEMP% /C /C:"%SystemRoot%\System32\rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 gditool.inf"

0

Share this post


Link to post
Share on other sites

Why not just add the one registry entry which tells Windows Update it's already installed? You shouldn't have an GDI issues with a fresh XP SP2 install anyway.

0

Share this post


Link to post
Share on other sites

I agree, do you really have to "install" this update? I prefer the registry tweak ;)

0

Share this post


Link to post
Share on other sites

True Thats what I will do then

Thats there if anyone wants it cause that works total Silent.

Edited by maxXPsoft
0

Share this post


Link to post
Share on other sites

OK, I still can't track down what change the Mydoom cleaner is making which gets WindowsUpdate to think it's be run. The most promising lead was a registry key being created called "RemovalTools" to which there was a REG_SZ entry called "MydoomTool" with a value of "OK". However, I manually added it on a fresh install and WindowsUpdate still saw it as a critical update to be downloaded. If anybody else manages to track down what change needs to be made, PLEASE let me know.

0

Share this post


Link to post
Share on other sites

Microsoft Security Bulletin MS04-040

Cumulative Security Update for Internet Explorer (889293)

Severity: Critical

Issued: December 1, 2004

Version: 1.0

Affected Components:

Internet Explorer 6 Service Pack 1 on Microsoft Windows 2000 Service Pack 3, on Microsoft Windows 2000 Service Pack 4, or on Microsoft Windows XP Service Pack 1: Download the update

Internet Explorer 6 Service Pack 1 on Microsoft Windows NT Server 4.0 Service Pack 6a, on Microsoft Windows NT Server 4.0 Terminal Service Edition Service Pack 6, on Microsoft Windows 98, on Microsoft Windows 98 SE, or on Microsoft Windows Me: Download the update

Internet Explorer 6 for Windows XP Service Pack 1 (64-Bit Edition): Download the update

Systems not affected:

Internet Explorer 5.01 Service Pack 3 on Windows 2000 SP3

Internet Explorer 5.01 Service Pack 4 on Windows 2000 SP4

Internet Explorer 5.5 Service Pack 2 on Microsoft Windows Me

Internet Explorer 6 for Windows Server 2003

Internet Explorer 6 for Windows Server 2003 64-Bit Edition and Windows XP 64-Bit Edition Version 2003

Internet Explorer 6 for Windows XP Service Pack 2

Site: Microsoft Technet Security

0

Share this post


Link to post
Share on other sites

Added. I'm still not finished with my simulations but it should be accurate...

EDIT: I'll have to check tomorrow, there is another obsolete update in Windows XP SP1 replaced by KB889293...

0

Share this post


Link to post
Share on other sites

According an article i read, Microsoft will also release a new serie of patchs for both IE and Windows. It should be on December 7th.

@ RyanVM : Maybe you should wait for this future release to make the 1.04 pack.

0

Share this post


Link to post
Share on other sites

@ Incroyable HULK

I must say your doing a great job keeping the SP1 hotfixes list up to date BUT, it's kinda messed-up :wacko:

You should put the lowest number first (in this case KB814078) and the the highest number last (KB889293) to make a good order. And you should definitely add the replaced/superseded hotfixes after all relevant hotfixes like posted here!

Update note to HULK:

KB889669 replaces > KB889293 which replaces > KB834707

and since KB834707 is also allready replaced by KB873377, I think this KB889669 also replaces KB873377, right? :huh::P

I just saying that everyone could benefit from a well ordered hotfixes-list! Right now it's a bit messy, sorry :no:

0

Share this post


Link to post
Share on other sites

I will correct this today. they will be put in numerical order

As I said before, my method to get the update list is under simulation with a clean installation an going to Windows Update website.

0

Share this post


Link to post
Share on other sites
@ RyanVM : Maybe you should wait for this future release to make the 1.04 pack.
Sounds good to me. And it's going to be a big update.
KB889669 replaces > KB889293 which replaces > KB834707

and since KB834707 is also allready replaced by KB873377, I think this KB889669 also replaces KB873377, right? :huh::P

OK, let me try to explain this to you (though you've pretty much got the right idea already).

889669 > 889293. 889669 appears to be 889293 with one extra fix included in the hotfix. And yes, Microsoft update rollups always postdate the older versions, so 889669 replaces 889293 which replaced 873377 which replaced 834707.

I hope that clears things up for you.

0

Share this post


Link to post
Share on other sites

Oke, thanks for the confirmation ;)

Now I can safely delete KB873377 from my Update directory.

0

Share this post


Link to post
Share on other sites

So if I got it right I should put KB889669 and then remove KB889293 KB873377 and KB834707

My only problem is how am I going to be sure theses are no longer required when I run my simulation... afterall Windows Update still list them as critical updates.

0

Share this post


Link to post
Share on other sites

Windows Update should know obsolete hotfixes on its end. Try a fresh install with just 889669 and see what it reports.

EDIT: Here's a quote directly from the KB889669 article:

Starting with MS04-025, cumulative hotfixes for Internet Explorer are available in a separate update rollup that includes both cumulative hotfixes and the security fixes included in the latest security update for Internet Explorer. For example, update rollup 871260 includes the cumulative security fixes in MS04-025 and hotfixes released since MS04-004. Update rollup 889669 includes the cumulative security fixes in MS04-040 and hotfixes released since MS04-004.
0

Share this post


Link to post
Share on other sites

Good Idea! I will try in a few minutes

God Bless the "snapshot" feature of WMware :rolleyes:

0

Share this post


Link to post
Share on other sites

This is the official list I get from Windows Update:

Windows XP SP1 (23)

KB889293 (new)

KB873376

KB873374

KB870669

KB841873

KB841533

KB841356

KB840987

KB840374

KB840315

KB837001

KB835732

KB833987

KB832483

KB828741

KB828035

KB828026

KB826939

KB825119

KB824105

KB823353

KB823182

KB814078

So i'll stick to that for my Update list. Beside, there is a massive update comming December 7... Wait & see

0

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.