The Windows 7 SP1 USB Driver Bug (what it is and how to fix it)

Discussion in 'Windows 7' started by Enigma256, Feb 6, 2011.

  1. DAz999

    DAz999 MDL Member

    May 19, 2007
    132
    40
    10
    burfadel

    I have just tried your fix on Windows Starter x86, I applied the patches as you stated rebooted each time, but when I ran your script, it ended with no update carried out, the script did not complete and just closed cmd as soon as I pressed a key to execute? I also tried to run from the command prompt and the error was"x86 Unexpected Error" It worked fine on Windows 7 x64, so it seems x86 script may still have a problem.
     
  2. burfadel

    burfadel MDL EXE>MSP/CAB

    Aug 19, 2009
    2,627
    3,855
    90
    hmmmm, thats interesting! I don't use x86 so I am unable to test that myself.

    The first thing to point out is the archive must be extracted, it should not be run from within the .7z archive. This is true for any programme, although if its a single file installer it may be ok to.

    If you have run it after exracting it, can you do the following on your x86 system:
    - Navigate to C:\Windows\winsxs
    - In the search box at the top right hand corner of explorer, type in *usbport.inf*
    (note you have to put the wildcare '*' at the beginning and end!
    - Wait for the seach to complete, and once it has if the folders aren't at the top of the list click on the 'name' column so they do. You should be in 'list' view for this. Most things are missed by people having the view in 'tiles' or 'small icons' mode
    - there should be a few folders, look at the ones specifically with the string '6.1.7601.21692' and '6.1.7601.21700' in the filename. If you do not have these folders, those updates didn't actually install properly!
    - click on the filename as if you were to rename it, and copy the folder name and paste it in to here for both of those folders.
    - repeat the process, but this time search for *usb.inf* and only select the '6.1.7601.21692' string, and copy the whole name into the post.
    - in total, you should have copied three strings

    This is just to check whether the string data I wrote is correct. If it is, then I will try and find out why it isn't working. It would be helpful if anyone else on x86 could tell me whether it is working for them or not, as its hard to find the issue when I don't have x86 to test on specifically.

    If the folder info is correct and others are also having the issue, I'll try reordering the code again (there is a few ways the code can be done) and see if that helps. But in that instance also, I can only test the x64 portion. Regardless of this, the only real difference is the pendmove being used and the folder referencing... for both x86 and x64 the same lines of code is used for the fix part of the script.
     
  3. DAz999

    DAz999 MDL Member

    May 19, 2007
    132
    40
    10
    #123 DAz999, May 13, 2011
    Last edited by a moderator: Apr 20, 2017
    Hi as requested, here is the information[, also I have listed the files in the folders for you.

    usbport.inf

    Code:
    x86_usbport.inf_31bf3856ad364e35_6.1.7601.21692_none_bffae6357b300705

    usbd.sys
    usbehci.sys
    usbhub.sys
    usbohci.sys
    usbport.inf
    usbport.sys
    usbuhci.sys


    Code:
    x86_usbport.inf_31bf3856ad364e35_6.1.7601.21700_none_c05a36d37ae8d605
    usbd.sys
    usbehci.sys
    usbhub.sys
    usbohci.sys
    usbport.inf
    usbport.sys
    usbuhci.sys


    usb.inf

    Code:
    x86_usb.inf_31bf3856ad364e35_6.1.7601.21692_none_cd30edb88614b91e
    usb.inf
    usbccgp.sys
    usbhub.sys
     
  4. DAz999

    DAz999 MDL Member

    May 19, 2007
    132
    40
    10
  5. Motley

    Motley MDL Novice

    May 12, 2011
    5
    0
    0
    Thank You!
     
  6. burfadel

    burfadel MDL EXE>MSP/CAB

    Aug 19, 2009
    2,627
    3,855
    90
    If it passed the test, not sure what else could be wrong! The script uses the same locations as the test script, and the actual code is the same for the x86 and x64 functional part of the script (referencing x86 instead of AMD64).

    Has anyone else with x86 encountered the same issue?
     
  7. malvo26

    malvo26 MDL Novice

    Jun 11, 2008
    24
    6
    0
    I ran into the same problem as DAz999 on an X86 laptop. Passes all test with the test script but with the fix script it states that the hot-fixes appear not to be installed although they are.
     
  8. burfadel

    burfadel MDL EXE>MSP/CAB

    Aug 19, 2009
    2,627
    3,855
    90
    The only way I can see it not working for x86 and x64 is if you don't have SP1 installed. I'll add a check for that, although it shouldn't really be needed!...
     
  9. zlaga

    zlaga MDL Novice

    Apr 14, 2011
    17
    1
    0
    Can you explain, please? Which files don't get updated?
     
  10. zlaga

    zlaga MDL Novice

    Apr 14, 2011
    17
    1
    0
    burfadel - The cases your tool is trying to correct is desired and intentional behavior. The versioning I'm seeing in the other thread that you're correcting is by design.

    For example:


    Yes, this is normal. Everything here is correct.


    Please PM me.
     
  11. burfadel

    burfadel MDL EXE>MSP/CAB

    Aug 19, 2009
    2,627
    3,855
    90
    The file versions of usbuhci.sys and usbd.sys are definitely incorrect, KB2529073 should have updated all those files to 6.1.7601.17591 if no other related hotfix installed or 6.1.7601.21692 if there were. If you installed KB2538984 usbehci.sys, usbhub.sys, and usbport.sys should be 6.1.7601.21700 and the remainder 6.1.7601.21692.
     
  12. burfadel

    burfadel MDL EXE>MSP/CAB

    Aug 19, 2009
    2,627
    3,855
    90
  13. DAz999

    DAz999 MDL Member

    May 19, 2007
    132
    40
    10