Jump to content

USB functional patches for Win2000 after SP4 and R1

Recommended Posts

Hello dear Windows 2000 users!

This thread is an (ambitious...) attempt to list all patches released after SP4 and Rollup 1 to improve function, not security, of the files implementing USB on Win 2000.

These patches aren't highly publicized by Microsoft (most were intended for an SP5 that was never published) and don't appear in automatic updates, so such a list isn't very common despite the patches may improve USB function for some users.

Microsoft's warning in these patches' descriptions is that they haven't been tested enough, so one should use them only if experiencing the specific undesired behaviour that a patch cures. Anyway, at least we'll know they exist.

To find the patches, I googled the filenames through support.microsoft.com in English only, which did take some time - hopefully saved to other users. This method certainly has limitations, so additions, improvements etc are welcome.

The wise users of Gurgelmeyer's unofficial SP5 have all these files already in their latest possible versions - at least, this is what I saw in its i386 folder without having installed the uSP5. The only exception is Usbport.sys at v6926 instead of v6941, which is hard to explain, as only KB843503 brings Openhci.sys v6940 present in uSp5 and this KB843503 brings Usbport.sys v6941 as well. As a consequence, the uSp5 may benefit from KB843503.

In the coming table, I shortened some repetitive numbers... So

1234 means version 5.0.2195.1234

123456 means KB123456 corresponding to these descriptions and patch file name:



(you must replace ENU by your language, like DEU ESN FRA PTB ITA, but should better stick to en-us!)

