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

[DISCONTINUED] Update Rollup 2 for Windows 2000

108 posts in this topic

ZxDg9.png

Update Rollup 2 for Windows 2000 SP4 is an unofficial rollup style package of updates. It is a cumulative update. It covers everything starting from the official Update Rollup 1 up to EOL (End-of-life) of Windows 2000 in July 2010. It can be installed in an existing Windows 2000 installation or slipstreamed (ex. using programs such as HFSLIP or nLite).

Update Rollup 2 uses exactly the same format as any official Windows update released by Microsoft. Only official public updates are included in it. It means that neither official hotfixes (available by request) or unofficial hotfixes are not part of this rollup.

Update Rollup 2 is based on Windows 2000 Service Pack 4 Updates page. Below you can find a full list of updates included in it.

----------------------------------------------------------------------------------------------------

Windows updates (93):

  • KB838989
    KB839228
    KB891861-v2 (Update Rollup 1)
    KB892211 (Web Folders update, no longer offered by MS)
    KB893756
    KB893803-v2 (Windows Installer 3.1)
    KB894395
    KB896358
    KB896423
    KB899587
    KB899589
    KB899591
    KB900725
    KB901017
    KB901214
    KB905414
    KB905749
    KB908506
    KB908531
    KB913580
    KB914388
    KB917008
    KB917537
    KB918118
    KB919521*
    KB920213
    KB920670
    KB920683
    KB923191
    KB923561
    KB923810
    KB923980
    KB924270
    KB924432
    KB924667
    KB925902
    KB926121 (installed only in Windows 2000 Server)
    KB926247
    KB926436
    KB927891
    KB928843
    KB935839
    KB938827
    KB942831
    KB943055
    KB943485
    KB950749
    KB950974
    KB951748-V2
    KB952004
    KB952954
    KB953155
    KB955069
    KB955417
    KB955759
    KB956802
    KB956844
    KB958470
    KB958644
    KB959426
    KB960225
    KB960803
    KB960859
    KB961501
    KB967715
    KB969059
    KB970238
    KB970483
    KB971032
    KB971468
    KB972270
    KB973037
    KB973507
    KB973869
    KB973904-v2
    KB974318
    KB974392
    KB974571
    KB974783
    KB975254
    KB975337 (GDI+ update)
    KB975713
    KB977290
    KB977914
    KB978037
    KB978601
    KB978706
    KB979309
    KB979482
    KB979559
    KB980195
    KB980218
    KB980232

Internet Explorer / Outlook Express updates** (7):

  • IE5.01sp4-KB938127-Windows2000sp4
    IE5.01sp4-KB982381-Windows2000sp4
    IE6.0sp1-KB905495
    IE6.0sp1-KB958869
    IE6.0sp1-KB982381
    OE5.5sp2-KB978542
    OE6.0sp1-KB978542

Script 5.1 / 5.6 updates (3):

  • KB917344***
    KB971961
    KB981350

DirectX7 updates**** (1):

  • KB975560

MDAC 2.53 updates (1):
  • KB927779

WMP 6.4 updates (5):

  • KB911564
    KB925398-v2
    KB954600
    KB974112
    KB977816

WMS 4.1 updates (2):

  • KB952068
    KB980858

 

* Fixes an issue with abnormal CPU temperature when using dual-core or hyper-threading processor, officialy available only as a KB article.

** The updates are installed accordingly to the IE/OE version which is used, i.e. IE5 updates when IE5 is present, IE6 updates when IE6 is used or slipstreamed. Everything is done automatically.

*** This update will not be installed/slipstreamed if you decide to use a newer version of Windows Script (5.6 or 5.7).

**** This update will be ignored if you use a newer version of DirectX (8.1 or 9).

----------------------------------------------------------------------------------------------------

If you decide to install or slipstream Update Rollup 2 you should not use any of the updates listed above as UR2 already covers all of them. Two updates (KB976323 & KB979683) were omitted intentionally as they seem to be buggy. In case of Remote Desktop Client update (KB958470), only registry entries are added to fix a security hole related to it. If you happen to actually use MS Remote Desktop, feel free to install KB958470 separately.

Two Windows 2000 Server only updates are not included in this rollup - KB961063, KB969883. If you use Windows 2000 Server you should install/slipstream them together with the Update Rollup 2.

If slipstreaming with HFSLIP you MUST NOT use Update Rollup 1 and Update Rollup 2 at the same time. Only one of them should be present in the HF folder so if you decide to use UR2 then you must remove UR1 from it (UR1 is included in UR2). I recommend using the newest beta of HFSLIP (available at Mim0's site). If you happen to use FDV fileset and slipstream IE6, using the newest beta of HFSLIP is required.

----------------------------------------------------------------------------------------------------

This is how installation process in a running system looks like:

ZxDg9.png

HSlCS.png

M3Gy1.png

EeHHs.png

----------------------------------------------------------------------------------------------------

I want to thank everyone who helped me create this package. There are too many people to list here but you know who you are :)

