tomasz86

I know it's quite a late reply but it seems that it's only that one flash drive to work so slowly. I tried a few others and they seem to work O.K. Anyway, thank you for your help

I think I'll have to change my mind about UR2. I wanted to make a one big Rollup will all of the available updates but HFSLIP is an obstacle to do it. The problem is that HFSLIP treats UR1 (891861) differently from the rest of updates. It is being unpacked before processing other components (DX, IE, etc.) and there are some strings related specifically to it (HFSLIP adds some reg entries, copies & deletes several files, etc.). For this reason I changed the filename of UR2 to 891861-UR2. What's the main problem? It's impossible to add DX9 updates for example. Because the update numbered 891861 is processeded before everything else, DX9 files are not copied (because at that moment DX9 is not YET slipstreamed...). On the other hand, other updates are processed later, after all other components have been slipstreamed which means that DX files are copied correctly. I'm thinking about making a new version of UR2 without UR1 which means that in order to have everything slipstreamed you will have to slipstream both UR1 and UR2. The advantage of doing so is that I have much more freedom when preparing the Rollup. Also, the package itself will be much simpler which is a + here as it'll be much easier to edit / fix / add components. I'm sorry for this confusion I belive this is the only way to be able to slipstream everything what is necessary and keep compatibility with HFSLIP at the same time. PS Update Rollup RC2 still works 99% (can't say 100% as I haven't done all necessary tests...) correctly so feel free to use it if you wish

By the way, there is also another advantage of using 976576 instead of 982524. 976576 can be processed by Silent .NET Maker synthesized while 982524 cannot

Yes but it will take some time as it's around 130 HBRs to merge. First I want to finish UR2. I also want to make UR2.1 which apart from the official updates will include also unofficial ones (not only WildBill's, MDGx's and mine which are available here at MSFN but also some from BlackWingCat... especially kernel32 v5 or newer if possible). The other difference will be that UR2, when finished, won't be updated anymore (unless bugs are found) while UR2.1 will be updated when new unofficial updates are available.

HFVER 0.0.2 (38.33 KB) is ready. I added md5 checking. It may not look pretty but that's not the point here ? TEMP\HF\empty.cat 6.0.2800.1585 TEMP\HF\iecustom.dll 6.2.29.0 TEMP\HF\spmsg.dll 6.2.29.0 TEMP\HF\spuninst.exe ? TEMP\HF\update 5.0.3854.2500 TEMP\HF\vgx.dll // // File Checksum Integrity Verifier version 2.05. // b1035a2e505af840eaaa5ed685d072d6 temp\hf\empty.cat af4dcbfe51d3fa7509f28cb0d793f101 temp\hf\iecustom.dll 37044da1f53a8a6e5c54fca4c974511a temp\hf\spmsg.dll b5ff6305e3b6fdfc91057d2fac100e4c temp\hf\spuninst.exe 3b701381334d8863e2cda06c53c9c076 temp\hf\vgx.dll

bristols, 824995 - that's true but the file installed by this update is not a part neither of Windows nor of any other update; still this update is probably not necessary 838141 - there is no Rastapi.dll in 839228 the KB article is wrong ? TEMP\HF\empty.cat 5.0.2195.6883 TEMP\HF\ipsec.sys 5.0.2195.6882 TEMP\HF\ipsecmon.exe 5.0.2195.6824 TEMP\HF\netdiag.exe 5.0.2195.6882 TEMP\HF\oakley.dll 5.0.2195.6882 TEMP\HF\polagent.dll 5.0.2195.6882 TEMP\HF\polstore.dll 5.0.2195.6872 TEMP\HF\rasmans.dll 6.2.29.0 TEMP\HF\spmsg.dll 6.2.29.0 TEMP\HF\spuninst.exe ? TEMP\HF\update

Update Rollup 2 RC2 (41 MB) ready Changelog: RC2 - added 917344 & 975560 RC1 - added 899591, 926121, 970483, 958470, 974571, 973904, 951748 Known issues: - KB979683 not included and will not be included as it seems to be buggy - three Server updates not included (961063, 969883, 974783) and (probably) will not be included in this Rollup; the other Server updates are included - Server update 976323 not included as it is buggy Full list of included updates (90): I decided to include DirectX7 update (975560) and Script 5.1 update (917344). The files replaced are originally present in Win2k so they were only replaced with newer versions. They will get replaced by newer versions if you slipstream DX9 and newer Script so don't worry

