One last thing I will try tomorrow is ask a friend who has a technet account to see if he has any luck ordering the fix
it's good for Update "USB" (file version is 6.1.7601.17591), it is with another Update that I had a problem, thanks
Why isnt it a complete replacement for KB2484031? It replaces all the files in KB2484031 with new versions.
@burfadel hey burf', I'm running into a wierd (throw my PC out type) problem with VC++ Redist Installer.cmd. It worked fine on fresh installs included in a synchronous first logon cmd file: Code: CALL D:\Win7(x64)_Microsoft\RunTimes\"VC++ Redist Installer V2a\VC++ Redist Installer.cmd" and, then, for some unfanthomable reason known only to my PC it started to kick out during subsequent fresh installs: Code: One or more of the installers is missing. Please do not delete any of the folders! A redownload of this installer will be required. then, if I immediately run when I arrive at the dektop: Code: D:\Win7(x64)_Microsoft\RunTimes\"VC++ Redist Installer V2a\VC++ Redist Installer.cmd" it kicks out: Code: If package is already installed, package will be reinstalled. This is beneficial in the case of the package needing to be repaired for some reason. and installs the runtimes for the first time. I've redownloaded the package three times, changed absolutely nothing and am doing nothing differently between when the cmd worked and when it commenced kicking out the error. Any ideas?
I'm beginning to wander if M$ actually even prepared that fix they're refering to in the download link. I got the hotfix is unavailable for both x86 and x64 after the requisite bulls**t runaround. ....sickening I tell ya'
The script is based on a relative path basis, so when you run: Code: CALL D:\Win7(x64)_Microsoft\RunTimes\"VC++ Redist Installer V2a\VC++ Redist Installer.cmd" it is running the script, but the script will be located back to whatever folder you are running the 'call command from. So, to call it correctly you will need to change it to: Code: pushd "D:\Win7(x64)_Microsoft\RunTimes\"VC++ Redist Installer V2a" CALL D:\Win7(x64)_Microsoft\RunTimes\"VC++ Redist Installer V2a\VC++ Redist Installer.cmd" popd In the case that you can't do that, you will need to make a sub batch file with those commands in it and call that instead
Thanks mawn, I will just add all of that to the cmd file and see how she goes next install and report back-many moons I hope.
List updated, i removed KB2484031 BTW... i think usbport.inf in KB2484031 was broken and now they are fixing it with new usbport.inf so even if it updates less files it properly updates all usbport.inf components and this is most important thing, not number of files updated.... EDIT: even more if you check winsxs folder you will see it even forces original versions of missing files, somehow i think this is for a reason... rememeber KB2484031 is basicaly BROKEN and in original form doesnt update ANY files so lets not base any assumption how usbport.inf update should look like on broken update. Also if you install KB2528984 before KB2484031, it says for KB2484031 that its not applicable and that should be good enough for us.
F5! damn 10 char edit: it was updated btw, but sometimes browser doesnt detect filechange so it doesnt load new file but it loads it from browser cache, so if you notice changed date just manualy refresh it.
Comes up now Also, SoLoR can you recheck updates KB2484031 and KB2528984? Update KB2528984 does not contain new version of usbd.sys, usbohci.sys, usbuhci.sys whereas KB2484031 does contain newer versions (than Windows 7 RTM anyway). Its true update KB2484031 does not install after KB2528984, but I believe thats because of the usbport.inf issue. The file usbuhci.sys is needed on all computers since its for the usb 2.0 universal host controller, which is the more 'standard one' (and you'll find in the device manager you'll have a lot more universal controllers than enhanced controllers) The usbehci.sys just covers the usb 2.0 enhanced host controller (intel proprietory). Also the USB root hubs utilise usbd.sys, so by not installing kb2484031 you are missing out on the updated controller and hub drivers the update kb2528984 just covers a specific issue with the Intel USB (usbehci.sys). I'm not sure, but I'm assuming if you already have kb2484031 already installed that kb2528984 will utilise the newer versions of the 3 files that aren't updated. If not, the fix still applies. If you just use KB2528984, basically all the controllers will still be using the RTM usb driver usbuhci.sys (6.1.7600.16385) for the Universal USB controller and USB root hubs usbd.sys (6.1.7600.16385) and and not the updated ones (6.1.7601.21624)... Actually its more a mix of RTM and updates files, whereas installing KB2484031 at least you get rid of those 2009 dates files It would be better to have a mix of sp1 hotfix USB drivers than sp1 hotfix drivers and RTM drivers... (the controllers and the hubs etc use multiple system files). So, KB2484031 should be installed first, then kb2528984, and then the kb2484031 V2 fix of mine should be applied... Hope that makes sense! And yes its stupid, but just confirmed the usbd.sys, usbduhci.sys installed with KB2484031 aren't utilised after installing kb2528984, but are utilised if used with the v2 of the KB2484031 fix. DON'T use the original fix. Its Microsoft's mess, just thought I'd point that out! Just wish that elusive hotfix becomes available so we can forget this mess! If you don't update usbd.sys and usbuhci.sys, any issues since Windows 7 rtm relating to those specific files will still be present.
Just so people know, I've updated the old update remover, but I haven't listed kb2484031 for removal due to the issue described in my last post.
There is nothing to recheck really, just one or the other update is more broken then the other. And we cant be sure 100% sure which one is it, only thing we know for sure is KB2484031 is broken but it suppose to update more files and KB2528984 works as it should but updates less files (maybe they forgot to include missing 2 files?). Its just a judgement call between 2 hotfixes and since im having this list by components and not actual files they update i removed broken update. And obviously MS hotfix system is also considered by components and not actual files or you would be able to apply KB2484031 even if you apply KB2528984 first. I personaly think both are bit broken, but oh well... i wont start to mess things up now because of 1 hotfix and 2 files that should or should not be updated as well... component is component and usbport.inf component as a whole in KB2528984 is newer then in KB2484031 and thats good enough for me atm and we will see with next usbport.inf update which hotfix was more broken.
I agree, the new update should have included those other files, but since it just related to the EHCI and not the UHCI and ports they didn't include the usbd.sys and usbuhci.sys files (the usbohci.sys I believe related only to USB 1.1 controllers). In any case, I've left the removal of KB2484031 out of the superseded update remover, so at least people have the choice of installing kb2484031 + kb2528984 + (any other fixes) + reboot + using the fix (to update the UHCI and port driver) + reboot, in that exact order, and just installing update KB2528984 (plus any other fixes) + reboot. Microsoft has made a real mess of USB with SP1, to me the elusive update should be pushed to Windows update as this is an issue that affects quite literally everybody who has installed SP1.