Thanks - let's hope that this works. Twenty four hours to run a backup from either Acronis True Image Home or windows 7 backup is entirely too long - epecially for an approximately 66 GB file.
It worked fine for me. I've checked the file dates after the reboot and all is in order. Note that your Browser (IE9) may hiss at the downloaded file. I ran it anyway after checking the hash and walaa. One interesting side note, Originally I did a "repair within install" to clean up a mess made previously then updated to SP1 and I got the bug. SFC /Scannow said all was fine. Here's hoping that was the only one! Many thanks to all who made this fix possible....
Thanks to Enigma256 and all the others for this fix. It should be stickied. It would have saved me a lot of problems and hours of frustration. I learned it the hard way but after reinstalling from scratch and updating with SP1 I applied the fix which solved the problems I had previously. So thanks again to all the Gurus.
I found this thread via google in the archive of this forum. For people who did the same: Note that the batch-file is not correct in archived view, spaces appear in the filenames, remove the space from 31bf3856ad364e35_6.1.7601.17514 (four times; spaces got between the 55th and 56th character of the line) Great fix, thanks! I was about to reinstall windows.
Actually, this is correct. As enigma pointed out, there isn't an old version of the driver in the slipstream, so you can't have the old version. Furthermore, the problem is that the driver doesn't get updated to the new version and you remain on the version you had prior to SP install. If you're clean installing SP1 from slipstream, there isn't an old version to get stuck on.
No, its false because it still occurs. the official slipstreamed ISO fails to copy the correct catalogue files over in some scenario's.
WoW, I came to some problem that prevent my external(usb) hard driver from recovering when woken up from sleep, and also minor problem that shut down my external driver after some time, regardless whether being written or not. The fix solve my problem. Why not this awesome topic pinned?
What scenarios? There aren't any incorrect catalogues on an official slipstreamed install. There is one version of the driver, and one catalogue.
Yeah I pointed that out in the hotfix repository thread, however the request page still doesn't work! I really think this should be an update pushed onto Microsoft Update, not just as a hotfix. Lets face it, most people who have Windows 7 at the moment don't have a slipstreamed or original Microsoft ISO SP1 install, meaning they have installed SP1 separately either from the standalone or through Microsoft/Windows Update. What that means is most people are affected by this issue, its not a typical hotfix where there is only a single digit percentage of computers affected.
You should use the official MS fix for this. All users will get the fix from WU at some point anyway.
The official MS fix doesn't completely work! if you check the actual file versions of usbd.sys, usbehci.sys usbohci.sys usbuhci.sys usbuhci.sys, usbccgp.sys, and usbhub.sys under Windows\System32\drivers you will find that not all of them are updated correctly. Also, the v2a version of the script should now work for x86.