A tough task I would say IE5.01SP4-KB938127-WINDOWS2000SP4-X86-ENU.EXE <- OK IE5.01SP4-KB982381-WINDOWS2000SP4-X86-ENU.EXE <- OK MDAC_TYP.EXE <- OK MDAC281-KB927779-X86-ENU.EXE <- OK MSXML2.MSI <- OK MSXML2SP6-KB887606-X86-ENU.EXE <- OK MSXML4-KB973685-ENU.EXE <- OK MSXML6-KB973686-ENU-X86.EXE <- OK OE5.5SP2-KB978542-WINDOWS2000-X86-ENU.EXE <- OK ROOTSUPD.EXE <- OK WINDOWS2000-KB2079403-V1A-X86-ENU.EXE <- OK WINDOWS2000-KB2121546-X86-ENU.EXE <- OK WINDOWS2000-KB2124261-V1A-X86-ENU.EXE <-OK WINDOWS2000-KB2290570-X86-ENU.EXE <- OK WINDOWS2000-KB2347290-X86-ENU.EXE <- OK WINDOWS2000-KB2360937-V1A-X86-ENU.EXE <- OK WINDOWS2000-KB2387149-V1A-X86-ENU.EXE <- OK WINDOWS2000-KB2419632-X86-ENU.EXE <- OK WINDOWS2000-KB2440591-X86-ENU.EXE <- OK WINDOWS2000-KB2443105-V2-X86-ENU.EXE <- OK WINDOWS2000-KB2443685-X86-ENU.EXE <- OK WINDOWS2000-KB2476687-V2A-X86-ENU.EXE <- OK WINDOWS2000-KB2479628-V8-X86-ENU.EXE <- OK WINDOWS2000-KB2485663-X86-ENU.EXE <- OK WINDOWS2000-KB2507618-V1A-X86-ENU.EXE <- OK WINDOWS2000-KB2511455-X86-ENU.EXE <- OK Everything is OK up to now. WINDOWS2000-KB654654-SRV-V3-X86-ENU.EXE <- HBR Mini Rollup (Srv) WINDOWS2000-KB811392-X86-ENU.EXE <- NEW WINDOWS2000-KB816134-X86-ENU.EXE <- OK, is on bristols WINDOWS2000-KB817446-X86-ENU.EXE <- OLD, newer version already in another update WINDOWS2000-KB824995-V3-X86-ENU.EXE <- NEW, Time Zone update WINDOWS2000-KB825027-X86-ENU.EXE <- OK, is on bristols WINDOWS2000-KB829395-X86-ENU.EXE <- NEW, winsta.dll has newer wersion, the rest is older WINDOWS2000-KB833154-X86-ENU.EXE <- OLD, newer version already in another update WINDOWS2000-KB838141-X86-ENU.EXE <- NEW, rastapi.dll has newer version, the rest is older or same WINDOWS2000-KB838969-X86-ENU.EXE <- OLD, newer version already in another update WINDOWS2000-KB890067-X86-ENU.EXE <- ?, same files already in another update WINDOWS2000-KB891861-UR2-RC1-X86-ENU.EXE <- OK, Update Rollup 2 RC1 WINDOWS2000-KB899268-X86-ENU.EXE <- OK, is on bristols WINDOWS2000-KB904712-X86-ENU.EXE <- OLD, newer version already in another update WINDOWS2000-KB922582-X86-ENU.EXE <- OK, but it's for Windows Update, useless if using unofficial updates WINDOWS2000-KB961063-X86-ENU.EXE <- OK, one of the three Srv updates not included in UR2 WINDOWS2000-KB969883-X86-ENU.EXE <- OK, one of the three Srv updates not included in UR2 WINDOWS2000-KB974783-X86-ENU.EXE <- OK, one of the three Srv updates not included in UR2 WINDOWS2000-KB975560-X86-ENU.EXE <- OK, DX7 update WINDOWS2000-KB979687-V2-X86-ENU.EXE <- OK WINDOWS2000-KB981322-X86-ENU.EXE <- OK WINDOWS2000-KB981852-V2A-X86-ENU.EXE <- OK WINDOWS2000-KB982132-X86-ENU.EXE <- OK WINDOWS2000-KB982214-V1A-X86-ENU.EXE <- OK WINDOWS2000-KB982665-V2-X86-ENU.EXE <- OK WINDOWS-KB890830-V3.13.EXE <- OK, Malicious Software Removal Tool WINDOWS-KB909520-V1.000-X86-ENU.EXE <- OK, Smartcard update, not really necessary To sum up, you're using a Server edition of Windows 2000 and you decided to slipstream HBRs together with public updates (official and unofficial). As for the public updates, everything seems to be OK. In case of HBRs, you're using my HBR Mini Rollup v3 which is quite outdated as many new updates have been added to the bristols' site recently. If you really want to include all HBRs in your Windows CD, I would suggest downloading them one by one as HBR Mini Rollup includes many updates which have been just replaced by the newly added updates. If you still decide to use HBR Mini Rollup, then compare this list with the HBRs available at bristols' and download the missing ones. BTW, HBRs may cause system instabilities so please be careful when slipstreaming them. They weren't thoroughly tested as public updates are. UR2 does not include any HBRs. And the last but very important thing, if you are using FDV fileset and slipstream IE6, you MUST use the newest beta of HFSLIP to have all files slipstreamed correctly.

