So this bug only affects the installer not the full iso's? And we don't have a M$ installer hash, so there is a possibility that the official SP1 installer will have these issues fixed?
Yes. We do have the official MSFT installer hash, and the one leaked via wzor is the "final and official" installer. And none of the hotfixes available via WU addresses this issue. So no, these issues have not yet been addressed in any official way.
Is there an easy way to see if you've been hit w/ this bug? I did an in-place upgrade over my existing Win7 retail installation, using the slipstreamed MSDN iso.
Run this from the command prompt: Code: cd %SystemRoot%\System32\drivers dir usbehci.sys usbport.sys winusb.sys And if any of the files are dated July 2009 instead of November 2010, then you are affected. (Alternatively, you can press the Windows+R key combination and paste in cmd /k pushd %SystemRoot%\System32\drivers & dir usbehci.sys usbport.sys winusb.sys)
I used the standalone installer on 2 systems , both have those usb files dated 2010 and all usb devices ,usb2 and usb 3 performing perfectly .
i just did, and it shows Code: Directory of C:\Windows\System32\drivers 11/20/2010 02:44 AM 343,040 usbhub.sys Directory of C:\Windows\System32\drivers 07/14/2009 11:06 AM 324,608 usbport.sys Directory of C:\Windows\System32\drivers 11/20/2010 02:43 AM 41,984 winusb.sys so only usbport.sys is affected, how should I only update this one file instead of all three of them? thanks
Oops. Sorry, I made a mistake in the post that I just made. usbhub.sys is not one of the affected files, but usbehci.sys. You should check usbehci.sys instead of usbhub.sys (I updated my post with the correction). If you run the batch file in the first post, it will replace all three files--usbehci, usbport, and winusb--with the 17514 version found in the driver repository. So in the case of winusb.sys, since you are already using the 17514 version, it will just be replacing the existing file with an identical file, and it doesn't matter.
Well, SP1 was pushed on Windows update yesterday, and this bug in fact hit my system... Waiting to see if MS puts out a hotfix to correct it before I self-repair, though!
Did any one else encountered this issue after isntalling SP1 using WU? ive had the USB bug on my other OS after upgrading to SP1 using the SP1 installer and the solution here didnt helped to fix the issue, had to reinstall WIN 7.
I have error after run this fix. More popup appear on my desktop. When plug-in usb drive for first use. error about dinotify.exe now I'm revert back to default.
I updated four Win 7 64 bit computers to SP1 today. Three I used the downloaded 903 MB file and one I let WU install it. The results were all the same; the 3 files in question were all dated 2009. I used Enigma256's fix and updated them all.
i have now got word of users of the official SP1 Win 7 + SP1 iso's having the "This device can perform faster" message. and the USB files are not signed. running the batch script corrected the issue for these users as well. also not totally correct, while its true 32bit apps cannot access system32 directly, windows provides the sysnative directory, which provides 32bit apps a method of interacting with the 64bit system32.
After running the batch file, all three files now are the 2009 version. Before I ran the batch file, only one was 2009. Did I do something wrong? How can I fix it?
Just installed SP1 through windows update today and had usbehci.sys and usbport.sys showing 2009. Ran the batch and now everything's up to date. Many thanks.