The first version number is observed in an (old) Win2000 with SP4 and R1 that has all security patches up to January 2009 but no function patch more recent than R1 - that is, a rather common situation. Interestingly, all these files are ENU or ANY on the non-English Win2000 I observed (but ENU patches don't install).

Well, here it comes...

Link to comment
Share on other sites

The table is plain text to help you copy it. In order to display your copy properly, you'll need a fixed width font (like Courier new) where you paste it, for instance an Html document or a text editor (Metapad does it).


Hidusb.sys and Usbser.sys exist only in Driver.cab on the observed Win2000.

Link to comment
Share on other sites

As a consequence of the version numbers above, and IF I understand it properly, one only needs the following updates to get all latest files:

836111 838417 838989 843503 883528 890202

which supersede

817765 823086 838771 838921 841880

836111 solves a very specific problem and nearly everyone should be able to neglect it.

Similarly, having 841880 instead of the uncommon 890202 should be as good for nearly everybody.

These files aren't easily available at Microsoft, but people running an ENU W2k may get most of them by searching for the file name, like


and so on.

Link to comment
Share on other sites

Thanks for this list. I did a similar list some time ago when we actually needed some of these Hotfixes.

However, at that time, I missed 843503 (which seems to completely replace the earlier 829759).

What do you mean by "These files aren't easily available at Microsoft"? Once the numbers are known, all of them are easily available on request by email with just a few mouse-clicks. You've already done the hard part, which is finding the KB numbers.


Link to comment
Share on other sites

Thank you so much, James_A! :thumbup

You are perfectly right, these patches are sent by Microsoft for free. I believed it would require a special maintenance contract after 2005, but my Oem W2k without Wga could receive the patches without any other condition.

I was disappointed that Microsoft had written patches and didn't release them with the planned Sp5, but giving the patches easily and for free improves their image quite a bit. Knowing that, incomplete testing is indeed a credible reason not to release the patches more widely.


The contents of several patches differ from the KB descriptions which were the source for my table.

KB838989 has Usbd.sys v6935 and Usbport.sys v6926 - both are more recent than announced. Maybe we shall understand KB838989 as a rather general-purpose refresh for Usb on W2k, though it isn't the latest possible update; Microsoft distributes it more widely, without the "little tested" warning and under Wga.

KB838417 has Usbd.sys v6935, Usbhub.sys v6935 (older than announced) and no usbser.sys (not installed anyway on my W2k).


I missed KB829759 just because it put "for W2k Sp3" and this reason was bad. The files it brings are newer than those brought by Sp4 and R1 - but older than KB843503, yes.


I've neglected KB836111 but have now the other five most recent ones. I'll try them and tell you what they've installed and if I can eject my CF cards after that.

Link to comment
Share on other sites

Now, I've received from MS all patches I wanted, installed normally since they had the adequate language, and tried them.

A general observation is that the versions and even the number of modified files that ship with a patch (or hotfix) don't always match the description in the KB (knowledge base). The versions seem to have evolved over time without updating the description. This would explain why, for instance, Gurgelmeyer's unofficial Sp5 contains files and files combinations that don't exist now in February 2009.

What does work is that patches install all the files they carry, provided these are of a more recent version than the one in place.

From all the patches I tried (basically, the ones that bring the newest files +841880 as an alternative), none did what I hoped: allow to eject a CF card from a "9-in-1" reader from the user session. Only the administrator can do it. I hoped the patches for Usbstor.sys would bring this extra refinement - no, they change nothing here. Even right-click on the Eject icon from the taskbar, and the the "detailed" option in the subsequent windows, shows all places from the 9in1 and closes them all, whatever I highlight.

More disturbing: with these patches, new instabilities have appeared. One blue screen when hot unplugging the Adsl modem as it was still trying to synchronize on the line; this modem as well as the "9-in-1" reader not always detected when plugged; a user session that doesn't close... Things I hadn't seen in 2 years, using W2k in an often cavalier fashion.

So Microsoft's recommendation now looks reasonable: these patches "aren't fully tested" as they say (are still bugged I say), and use them only if you experience the problem they solve. And a W2k incorporating all these patches isn't necessarily better than without them all, quite the opposite.

I haven't tried each one in-depth, except for ejecting the CF. MS releases KB838989 without the accompanying warnings, so this one could be of higher quality. And to install W2k from a CD drive on Usb, the relevant patches are 823086 (replaced by 890202) and 838417 (replacing 838921).

Edited by pointertovoid
Link to comment
Share on other sites

Ciao Jaclaz!

Benchmarked the FAT32 on USB sticks: no.

- To go fast, use a CF on a P-Ata adapter or in an Udma reader, not a Usb stick

- I've already seen three broken Usb sticks (from "innocent" users), but none of my many CF (who have experienced heavy and exotic uses).

- I also use two Win95b around me, which work very well and will stay indefinitely, but don't have Usb. They access CF through P-Ata and Pcmcia.

So I have no Usb stick - not a single one.

I've benchmarked a lot, but on CF with a P-Ata adapter. In short:

- Mlc is very slow on small files, Slc is faster there, especially when writing, and HDD are generally better. This corresponds to the experienced speed, and is best measured with Atto, not at all with HdTach nor HdTune.

- Filesystem makes no difference there, PROVIDED THAT cluster size is the same

- CLUSTER SIZE changes speed an awful lot on Flash memory. This favours Fat16. Have a look at Dandu.be if you read French - others exist in German and English.

- Drivers don't change CF speed significantly on P-Ata.

Conclusions with Usb sticks may be different.


Link to comment
Share on other sites

I've tried separately the various functional patches for Usb. In short:

- Most work without obvious flaws, but what they bring doesn't correspond to my computer

- KB838417 is bugged and should better be avoided.

Not only does KB838417 produce a blue screen each time I disconnect my Adsl modem (even with proper ejection before), it also lets my Cdrom reader make from time to time the same noise as during power up, lets the mouse scroll go mad, and partially closes Explorer plus TClockEx (a better clock for W95-98-98se-Me-2k, very nice). To produce such varied nonsense on a computer, the most probable way is to write at irrelevant locations in the Ram - something a driver is probably allowed to do.

I also tried the Usbhub.sys v7006, which is announced in the knowledge base KB838417 and is integrated in Gurgelmeyer's unofficial Sp5 (the KB838417 patch brings v6935, and also Usbd.sys v6935 which KB838989 and KB843503 already bring). For that, recreating with Cabarc a modified Drivers.cab was necessary. It has similar bugs. So to users of uSp5 who would experience similar mishaps, I would suggest to bring Usbhub.sys back to v6689 in Drivers.cab, DllCache and Drivers.

By the way, I find a bit disappointing that several editions of Usbhub.sys display the same patent bug. The bug probably explains why the patch doesn't contain the file versions announced in the Knowledge Base - but it didn't help. And as the Sp5 was suppressed, there was logically no money left to correct Usbhub.sys. Such bugs explain why Microsoft tell to use the patches with caution and only if experiencing the related problem.

I couldn't find a better version of Usbhub.sys : v6883 from KB838771 doesn't address the issue of installing W2k from a Cdrom reader on Usb, and v6884 from KB838921 isn't publicly available. No other patch for Usbhub.sys seems to exist.

So to people willing to install W2k from a Cdrom reader on Usb, the suggestion would be to find a P-Ata Cdrom reader. Has anyone tried from a S-Ata Cdrom reader?

Edited by pointertovoid
Link to comment
Share on other sites

And now, an updated version of the table, with the missing KB829759 and more indications.

The table is plain text to help you copy it. In order to display your copy properly, you'll need a fixed width font (like Courier new) where you paste it, for instance an Html document or a text editor (Metapad does it).

Again, 123456 means KB123456 and 1234 means 5.0.2195.1234

PAY is shorthand for "not publicly available", WGA for "no caution warning" and BSOD for "better keep away".


NB (by dencorso): When requesting KB838417, make sure to select the so-called "SP5" release, not so-called "latest" release, which contains earlier files and omits usbser.sys, as pointed out by Bristols here. I corrected the tables to reflect the contents of the "SP5"release, but poinertovoid tested the "latest" release, instead, because the existence of two different versions was not known at the time, so perhaps the "SP5" version is useful and does not cause BSODs... This, clearly, warrants testing.

Edited by dencorso
Link to comment
Share on other sites

  • 3 years later...

NB (by dencorso): When requesting KB838417, make sure to select the so-called "SP5" release, not so-called "latest" release, which contains earlier files and omits usbser.sys, as pointed out by Bristols here. I corrected the tables to reflect the contents of the "SP5"release, but poinertovoid tested the "latest" release, instead, because the existence of two different versions was not known at the time, so perhaps the "SP5" version is useful and does not cause BSODs... This, clearly, warrants testing.

Actually pointertovoid tested both sp5 and "latest" and both didn't work for him.

Out of all these updates\hotfixes the following ones seem useful:


The rest are superseded by these and the buggy 838417 is omitted. Pointertovoid mentions problems only with Usbhub.sys v7006 but there are three files available in the hotfix:

usbd.sys 5.0.2195.7008
usbhub.sys 5.0.2195.7006
usbser.sys 5.0.2195.7006

Personally I'd avoid using all three of them just in case (one of them is buggy and the two others are connected with it so you never know...). If you're using Gurgelmeyer's USP 5.1 you may want to replace them like this:

usbd.sys 5.0.2195.7008 -> usbd.sys 5.0.2195.6935 (843503)

usbhub.sys 5.0.2195.7006 -> usbhub.sys 5.0.2195.6689 (SP4)

usbser.sys 5.0.2195.7006 -> Usbser.sys 5.0.2195.6655 (SP4)

Replacer is a very good program to replace system files manually.

Edited by tomasz86
Link to comment
Share on other sites

  • 3 months later...


It may be old but nothing has changed since then so it's still relevant and will probably be relevant in the future too unless someone manages to replace/modify the files in order to make them compatible with USB3.0 drivers.

Link to comment
Share on other sites

  • 1 month later...

@pointertovoid ... I seem to remember you are using 2k on ICH10 chipset ... ICH10 handles the USB bus ...

have you had any luck (or problems) trying to boot from a WinSetupFromUSB setup iso from a USB flash drive?

I was wondering where to post this ... this seemed best, because it kind of gets into usb drivers for 2k

I have 2K on top of a ICH10 P43 chipset (msi p43neo3f core2duo)

bios has all SATA hdds read as straight IDE (no hotswap or raid)

intel XP drivers install no questions and fingers crossed ... no problems so far

bios for usb is set to recognise legacy USB (choices are enable or disable)

disable prevents bios from scanning USB bus for flash drives

(if disabled, once loaded 2k will see them fine, but for safety USBs can't selected from a boot sequence)

@tomasz86 ... I remember a list somewhere where Update Rollup2 or UUrollup-v10c had included some of the USB drivers from the SP3.CAB cabfile for XPpro?




they were on the list, but I think they were removed from the files and you went with the straight 2K version of KB838989

that was the patch for not losing contact with a USB during power cycles (i.e. during loading phase of booting)

the same KB number gives different filesets for XP and 2K, but both sets should address the same issue (obviously)

I'm asking because I'm running a script that will almost restore an image of a working 2K system to a UFD ,,,

when I restore an image of my 2k system to UFD, the UFD boots, 2K loads in text mode, loads vga mode, but bsod's me with a "7D" when it changes over to logon

the techie at terabyte (it's their script) had tested it in 2k and recalled that it worked ... a 2K image can boot from a UFD and run

I'm wondering if it might be the 2k USB drivers and the ICH10

(we usually think ICH10 for AHCI or RAID, but ICH10 also controls the USB bus ...)

so loading the XP drivers in 2K might make a difference for 2K on ICH10 mobos ...

when I boot parted magic from USB it runs fine ... thus, bios plus ICH10 plus linux drivers are "all systems go"

when I try to format UFD using WinSetupFromUSB with 2k, the program doesn't see the USB, even to select it as target for formatting ... yet 2K manager will format it, as will everything else I've tested

thus, I'm trying to get WinSetupFromUSB to work, but I have the feeling it might be the 2K drivers plus the ICH10 ...

any reason you pulled the XP files from the UUrollup2 and the v10c?

how do I install them to use them? (I have XPproSP3 ... they are in SP3.CAB)

I tried registering them but regsvr32 answered with ... file was loaded but could not find initial entry point ... not a dll or ocx ... something like that

do you think it might be the 2K drivers + ICH10 that blocking boot from USB in windows 2k?

Edited by Molecule
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Create New...