I think that 2416400 should have different filename. It's an IE6 Cumulative Update and Windows 2000 IE6 Cumulative Updates used to follow this scheme: IE6.0sp1-KBXXXXXX-Windows2000-x86-ENU in opposite to IE5's IE5.01sp4-KBXXXXXX-Windows2000sp4-x86-ENU. 2416400's current filename is Windows2000-KB2416400-x86-ENU. Wouldn't it be better to change it to IE6.0sp1-KB2416400-Windows2000-x86-ENU? What's your opinion on this, WildBill?

Update Rollup 2 RC1 (KB891861-UR2-RC1) ready Changelog: RC1 - added 899591*, 926121*, 970483*, 958470**, 974571, 973904***, 951748**** BETA3 - Update Rollup 1 (KB891861-v2) added - catalog files are installed - filename changed BETA2 - Windows Installer 3.1 included (KB893803-v2, KB927891) - Web Folders update (KB892211) included Known issues: - Windows Installer 3.1 not yet included (KB893803-v2, KB927891) - KB951748-V2 not yet included - KB958470 not yet included - KB974571 not yet included - KB979683 not included and will not be included as it seems to be buggy - three Server updates not included (961063, 969883, 974783) and (probably) will not be included in this Rollup - Server update 976323 not included as it is buggy - catalog files (*.cat) are not installed * - these updates are marked as Server only updates by bristols but 899591 - installs rdpwd.sys which is deleted by HFSLIP if Windows 2000 Professional is detected. Rdpwd.sys is also present in UR1. 926121 - does not install any files but adds only one registry entry. It will be added only if you use Windows 2000 Server (all editions) 970483 - installs httpext.dll which is present also in Windows 2000 Professional ** - in case of 958470 these registry entries are added and the update itself is not installed *** - official 973904 cannot be slipstreamed but 973904-v2 can and this the one included in this Rollup **** - 951748 is marked as "not for server" by bristols but Microsoft says it can be installed in any edition of Windows 2000. It also gets automatically installed if you run Windows Update in Windows 2000 Server. I still need to do some cosmetic work but the Rollup itself is already completed. Final version should be ready in a very short time

I prepared a corrected version of the Wordpad update 973904 which includes the corrected wordpad.inf. It can be slipstreamed from HF folder and no changes have to be made further. Windows2000-KB973904-v2-x86-ENU.EXE Please check this topic for details.

There is another problem with this: [SourceDisksNames] 3 = "Windows CD",\CDROM_NT.5,,\I386 "Windows CD" means that the label MUST be "Windows CD" in order to copy these files. So what's the problem? For example, if you use nLite to make a bootable CD, it'll automatically change it to "Winlite" which will break the above string. I think I found the ultimate solution You should change this [SourceDisksNames] 3 = "Windows CD",\CDROM_IP.5,,\I386 [SourceDisksFiles] mswrd6.wpc = 3 mswrd8.wpc = 3 write.wpc = 3 [WordPadCopyFiles] wordpad.exe mswrd6.wpc mswrd8.wpc write.wpc to this [SourceDisksFiles] mswrd6.wpc = 1 mswrd8.wpc = 1 write.wpc = 1 [WordPadCopyFiles] wordpad.exe mswrd6.wpc mswrd8.wpc write.wpc You should remove [sourceDisksNames]. What does "1" mean? Windows 2000 installer by default understands "1" as 1 = %wkscd%,\cdrom_ip.5,,\i386 <- Professional 1 = %srvcd%,\cdrom_is.5,,\i386 <- Server 1 = %entcd%,\cdrom_ia.5,,\i386 <- Advanced Server 1 = %dtccd%,\cdrom_id.5,,\i386 <- Datacenter Server which means that the files will be copied correctly regardless of the edition of Windows 2000 you're using. And CD label also won't matter at all Anyway, I prepared a corrected version of this update which includes the corrected wordpad.inf. It can be slipstreamed from HF folder and no changes have to be made further. Windows2000-KB973904-v2-x86-ENU.EXE Also check this post for a corrected version of KB975560