For support or bug report related with Update Rollup 2 please write in this topic or send me a message here.

----------------------------------------------------------------------------------------------------

Automatic Updates are turned OFF by default. Don't turn them ON if you want to avoid issues!

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

DOWNLOAD

:zzz:

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

Just to be totally clear - This Update Rollup 2 does NOT include Update Rollup 1??

I got that impression from:

If slipstreaming with HFSLIP you MUST NOT use Update Rollup 1 and Update Rollup 2 at the same time. Only one of them should be present in the HF folder.

So to have the basis of a fully up to date Win2K you need to take Win2K, integrate SP4, then slip Update Rollup 1 in one pass, then Update Rollup 2? If this is true, is there any chance of combining the two in a future release, or would that be of any benefit? If I misunderstood, you might want to clarify a bit in the instructions that Update Rollup 1 has been replaced so is no longer required.

Also, it might be helpful to show how to do a complete Win2K install, with commonly used apps and all. Maybe partner up with Kurt_Aust, or use his guide as a template/model? http://www.msfn.org/board/topic/97047-up-to-date-windows-2000-install-media-creation-guide/ The comparison between the two approaches might be interesting.

Cheers and Regards

0

Share this post


Link to post
Share on other sites

UR1 is included :)

I fixed the description. If using HFSLIP it should go like this -> SP4 (if not already slipstreamed), UR2, other updates (WMP, DX9, newer Script, MDAC, etc.).

As for Kurt_Aust's guide, I know it but it's much more comprehensive than my work now. At the moment I'm concentrated on MS-style updates / update rollups while Kurt includes everything in his guide - from updates to applications. I haven't really thought about including non-MS applications in my projects... yet ;) I'll have to think more about it.

Still UR2.0 is going to include only official updates. There will an upgraded version later on - I want to add a MDAC 2.53 update and WMP6.4 security updates. UR2.1 will include more things but it's still in the planning stage now.

0

Share this post


Link to post
Share on other sites

I added the Italian version.

0

Share this post


Link to post
Share on other sites

Just to make everything clear - BlackWingCat's Japanese Rollup has no connection with my Update Rollup 2. It's much more comprehensive, apart from MS updates includes also many other components, and CANNOT be slipstreamed.

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

Just one information - BITS 2.0 is not installed by this Rollup. Other Windows Update related updates are also not installed. If you still want to use WU you should install them manually.

0

Share this post


Link to post
Share on other sites

Since Win2K is past end of life, the only value for WU/MU is for the other MS products such as Office, correct? Win2K is no longer examined or updates offered, or am I wrong?

Cheers and Regards

0

Share this post


Link to post
Share on other sites

Yes and no ;)

WMP9, MDAC2.8, .NET Framework etc. are not included in UR2 so if you install WMP9 after UR2, the updates for it will be shown in WU. But generally speaking you're right. No new (released after July 2010) updates appear in WU, even for those system components that are still getting new updates (ex. .NET Framework). If you install newer .NET updates, you should turn WU off as it will still ask for the older, replaced ones. The same case is with the unofficial W2k updates.

That's why I didn't include any WU related updates in UR2 - WU doesn't have any real use today.

EDIT

This is how WU should look like after installing UR2-v2 (WMP9, DX9, newer >2.53 MDAC not installed)

91fXK.png

Only 5 updates are offered to download.

KB908531 - not recommended (Verclsid.exe), see bristols for details

KB944338, KB971961, KB981350 - Script 5.6 updates, it's because I installed IE6 with Script 5.6 before UR2 (UR2 installs only a Script 5.1 update)

KB979683 - kernel update, buggy (check first post)

UR2-v2 is being tested at this moment. I added WMP6.4 security updates, MDAC2.53 SP3 and a GDI+ update.

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

Well I know that any users that are not as familiar with things to the extent that you are would prefer that after installing UR2 or UR2-v2 if they go to WU/MU that the only updates that show up are the ones that should be truly applied. I know that anyone that is choosing to use Win2K at this point should be willing to educate themselves appropriately, but is there anything you could do to hide updates that you feel should not be applied when UR2 or UR2-v2 is applied, or do you think that would not be a good idea? Or did I misunderstand what you posted? Just a thought.

Cheers and Regards

0

Share this post


Link to post
Share on other sites

This a really good idea. I haven't thought about it :o

There are several ways to do it but the easiest one is to add catalog files (*.CAT) from these updates to UR2 which will make WU not ask about them.

0

Share this post


Link to post
Share on other sites

Done but it was much more difficult than I thought it would be. Only adding the .CAT files didn't work because WU apparently checks file versions too. I had to do some work and change file versions manually in order to prevent WU from asking for KB979683. Before doing so I checked KB979683 once more - and got a blue screen after reboot. So no KB979683 in UR2. In case of 908531 I had to add the file Verclsid.exe to the Rollup but didn't add the related registry entries. By doing so it's just a dummy file - it's not used by the system but is still present in %systemroot%\system32 folder. WU doesn't ask for 908531 anymore.

