Windows Updates

[bristols]

Well, Windows2000-KB908531-v2-x86-ENU.EXE is included for the sake of completeness, even though later release contain an updated SHELL32.DLL file.

Boy, I admit that did not quite compute.

Is the later release on the list? If so, which one?

967715 has the last official SHELL32.DLL - build 5.0.3900.7155. However the list of unofficial patches (to which I linked in my previous post) has a later (unofficial) build (thanks to WildBill!) - 5.0.3900.7158. The update in question is 2286198 - MS10-046 Vulnerability in Windows Shell Could Allow Remote Code Execution (update) - right now the first in the list. An obligatory word of caution - it's an unofficial update (although no-one seems to have had any problems with WildBill's updates, including me).

You rock dude.

Back and forth.

*****

OK, I admit it. I'm a noob. I just spent five minutes trying to figure out how to make a "so and so, said:" quote. Anyone want to toss the old man a bone and give me a clue?

When you reply to a post, the first quote (in square brackets) shown in the message box contains the name of the quoted post's author and the time it was made.

Edited December 12, 2010 by bristols

[Guest]

These are my findings for December...

Windows XP

Malicious Software Removal Tool updates to version 3.14

+ KB2296199

+ KB2416400

+ KB2423089

+ KB2436673

+ KB2440591

+ KB2443105

+ KB2467659

- KB981957 replaced by KB2436673

- KB2279986 replaced by KB2296199

- KB2360131 replaced by KB2416400

[Mim0]

+ 2447961 (MS10-094: Windows Media Encoder)

hrmpf... I always forget in the first moment that the ENCODER is not an origin part of WinXP

Edited December 15, 2010 by Mim0

[fo128]

I appologize if intruding, but this seemed as the closest discussion to my topic, and I also can't get over this (bug)!

I have WinXP Home SP3.

Listed in Add / Remove is the MSXML 6.0 Parser (KB925673).

With yesterday's (Dec 14th 2010) Windows Update, I was offered the following update - KB973687!

This seems to be in order (my current ...\system32\msxml6.dll is Version 6.20.1099.0) and the update offers the newer version (6.20.1103.0).

However, why was this update only offered to me yesterday?

Short installation history:

I formated and re-installed fresh Windows XP Home (CD Slipstreamed to SP3), around end of Sep 2010,

