I was just about to report on that! I believe its because KB2528984 has a usbport.inf build of 21700, and doesn't include usbohci.sys, usbuhci.sys, and usbd.sys. Therefore, installing the new USB hotfix KB2529073 with usbport.inf build 21692 doesn't replace the files because it is 'older'? if you install the new update first, you may be ok. This is still a big stuffup as the new build (with the missing files) USB fix has a lower KB article date. May mean another 'special case' add to the installer/integrator! I'll check further on this theory. Even if they have muffed it again it doesn't matter, just that there will be a v3 of the usb fix
Just confirmed my hypothesis! However, extending on that hypothesis, the newer files in KB2528984 aren't updated either!... So, I'll post a new USB hotfix script which will check for both USB updates, and if present use the latest files from both of them. This is getting a little ridiculous... The next USB hotfix from Microsoft should work, as long as its build is above 21700 and that it includes ALL files, and not just 'oh we only need half the files so we'll only put half the files in' half-arsed measure!
it's normal that the new update for USB is an older version for usbport.inf? KB2528984: usbport.inf - 6.1.7601.17591/6.1.7601.21700 KB2529073: usb.inf/usbport.inf - 6.1.7601.17586/6.1.7601.21692 for me, usbport.inf is still at version 6.1.7601.17591 thanks PS: it may be just what you explain above
Exactly! In other words, a big stuff up. Obviously is doesn't even LDR it :S It doesn't really matter though, the only differences between the 4 usbport.inf files is the version number. The important thing is the USB driver file versions, which I can assure you on your system would not be updated correctly (utilising all the latest versions). I've updated the script and just about to restart to make sure its all good, then I'll post it
thanks for the explanation and what file is it to check the version (I have no usb.inf in system32\drivers)? thanks
Navigate to c:\windows\system32\drivers and put the mouse cursor over files usbhub.sys, usbport.sys, usbehci.sys, esbuhci.sys, usbport.sys, usbhub.sys, usbd.sys and you should see the file versions (move the mouse slowly). If not, right click on each file, select properties, then click the details tab and the file versions should show. The file version of usbport.inf is less relevant as its identical apart from the file version.
usbhub.sys is 6.1.7601.21692 usbport.sys and usbehci.sys, are 6.1.7601.17591 esbuhci.sys and usbd.sys are 6.1.7600.16385 this is normal? thanks
Using the new USB fix tool in the above post, usbd.sys, usbohci.sys, usbuhci.sys are updated from KB2529073, with LDR version 6.1.7601.21692, and files usbehci.sys, usbhub.sys, & usbport.sys are updated from KB2528984 with LDR version 6.1.7601.21700.
No thats not normal. Actually it is with Microsoft's stuff up! but they're meant to be the file versions I have outlined in my previous post if you have KB2529073 and KB2528984 installed . The fix tool corrects the stuffup, apart from USBport.inf if its incorrect, but this file doesn't matter as its identical apart from the file version. The LDR versions are used, as if you have both the updates installed the LDR version would be the utilised one. Besides, LDR versions are 'more fully updated'... If you have both updates installed, the usbport.inf file located in c:\windows\inf should be the 6.1.7601.21700 one. I've added the following info to the post with the fix:
with your USB fix tool: usbd.sys, usbohci.sys and usbuhci.sys are 6.1.7601.21692 usbehci.sys, usbhub.sys and usbport.sys are 6.1.7601.21700 but the usbport.inf file (in c:\windows\inf) is 6.1.7601.17591 and usb.inf file is 6.1.7601.21692 thank you very much PS: it is possible to adapt this script to be able to integrate this "fix" in Offline (for integration in fact) EDIT: ok, there is always the KB2484031 to install, I'll do a clean install to see
Hi.I need info on 6 updates. Do these updates have a x86 version or are they x64 exclusive? Or are they superseded by other updates?: KB2461108-v2 KB2487292 KB2487426 KB2504602-v2 KB2506014 Does this update have a x64 version?: KB2502285
I should point other there was nothing wrong with the original KB2529073 fix, just that the changes now make the fix absolutely complete In fact, what you have after running the fix and rebooting is what should be the case if Microsoft hadn't muffed it!
sorry for the stupid question, with your USB fix, it really put the files in the LDR version or it just changes the file version?
It really puts the actual LDR versions. They are copied from the relevant winsxs folders, which are unaffected by the USB issue. Its only the updating of the USB files (the ones outlines in previous posts) in Windows\system32\drivers and Windows\inf that are affected by the bug. No files are altered by the fix, the fix just merely copies the relevant latest version files to where they're meant to be (overwriting the superseded files the updates are meant to replace but don't). The outcome is a system that is the same as if both updates actually worked like they should.