MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically.

Share this post

Link to post

Share on other sites

No file was replaced in C:\WINDOWS\OPTIONS\CABS, because AFAIK this directory is only used for backup.

If I am not mistaken files in that directory are used by the windows installer instead of the same files that are in the cab archives so it's possible to reinstall without downgrading anything if all the newer ones are in that dir. (I haven't installed/reinstalled since many years though so I might be wrong eventually.)

Share this post

Link to post

Share on other sites

Ok then I understand now. The title of this thread is very misleading as it gives the impression you've installed the SP3 which you did not. Furthermore, since you've reverted back all the files from the SP3 you've updated manually, there is IMO not a chance that the SP is responsable for the problem and you perhaps shouldn't make a thread with a title saying so categorically there is a bug with it. Something else must have hapened to your system and I have obviously no clue what it is, good luck finding it out.

Share this post

Link to post

Share on other sites

gerislamico may well be right... and in case he is, I cannot resist telling you: "I said so!"

- usbser.sys 5.1.2600.5512 (from XP-SP3)

Well, Drugwash, IMO what blorked your system was the .inf inside USB20DRV. Of course the files it contains are OK for your system, provided USBSTOR.INF is edited to load WDMSTUB.SYS with USBSTOR.SYS. Now, adding the untested (AFAIK) USBSER.SYS from XP SP3 didn't help any, either. Fact is, I tested it with WDMCHECK.EXE, and it turns out to have the same 3 unsatisfied dependencies that the USBSTOR.SYS (v. 5.0.2195.6773) from USB20DRV has. On the bright side it means it should work, provided it's also loaded with WDMSTUB.SYS, and this means finding the .inf that sets its registry entry and editing it too. The downside is it may be more than one .inf... USBSER.SYS is for the USB virtual serial port, which is mostly used to support USB modems, AFAIK. Here's a screenshot of WDMCHECK's output:

I *think* the relevant file is USBCDC.INF, which must be edited in 3 places...

Share this post

Link to post

Share on other sites

I *think* the relevant file is USBCDC.INF, which must be edited in 3 places...

Maybe a good idea to update USBCDC.INF. gerislamico also found this was not the problem but USBEHCI.SYS was the cause (this post). I will probably put back the WinXP of USBSER.SYS version since this was not the actual cause. Please note the Service Pack is set to load WDMSTUB.SYS automatically so we don't have problems in the future.