In the next 1-2 days, I ran the MS Updates, untill all security and non-security fixes were installed (only one remained - windows live, but this shouldn't play a role with this issue).

I keep updating every Tuesday (if any updates are released by MS).

My first assumption was that a recently installed program might have triggered this.

However, I have not installed anything in the last, say 2-3 weeks, and even if i did, my Microsoft Update (it is set on AUTO/PROMPT) should have "picked-up" this update as "missing" at that point already (assuming I did install something that required this update).

The end point is that the KB was only offered yesterday at MS UPDATE - any ideas?

A little to the side of the topic:

Since I researched a little on this issue, I noticed a different but related KB973686.

However, MS indicates that this KB is only applicable if MSXML 6.0 was installed by a stand alone program or application.

The KB 973687, is released update for the version of MSXML 6.0 which is installed with the OS.

I did download the KB973686, but it failed to install on my system.

Friendly regards.

[Mim0]

Regarding MSXML-Updates for XP: Probably this helps

http://mimo.zxq.net/msxml.htm

[fo128]

Regarding MSXML-Updates for XP: Probably this helps

http://mimo.zxq.net/msxml.htm

Mim0:

Thank for your time and feedback.

After the reserch, I also figured out some of the info you did provide via your link, but yours has much greater detail and excellent presentation.

However, the main reason for my post - the question still remains - why is this old update only emerging now, on the Auto Update site and for my system?

It should have become available immediately on the update site, right after my MSXML 6.0 installation - which judging from the current version of the MSXML6.DLL, most probably was installed during the fresh installation of the OS.

Perhaps, this issue is still new, and more similar occurance will emerge from different users as time goes by.

I only managed to find a single post on th web having the exact same referrence.

http://www.windowsbbs.com/windows-xp/96759-windows-update-prompts-install-kb973687-dated-11-23-2009-sp3.html

[PROBLEMCHYLD]

If anyone is using Win 2000 Server, can you post a list of all current & obsolete updates.

Thanks.

[Mim0]

If anyone is using Win 2000 Server, can you post a list of all current & obsolete updates.

Thanks.

this list contains updates for W2K workstation and server. In addition you can use the file-checker in combination with the W2K-extension. Edited December 16, 2010 by Mim0

[PROBLEMCHYLD]

Here is my list for 2000 server some updates are hotfixes etc...

Are there other updates that might not be listed ? Is any of mines thats listed obsolete?

IE5.01SP4-KB982381-WINDOWS2000SP4-X86-ENU.EXE

ROOTSUPD.EXE

W2KSP4_EN.EXE

WINDOWS2000-KB830460-X86-ENU.EXE

WINDOWS2000-KB832004-X86-ENU.EXE

WINDOWS2000-KB838989-X86-ENU.EXE

WINDOWS2000-KB839228-X86-ENU.EXE

WINDOWS2000-KB842933-X86-ENU.EXE

WINDOWS2000-KB891861-V2-X86-ENU.EXE

WINDOWS2000-KB893756-X86-ENU.EXE

WINDOWS2000-KB896358-X86-ENU.EXE

WINDOWS2000-KB896423-X86-ENU.EXE

WINDOWS2000-KB898465-X86-ENU.EXE

WINDOWS2000-KB899587-X86-ENU.EXE

WINDOWS2000-KB899589-X86-ENU.EXE

WINDOWS2000-KB899591-X86-ENU.EXE

WINDOWS2000-KB900725-X86-ENU.EXE

WINDOWS2000-KB901017-X86-ENU.EXE

WINDOWS2000-KB901214-X86-ENU.EXE

WINDOWS2000-KB905414-X86-ENU.EXE

WINDOWS2000-KB905749-X86-ENU.EXE

WINDOWS2000-KB908506-X86-ENU.EXE

WINDOWS2000-KB911589-X86-ENU.EXE

WINDOWS2000-KB913580-X86-ENU.EXE

WINDOWS2000-KB914388-X86-ENU.EXE

WINDOWS2000-KB917008-X86-ENU.EXE

WINDOWS2000-KB917537-X86-ENU.EXE

WINDOWS2000-KB918118-X86-ENU.EXE

WINDOWS2000-KB920213-X86-ENU.EXE

WINDOWS2000-KB920670-X86-ENU.EXE

WINDOWS2000-KB920683-X86-ENU.EXE

WINDOWS2000-KB921398-X86-ENU.EXE

WINDOWS2000-KB922667-X86-ENU.EXE

WINDOWS2000-KB923191-X86-ENU.EXE

WINDOWS2000-KB923561-X86-ENU.EXE

WINDOWS2000-KB923810-X86-ENU.EXE

WINDOWS2000-KB923980-X86-ENU.EXE

WINDOWS2000-KB924270-X86-ENU.EXE

WINDOWS2000-KB924667-X86-ENU.EXE

WINDOWS2000-KB925902-X86-ENU.EXE

WINDOWS2000-KB926121-X86-ENU.EXE

WINDOWS2000-KB926247-X86-ENU.EXE

WINDOWS2000-KB926436-X86-ENU.EXE

WINDOWS2000-KB927891-X86-ENU.EXE

WINDOWS2000-KB928843-X86-ENU.EXE

WINDOWS2000-KB932590-X86-ENU.EXE

WINDOWS2000-KB935839-X86-ENU.EXE

WINDOWS2000-KB938827-X86-ENU.EXE

WINDOWS2000-KB942831-X86-ENU.EXE

WINDOWS2000-KB943055-X86-ENU.EXE

WINDOWS2000-KB943485-X86-ENU.EXE

WINDOWS2000-KB950749-X86-ENU.EXE

WINDOWS2000-KB950974-X86-ENU.EXE

WINDOWS2000-KB952004-X86-ENU.EXE

WINDOWS2000-KB952954-X86-ENU.EXE

WINDOWS2000-KB953155-X86-ENU.EXE

WINDOWS2000-KB955069-X86-ENU.EXE

WINDOWS2000-KB955417-X86-ENU.EXE

WINDOWS2000-KB955759-X86-ENU.EXE

WINDOWS2000-KB956802-X86-ENU.EXE

WINDOWS2000-KB956844-X86-ENU.EXE

WINDOWS2000-KB957097-X86-ENU.EXE

WINDOWS2000-KB958644-X86-ENU.EXE

WINDOWS2000-KB959426-X86-ENU.EXE

WINDOWS2000-KB960225-X86-ENU.EXE

WINDOWS2000-KB960803-X86-ENU.EXE

WINDOWS2000-KB960859-X86-ENU.EXE

WINDOWS2000-KB961063-X86-ENU.EXE

WINDOWS2000-KB961501-X86-ENU.EXE

WINDOWS2000-KB967715-X86-ENU.EXE

WINDOWS2000-KB969059-X86-ENU.EXE

WINDOWS2000-KB969883-X86-ENU.EXE

WINDOWS2000-KB970238-X86-ENU.EXE

WINDOWS2000-KB970483-X86-ENU.EXE

WINDOWS2000-KB971032-X86-ENU.EXE

WINDOWS2000-KB971468-X86-ENU.EXE

WINDOWS2000-KB972270-X86-ENU.EXE

WINDOWS2000-KB973037-X86-ENU.EXE

WINDOWS2000-KB973507-X86-ENU.EXE

WINDOWS2000-KB973869-X86-ENU.EXE

WINDOWS2000-KB973904-X86-ENU.EXE

WINDOWS2000-KB974318-X86-ENU.EXE

WINDOWS2000-KB974392-X86-ENU.EXE

WINDOWS2000-KB974571-X86-ENU.EXE

WINDOWS2000-KB974783-X86-ENU.EXE

WINDOWS2000-KB975254-X86-ENU.EXE

WINDOWS2000-KB975560-X86-ENU.EXE

WINDOWS2000-KB975713-X86-ENU.EXE

WINDOWS2000-KB976323-X86-ENU.EXE

WINDOWS2000-KB977290-X86-ENU.EXE

WINDOWS2000-KB978037-X86-ENU.EXE

WINDOWS2000-KB978601-X86-ENU.EXE

WINDOWS2000-KB978706-X86-ENU.EXE

WINDOWS2000-KB979309-X86-ENU.EXE

WINDOWS2000-KB979482-X86-ENU.EXE

WINDOWS2000-KB979559-X86-ENU.EXE

WINDOWS2000-KB979683-X86-ENU.EXE

WINDOWS2000-KB980218-X86-ENU.EXE

WINDOWS2000-KB980232-X86-ENU.EXE

WINDOWSINSTALLER-KB893803-V2-X86.EXE

WINDOWS-KB890830-V3.13.EXE

WINDOWS-KB909520-V1.000-X86-ENU.EXE

[Mim0]

Here is my list for 2000 server some updates are hotfixes etc...

Are there other updates that might not be listed ? Is any of mines thats listed obsolete?

...you can use the file-checker in combination with the W2K-extension.

[PROBLEMCHYLD]

Here is my list for 2000 server some updates are hotfixes etc...

Are there other updates that might not be listed ? Is any of mines thats listed obsolete?

...you can use the file-checker in combination with the W2K-extension.

Thanks but no thanks. This is what I was looking for

http://thehotfixshare.net/board/index.php?autocom=downloads&showcat=15

Its has if not all 2000 Server/Pro thats not listed @ fdv site or any other place. This is what I was talking about.

Some are obsolete, some are not.

Edited December 18, 2010 by PROBLEMCHYLD

[Inki]

FYI, regarding update KB952013 for XP :

HFSLIP does not appear to support slipstreaming SmartCard_XP_x86.exe (renamed as WindowsXP-KB952013-x86-xxx.exe), which therefore should be placed into HFSVCPACK_SW1 rather than HF.

When run manually, the update places its driver file wudfusbcciddriver.dll into windows\system32\drivers\umdf\, where the accompanying wudfusbcciddriver.inf then expects to find it if and when a device comes around that needs it. (See line #85 of update.inf extractable from the update exe as well as line #122 of wudfusbcciddriver.inf). HFSLIP does not have specific coding to handle this special location (it is not an essential fix after all), and attempting to slipstream the update places the driver file into windows\system32\, where it most likely is useless. ( I don't have any suitable smart card device to conclusively verify this in practice.)

(Still, as this update is not likely to be needed in most cases, a reasonable person might opt not to install it at all unless truly needed.)

P.S.

I thought I could still mention, that not being a reasonable person myself, I do slipstream even this update, but to make it proper, I have to make the following manual modifications to TXTSETUP.SIF before burning my install CD:

New line under [WinntDirectories]:

1010 = "system32\drivers\umdf"

Modified line under [sourceDisksFiles] ('2' replaced by '1010'):

wudfusbcciddriver.dll = 1,,,,,,,1010,0,0

Edited January 7, 2011 by Inki

[bristols]

For those that don't know, I maintain the Windows 2000 Hotfixes page on FDV's site. FDV hasn't responded for the past couple of months to my attempts to contact him, and as a result, the page hasn't been updated (I can't upload changes to the page myself). Does anyone have any suggestions? I will consider posting the page elsewhere if there's any indication that FDV cannot / will not any longer be available.

[fdv]

hi all, i updated the win2k page. all others are updated too.

i have gotten very lazy and i apologize. i now use windows 7 and have very little motivation on the previous generations of windows.

i will say that since rt7lite is out, and since so many files in windows are the same, customizing win 7 is fairly straightforward.

the fileset work i did for so long was so long ago and i just don't intend to update the xp or 2003 sets any more either. i encourage people to apply what they have learned in this forum to dissecting win7.

emailed bristols about this too

[rulman]

HFSVCPACK_SW1

Windows2003-SP2-WindowsMedia-KB975558-x86-ENU

WindowsServer2003-KB925876-v2-x86-ENU

WindowsServer2003-KB956744-x86-ENU

WindowsServer2003-KB2416400-x86-ENU

Ie8 and updates can not be integrated out of the above. Is there a solution for this?

Edited January 30, 2011 by rulman