Well 2533552 just fixes the actual cause of the issue, it won't help people who have already hit the USB problem from the SP1 install.
This time it gives a different error text:\ -------------------------------------- KB2529073 and KB2528984 USB Driver fix -------------------------------------- 'pendmove.exe' is not recognized as an internal or external command, operable program or batch file. 'pendmove.exe' is not recognized as an internal or external command, operable program or batch file. 'pendmove.exe' is not recognized as an internal or external command, operable program or batch file. 'pendmove.exe' is not recognized as an internal or external command, operable program or batch file. 'pendmove.exe' is not recognized as an internal or external command, operable program or batch file. 'pendmove.exe' is not recognized as an internal or external command, operable program or batch file. 'pendmove.exe' is not recognized as an internal or external command, operable program or batch file. You now need to reboot to complete the fix process. Please do so as soon as it is practical. Once Windows has restarted the latest available USB drivers should be installed and utilised correctly. Press any key to exit...
hmmm, how are you actually running the program? you have to extract it from the archive, you should never run a program from an archive unless its a singular file and there are exceptions to that as well.
Obviously I extracted the file, ran the cmd as administrator. I checked the directory windows\system32\drivers and see a whole bunch of sys-files ending with ".new". I suppose that this happened with "USB KB2529073 Fix v2d".
To burfadel: Just to be sure I logged on as administrator and ran the cmd as administrator but again got the error messages that files ending in new cannot run in windows 32. Nevertheless with my previous message we might be getting somewhere? I tried the following: in windows\system32\drivers I renamed the affected files to .bak previously taking full administration rights and deleted the ".new" ending on the files that had that ending. Now all ubs-sys-files state the correct version. I hope this helps you and others.
Sorry to be like a pain in the ... but opening the downloaded file with 7-zip I get an error message of unsupported compression method. The file could be corrupted and I downloaded the file 4 times but always get the same error message.
Thats correct, only two files in the new one all the functional stuff is contained in the .cmd file. If you are on x64 and used V2, then you are fine! All subsequent versions from v2a to v2f were to try and resolve issues regarding x86. The outcome of V3 is the same as V2, but for future use it would probably be beneficial to use V3. Since the issues were relating to the third party pendmove apps, I did away with them and now the function of pendmove is done directly. I believe that some people may have been trying to run it directly from the archive which before was an issue but should be fine to do now Basically here's the rundown of what has happened with the changes: V2: added usbccgp.sys and usb.inf to the fix V2a through V2f: various changes to the script to try and get 32-bit support working V3: Did away with using third party apps and now does the function of them internally. Should now work on both platforms! So I apologise for all the different versions, but sometimes the simplest things are hardest to work out properly. Afterall, thats the exact reason why the fix is needed in the first place! Microsoft releases an official fix and still can't get it right
ok, I understand better and does not apologize, after all the work you do me, I integrate the Updates to ISO and I do some cleaning in the winsxs folder (with rt7lite), I'll leave the files as shown I'm not sure that changing the files manually be a good thing (I do not know if everything is changing, everywhere)
Hmmm, thats interesting! it seems only 32-bit is affected by this issue? It may be a permissions things? I could see no reason for any version of the fix to not work on x86, almost to the point that I have to say its either something to do with the x86 install or x86 itself!
New updated ISOs on MSDN/Technet with KB2534111 integrated... ill remove it from repository (or move it somewhere) on next update... BTW anyone have technet/msdn account to give me download links on PM for Ultimate x86/x64 ? EDIT: nvm got isos!