Several inbox USB drivers may not get updated on upgrade from Win7 RTM to Win7 SP1

When upgrading from Windows 7 RTM to SP1 on a clean Windows 7 RTM build, binaries such as usbport.sys, usbehci.sys and winusb.sys may not get updated. Machines that have INF files from OEMs to install USB drivers with a custom description will not get affected. This issue doesn’t exist if you use a slipstream version of SP1.  A new update will be released very soon to address this issue.

This issue manifests if two INF files refer to the same binary. So far we aware of only USB drivers being affected by the SP1 upgrade process because of the way USB INF files are structured. In the USB case, usbport.inf and usb.inf both refer to usbhub.sys. Depending on which INF gets serviced first the other INF gets ignored, and that leads to a mix of RTM and SP1 binaries. As far as we know, this hasn’t lead of any system crash because the fixes to these binaries don’t have any cross binary dependency.

Comments (10)

  1. I've seen several users in the Technet Forums which had USB device errors (yellow icon in the device manager) because of this issue.

    The fix was to run this Tool:…/7601usbfix

    Is this fix recommend or not?


  2. mpbk says:

    Thanks for looking into this!  I appreciate it!

  3. USB Blog says:

    @Andre: We can’t officially recommend any third party tools. So whether the fix posted on this website is good or not is something we cannot comment on. Sorry.

  4. but why does it fix USB issues which only occurred because of the  USB RTM file installed, instead of the Sp1 files?

    Have you read the topic of this other forum? This fix works for the users.

  5. Anonymous Coward says:

    The main problem is that the drivers can become unsigned if the user does a post-SP1 cleanup (e.g., via the disk cleanup wizard) since that cleanup removes security catalog files that are normally safe to remove, but since the binaries were not properly updated, they needed those old catalogs.  This results in the driver becoming unsigned and a loss of functionality.

  6. Danial says:

    "This issue doesn’t exist if you use a slipstream version of SP1."

    This is false. Several users have had the EHCI controller not function correctly from a fresh install of the official integrated media and have had to run the tool provided by MDL.

  7. Z says:

    Andre – a fix is also to uninstall any *one* USB 2.0 host controller (preferably one with no devices attached), then scan for new devices.  This will reinstall the host controller, update the driver, and doesn't require any user devices to be reinstalled.

  8. Jeffrey says:

    I was able to fix it by choosing the "unsigned" driver and saying "Update this driver" "local" and choose from a list. Updating with the only choice given fixed it for me.

  9. Olivier says:

    Do you have any ETA for the update? Also is there a knowledge base article about this?


  10. Today the Update KB2529073 was released on Windows Update which fixes the issue:…/en-us

Skip to main content