Yes, CDROM_XX.5 is needed but you shouldn't use CDROM_IP.5 because it's only for Windows 2000 Professional. Server versions are different - CDROM_IS.5, CDROM_IA.5, etc. It's better to change it to CDROM_NT.5 in order to have it work with all editions of Windows 2000. [SourceDisksNames] 3 = "Windows CD",\CDROM_NT.5,,\I386 Mmhh, what if I actually want it to be installed? What is going to happen? If you want to have it installed then you should use HFSVCPACK_SW1 The update has different structure and cannot be directly slipstreamed from HF. Well, actually probably can but a lot of unnecessary files will be copied to i386 folder.

As no one has replied I believe that Gurgelmeyer didn't share his tool with anyone... but I have another request - does anyone have IC.exe (Internet Components) and DX.exe (DirectX) packs which were available to download by Gurgelmeyer? I would be very thankful if you could share them

June updates are up and I wonder if this update (2518295) affects Windows 2000 Server too.

June 2011 Updates: - KB2446704-v2 replaced by KB2518864 - KB2478658 added - switchless installers updated

.NET Framework updates KB2518864 and KB2478658 apply also to Windows 2000 (even though it's not mentioned on the M$ site).

Sfxcab.exe cannot be obtained in a legal way so in order to make a hotfix just follow the tips given above. WildBill wrote a quick manual too.

Basing on this post by Inki I managed to "correct" the DirectX update and I'm working on getting the Wordpad one to work too. The point is to be able to slipstream them using HF folder. 975560 - I corrected the header so it can be slipstreamed from HF now (no problems during text setup when copying files). Windows2000-DirectX9-KB975560-v2-x86-ENU.exe Tested in HFSLIP and tested in text setup - no problems occur when copying files.

Update Rollup 2 is almost finished but I'm struggling to separate Server-only and Professional-only (there is just one - KB951748 and it's a pain in the neck...) updates. Actually, it's very easy to edit the update.inf to install specific files according to Windows edition BUT HFSLIP slipstreams all files anyway. That's why two versions of UR2 have to be created if you don't want server-only files being slipstreamed

Update Rollup 2 BETA3 (KB891861-UR2) ready Changelog: BETA3 - Update Rollup 1 (KB891861-v2) added - catalog files are installed - filename changed BETA2 - Windows Installer 3.1 included (KB893803-v2, KB927891) - Web Folders update (KB892211) included Known issues: - Windows Installer 3.1 not yet included (KB893803-v2, KB927891) - KB951748-V2 not yet included - KB958470 not yet included - KB974571 not yet included - KB979683 not (yet?) included - Server updates not included - catalog files (*.cat) are not installed

I uploaded a package which contains almost all HBRs from bristols' page. This is not a Rollup, just an archive with updates. Win2k-HBR-20110613.7z (127 hotfixes) I hope you can save time by downloading this. Some filenames may be different (Windows2000-KBXXXXXX instead of QXXXXXX but you should just look at the KB number).

Update Rollup 2 BETA2 (KB742742-BETA2) ready Changelog: - Windows Installer 3.1 included (KB893803-v2, KB927891) - Web Folders update (KB892211) included Known issues: - Windows Installer 3.1 not yet included (KB893803-v2, KB927891) - KB951748-V2 not yet included - KB958470 not yet included - KB974571 not yet included - KB979683 not (yet?) included - Server updates not included - catalog files (*.cat) are not installed I rebuilt the entire thing using a batch script which allows me to automatically merge hotfixes except for the update.inf files which I had to merge manually. Nevertheless, the process is much simpler now and I'm able to work much quicker than before Also the probability of making mistakes has been much lowered thanks to the script.

I don't know if it's me doing something wrong or the script is wrong but I tested it on 3 different systems (w2k adv srv, w2k pro, xp pro) and always got errors... :/ On the other hand, I've been using SNMSynch with no problems here.

I get this when trying to run the script My system is Windows 2000.