Actaully this applies to all people with SP1 and have installed KB2484031. On a SP1 image, even a proper one from Microsoft, the USB driver bug is still there. The driver bug appears in two separate ways: - USB drivers, mainly USBehci.sys and USBport.sys, do not update to newer versions. If SP1 is installed and RTM USB versions of these files are 'available', the RTM versions are utilised. If installed update KB2484031, the newer KB2484031 files are not utilised, only the existing RTM versions OR the SP1 versions if you started with a pre-integrated or true SP1 iso from Microsoft. - The 'driver file details' under device manager do not report the correct versions for individual files, namely USBport.sys and USBehci.sys. These versions should not be confused with the actual device INF driver versions which is reported correctly. The way of finding the version of usbport, usbehci.sys etc is by navigating to c:\windows\system32\drivers and checking for yourself. This is only due to the bug, and believed only to affect USB driver files. Please note that if you haven't installed KB2484031, it just means you are either using the RTM USB driver files or the SP1 USB driver files. It does not mean you are SP1 USB driver bug free!!! this modified version is so anyone (regardless of installation type) can utilise the even newer post SP1 USB drivers if the post-SP1 update KB2484031 is installed. This USB driver fix tool is not dependent on you having used the other one if you are on a system that required it. It can be used in any case where SP1 and KB2484031 is installed I hope that makes sense! but basically no one is SP1 driver bug free (until Microsoft gets around to releasing a fix), you can just look at it as if you used a pre-integrated SP1 iso the issue (point 1, not point 2 in the above list) is 'masked' until the USB driver files are updated again such as when you installed KB2484031
Thanks for the explanation. I just checked usb drivers in C:\Windows\System32\drivers and the file versions were all 6.1.7601.21624 so I guess the correct version of files are already installed however please note that I installed my windows from a dvd integrated with KB2484031. Maybe manually installing the mentioned hotfix causes that bug. However file versions reported in device manager were wrong just as you mentioned. Does this mean I am affected by this bug?
Note: USB bug is not present if you integrate your updates BTW Yea, never use the Device Manager to determine what file version you have, its wrong sometimes
This is indeed true... before today i had integrated that USB hotfix and files versions where correct, but today i decided to try to reinstall all hotfixes with forcing them in to LDR branch and after i first removed all hotfixes and later installed them again, usb drivers versions files where wrong.
me I have version 6.1.7601.17527 for the 2 files, but I will integrate Updates to ISO, so I should not have this bug problem? thanks
It seems its a 'in some situations' thing. I believe integrated kb2484031 is ok, but it seems in other cases its hit and miss. At first I thought it might have been a pkgmgr.exe install thing, but on a system that I know the installer wasn't used on (instead installed via running the .msu file as normal) as they only wanted specific updates, the files weren't updated. This USB issue is a strange one! Its this very 'hit and miss' reason why Microsoft probably haven't released a fix for it yet, otherwise it would be as simple as releasing an update on Windowsupdate that just included the proper USB files (or copy them over like the USB fix)...
The reason for this as i explained in the other thread is that microsoft didn't update the MUI files which contain the resources for those files...... you can delete those files anyway if you really want to as the OS just pulls the resource info from the dll itself in that case,
I'll do a clean install (by integrating the drivers) is that I can integrate these 2 Updates (KB979350 and KB981070) without problems? they are not yet on the list of Solor thank you
There will probably be lot more of them... im not even half way thru: Code: mih microsoftkbs # diff new/ old/ -q | grep new Only in new/: 2444142 Files new//2446026 and old//2446026 differ Only in new/: 2450944 Only in new/: 2460971 Only in new/: 2465408 Only in new/: 2468345 Only in new/: 2470853