rsH4y.png

EDIT

At the end, I think I'll have to make UR2 disable WU :/ something doesn't seem to work properly.

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

I currently use Windows 2000 SP4 Rollout 1. Can this just be applied right away? Nothing else needs doing? Note that since I put 2000 on, it has not connected to the Internet so it's not got any updates since Rollout 1.

Reason I'm asking is because I saw the "Let's keep Windows 2000 alive" topic and saw things like Service Pack 5 etc.

Edited by FireFox276
0

Share this post


Link to post
Share on other sites

Yes, Update Rollup 2 can be installed over UR1 without any problems :yes:

BUT

I strongly recommend waiting just one more day for UR2-v2 as it's almost ready and includes several important fixes to the current version.

0

Share this post


Link to post
Share on other sites

I uploaded Update Rollup 2 (v2).

The total number of included updates is now 107.

Changes:


  • - added KB927779 for MDAC 2.53 (compatible with MDAC 2.81)
    - added KB911564, KB925398-v2, KB954600, KB974112, KB977816 for WMP 6.4
    - added KB975337 (GDI+ update)
    - fixed issue with slipstreaming UR2 and IE6 with HFSLIP (some IE5 files were copied instead of the IE6 ones)
    - fixed several cosmetic issues
    - from now Automatic Updates are disabled by default (DON'T TURN THEM ON!!!)

I hope this will be the final version of Update Rollup 2.0.

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

What's the difference between this and the UR1 from M$?

To explain it in one word - UR2 is UR1 + 106 other updates (released after UR1 starting from 2005 till July 2010).

0

Share this post


Link to post
Share on other sites

tomasz86,

First of all thank you very much for all the hard work you've done in creating these "programs" . I know it requires much of your time and I appreciate it.

I have attempted to slipstream the Update Rollup 2, DX9.0c Full Pack, and IE / OE Mini Rollup v1.1 using the lastest version of HFSLIP and have receive the following errors.

1. During the copy files phase I get the following error: Shlwapi.dllError See attachment below I believe this due to 2416400 update

2. During the Performing Final Tasks Phase I get the DXError See attachment below

3. Finally, During the First Boot I get the ScriptError See attachment below

Again, thanks for these great tools and any insight you can shed on these errors would be very helpful.

My2GirlsDad

0

Share this post


Link to post
Share on other sites

I'll check it as soon as possible but could you give me your HFSLIP log? It would help me a lot when diagnosing the problem :)

0

Share this post


Link to post
Share on other sites

I get an error from nLite when adding this as a hotfix.

It says kb##### cannot be slipstreamed after it extracts it.

0

Share this post


Link to post
Share on other sites

I'll check it as soon as possible but could you give me your HFSLIP log? It would help me a lot when diagnosing the problem :)

Thanks tomasz86 for looking into this. Here's my HFSLIP log.

0

Share this post


Link to post
Share on other sites

After doing some tests:

Kelsenellenelvian,

nLite direct integration of UR2 is unsupported because UR2 contains a few files which are not present on the original W2K CD (ex. gdiplus.dll). It can be only integrated indirectly. I recommend using HFSLIP in this case.

I'll have to add this to the readme. I'm sorry for inconvenience :}

My2GirlsDad,

These problems are not caused by UR2.

1. You're right about the IE / OE Mini Rollup 1.1. The header of shlwapi.dll is wrong. The same problem occurs if you try to slipstream WildBill's KB2416400.

I prepared a corrected version of IE/OE Mini Rollup 1.1 (v2a) and KB2416400 (v2).

By the way, KB2416400 & KB2423089 are already included in IE / OE Mini Rollup 1.1. You shouldn't use both :no:

2. There is something wrong with DX Full Pack. I'll need to check it once again from the beginning.

3. It's caused neither by UR2 nor by IEOEMR1.1. I need to do more tests.

I also suggest using the newest UR2 (v2). You could delete the following updates

  • KB911564
    KB925398-v2
    KB954600
    KB974112

KB977816 is also included in UR2 but only for WMP6.4. You're slipstreaming WMP9 so you still should slipstream KB977816 separately (as you're doing now).

You also seem to include stuff related to Windows Update. UR2 at this moment is not compatible with it - the updates already included in UR2 will still show in WU. For this reason UR2 (v2) disables Automatic Updates by default.

I'll write here again after I find out the causes of #2 & #3.

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

2. You have to use this unofficial kernel made by BlackWingCat (and modified by me to make it streamable) when using DX9 Full Pack (June 2010).

Windows2000-KB935839-v5a-x86-ENU.exe

Just copy it to HF :)

In case of DX9 Full Pack (Standard) there is no need for any patches.

EDIT

3. This error is caused by Script 5.7 (scripten.exe). It's not related to anything else. I've just did a test where I used a clean Win2k SP4 & scripten.exe and processed it through HFSLIP - and got this error on the first boot.

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.