Windows 7 - USB bus not recognized after restart after USBPcap installation #3
Comments
|
Which version of Windows and USBPcap did you use? |
|
I attempted to install USBpcap 1.0.6 on a 32 bit windows 7 machine. I uninstalled USB Pcap 1.0.2, then ran the 1.0.6 installer which 'failed' during install. After reboot, no USB devices were recognized. Recovered machine with a system restore. |
|
I used USBpcap 1.0.0.6 on Windows 7 Enterprise SP 1, 64 bits |
ghost
assigned
|
To manually recover from this issue it is possible to remove USBPcap from following registry entry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Class{36FC9E60-C465-11CF-8056-444553540000}\UpperFilters The problem happens when USBPcap service cannot start (most likely because USBPcap.sys is not present in System32\drivers directory). Alternative recovery solution would be to copy the USBPcap.sys from USBPcap's installation directory into System32\drivers and reboot. |
|
I've installed v1.10 and after a reboot most of my system usb ports stopped working. I had to pull it out via SCCM from nearly 30 desktops... very disappointing but nice finding, I wrecked two computers until I found this thread! Models are Dell 990, Dell 9010, Dell 9020 G1 and G2 with Intel 6-7-8 USB3 chipsets. |
|
I have just had this issue. I updated Wireshark on a Toshiba laptop and added USBPCap. After the reboot - no USB devices, no mouse, no trackpad. I had no idea what the cause was. I didn't twig on the USBPCap connection - I just assumed the restart had randomly trashed my registry. I eventually got back on air by booting to a command prompt and copying the files at C:\Windows\System32\config\RegBack to C:\Windows\System32\config\ and then restarting normally. The RegBack folder holds a copy of the registry at the last successful boot. I took this approach because the device manager said it couldn't load the drivers because the registry was corrupted, so I reasoned that replacing it with the last known good copy would fix it. In fact I guess it fixed it because the backup of the registry was pre-USBPCap and didn't have any registry stuff for it. The next day I repeated the excercise on my desktop Dell 8700. AArrgghhh! Same outcome, except I also had no keyboard. I could however TeamViewer across to the machine. So, just a heads-up really. The problem is still there, and it must be causing people some considerable grief. |
|
I had usbpcap installed across 100 workstation... grief it caused indeed, On 3 November 2016 at 00:13, RrnR notifications@github.com wrote:
-Éric Sylvain Périard “What you leave behind is not what is engraved in stone monuments, but what "Ce que vous laissez en arrière n'est pas ce qui est gravé dans des |
|
@desowin - Is there any possibility of documenting an installation procedure that isn't going to leave my machine with non-functional USB after the next restart? I'm not keen to try it again ;-). Presumably when installation is completed something still isn't right, but it doesn't become an issue until the next reboot, so would installing it, then making sure there is a copy of USBPCap.sys in C:\Windows\System\Drivers and then restarting be sufficient (I'm not asking for cast-iron guarantees ... - just trying understand why it fails). |
|
I've had the same problem when installing Wireshark but only when updating from an older version of USBPcap. I previously had a working version of Wireshark + USBPcap installed. I installed the latest version of Wireshark and noticed that there was also a newer version of usbpcap available. There is no option in the Wireshark installer to remove the old usbpcap and then install a new version so I had to uninstall USBPcap manually. The process I went through was:
When my PC rebooted, my USB no longer worked so I no longer had a working USB keyboard or mouse. I was eventually able to recover the system from a system restore point. I believe the correct process should be:
It would be good if this could be enforced within the installer as it's awkward to try to recover the machine |
|
IF THE ABOVE SOLUTIONS DIDN'T WORK FOR YOU, TRY THIS No matter what I tried (uninstalling, reinstalling, registry edits, system restore...), nothing worked. Hope this helps someone. |
|
Hello, |
|
I had the same issues with installing WireShark 2.2.4 with the USBPcap driver. Everything was fine until I rebooted my PC - No USB function what-so-ever! |
|
@BDub74: Do you have KB3033929 installed? I will give it another try to write driver installer from scratch instead of relying on the DefaultInstall/DefaultUninstall as the DefaultInstall/DefaultUninstall does not give enough flexibility when it comes to performing sanity checks. Based on all these failure reports I think installer should prevent installation (and note that installation can proceed after reboot) if there is USBPcap in PendingFileRenameOperations (https://technet.microsoft.com/en-us/library/cc960241.aspx). After installing it should check (in that order) USBPcap.sys, Service, UpperFilters entry. |
|
I suffered from this same problem after trying to update Wireshark and install USBPcap from it. I had existing separately-installed versions of Wireshark and USBPcap. My system Restore Points did not work properly. I tried rebooting normally with a mouse with a USB-to-PS2 adapter, but it did not seem to work at first. Then I found the key point: use only the mouse; do not touch the USB keyboard. The mouse will work fine until you press a key on the keyboard, and then the mouse will stop working. I was able to uninstall both Wireshark and USBPcap from Settings with the mouse. Then I had to shutdown and restart twice before USB devices worked again. |
|
I experienced this issue when testing 1.2.0.1 release candidate. The solution that worked was to navigate to C:\Program Files\USBPcap, right click on USBPcap.inf and select Install. Then after a reboot USB devices and USBPcap worked fine. I will check if I can reproduce this. |
|
Unfortunately none of the System Restore points could let me reproduce the problem. I tried uninstalling and installing it a few times but the problem did not reappear. |
|
@desowin -Thanks for continually looking into this issue. I'm willing to try version 1.2.0.1 to see if it fixes my USB problems after reboot. Please let me know when you have something available for me and others to test out? |
|
I think I have found the way to reproduce this issue: However, if step 2 is replaced by uninstall by double clicking on Uninstall.exe, then everything works fine. If you notice the error box and don't want USB to stop working after reboot, simply start Uninstall.exe and remove USBPcap before rebooting. Could you please check if you can reproduce this behaviour on your systems? |
|
@desowin I think what happened is this:
I think that is equivalent to what you reproduced. I'm kind of unwilling to try this again casually because recovery was quite painful. |
Ok... replied to your steps below on my Win7 Pro x64:I think I have found the way to reproduce this issue:
|
|
It still does not work for me.... Installing 1.0.7.0, rebooted, No USB funct.
|
|
@BDub74: The issue you are observing seems to be with your Windows for some reason not accepting the signature for USBPcapDriver. This is suprising as it is signed and timestamped using VeriSign certificate and timestamp server. This is not directly related to the Add/Remove Programs uninstall vs uninstall.exe. Thanks to https://sourceforge.net/projects/regshot/ I managed to identify the difference between the two. It is related to how service is uninstalled:
Hopefully this can be detected in installer and instruct user to reboot before installing. I think I will release 1.2.0.1 later today. It will be signed using new certificate so maybe @BDub74 issue will be resolved as well. |
|
Signed 1.2.0.1 installer can be downloaded from releases page. |
|
@desowin Ok, downloaded and installed. I will reboot shortly to test. |
|
@desowin So no luck for me. :( Not sure what to do at this point other than hitting F8 every time I need to boot up. I installed it, rebooted lost usb funct, powered off, did F8 and selected DDSE and booted fine. |
|
I am having the exact issue described here with My Windows 10 64bit machine: I installed the latest version of Wireshark and USBPcapDriver. Re-booted. Lost keyboard and mouse. Powered down and rebooted. Hit F8. Selected "Disable Driver Signature Enforcement". What is the best solution at this point? Why is this continuing to occur? "desowin commented on May 10 |
|
@ira-hart: Can you try with Secure Boot disabled? |
|
I tried Secure boot disabled. F12, UEFI Boot Mode, SecureBoot=off
It did boot after this. Tried install of USBpcap.inf again. Just got the spinning wheel forever.
Did a hard power cycle. Very slow booting. Machine would originally boot in ~45 sec. Now it's ~4 minutes. Still no internet connection and audio driver is also off.
From: Tomasz Moń <notifications@github.com>
To: desowin/usbpcap <usbpcap@noreply.github.com>
Cc: ira-hart <ira.hart@yahoo.com>; Mention <mention@noreply.github.com>
Sent: Monday, June 12, 2017 10:10 AM
Subject: Re: [desowin/usbpcap] Windows 7 - USB bus not recognized after restart after USBPcap installation (#3)
@ira-hart: Can you try with Secure Boot disabled?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
@desowin I had multiple IT people at my company come look at this. I ended up in a situation with the current state of the machine, where we cant elevate admin rights at all. Since this is true, we cant remove programs now or regedit. Everything is dog slow. We are wiping the machine tomorrow and reinstalling Windows 10 and all my FPGA design software which will take at least a day.. I'm not sure if this is an issue with Secure Boot or with Driver Signature Enforcement. I would suggest that you post a warning on your web page for people installing USBCap on Windows 10 until a good solution is found.. |
|
@desowin Yes, with secure boot disabled, the keyboard and mouse worked. |
|
Windows 10 pc |
|
@JimNickerson Could you please send me the minidump file from C:\Windows\Minidump? Without it I cannot analyze what went wrong. |
|
The dump is attached
"
BugCheck C9, {23e, fffff80364b82dc4, ffffa6044774ea60, 0}
Unable to load image USBPcap.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for USBPcap.sys
*** ERROR: Module load completed but symbols could not be loaded for
USBPcap.sys
Probably caused by : USBPcap.sys ( USBPcap+2dc4 )
"
jim
------ Original Message ------
From: "Tomasz Moń" <notifications@github.com>
To: "desowin/usbpcap" <usbpcap@noreply.github.com>
Cc: "JimNickerson" <Jim.Nickerson@gmail.com>; "Mention"
<mention@noreply.github.com>
Sent: 6/29/2017 10:10:16 PM
Subject: Re: [desowin/usbpcap] Windows 7 - USB bus not recognized after
restart after USBPcap installation (#3)
…
@JimNickerson <https://github.com/jimnickerson> Could you please send
me the minidump file from C:\Windows\Minidump? Without it I cannot
analyze what went wrong.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKtuOU0V6mIKYt-WrbEqM0NQtZzQ88Xfks5sJIM4gaJpZM4BCpXR>.
|
|
jim Unable to load image USBPcap.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for USBPcap.sys |
|
@JimNickerson Does this BSoD happen also when all USB devices are unplugged? Why do you have driver verifier enabled? |
|
The BSoD happens during boot, there is no time to plug/unplug anything. |
|
Atleast on my laptop it works with normal Windows settings. When I enabled driver verifier it did BSoD just like in your case. |
|
Is it possible to detect if verifier is enabled programmatically? |
|
I need to do some more research about the issue before I can fix it. I hope I can get it fixed on some weekend. Hopefully I can reproduce the issue on my laptop (and get it back to working condition rather quickly) so it's not only guessing. I created issue #40 about this particular problem. Please direct all follow-up to that particular BSoD (revealed with Driver Verifier) to that issue. |
|
So, I have experienced the exact same problem. And have spent countless hours trying to fix this issue. But now I've found a fix that works for me. I hope this method helps. ;) Simply, if you have a UEFI bios, turn Windows UEFI (in Boot>Secure Boot) to Other OS. Then it worked! Imwas very surprised when I found out. |
|
I have just reinstalled Windows 10 x64 on my laptop along with Wireshark 2.4.0 containing USBpcap 1.2.0.1 and have encountered the Driver Not Signed issue that breaks all USB connectivity. I tried v1.2.0.2 without success, but the suggestion from @Nathan13888 above to disable Secure Boot cleared the problem. While testing v1.2.0.2, I also encountered the Malicious File warning reported by @JimNickerson on 1-aug-2017 in issue #40, but this was resolved by unblocking the downloaded .EXE binary (right-click Properties - Unblock) I am not up on whether disabling Secure Boot is a good idea so shall live without USBpcap for now, |
|
I'm glad my method worked! OwO |
|
This bug should not be closed. It has cost me several hours troubleshooting this issue on Win10 with USBpcap 1.1.0.0-g794bf26-5. Uninstalling USBpcap itself doesn't fix the issue, as noted above. |
|
The WireShark installer mentions this bug. I'd really like to use this tool, but there's no way I can risk this happening. I hope that someone will look in to this bug at some point because it seems like a real shame to avoid using this tool just because of this issue. |
|
Looking at Downloading Wireshark today and noticed the USBPcap version is now at 1.2.0.3 |
|
@JeighBI FWIW I have used USBPCap recently (within the last six months) and didn't hit this issue. I was using Windows 10 Home throughout. |
|
USBPcapDriver since the 1.2.0.3 release features driver that is Windows 10 Attestation Signed and hence it should work with the Secure Boot enabled. |
|
The most important thing is to always reboot after uninstalling USBPcap. And install new new USBPcap version only after a reboot. The installer is trying to detect a pending reboot after USBPcap removal and let you through without a reboot - but you shouldn't really try to proceed if you know that you didn't reboot after uninstall. |
|
@FlamusFlamus,what method? |
|
There seems to be a problem with Windows To Go. See #61 for the recovery instructions. I'll try to get the Windows To Go and investigate this issue. For the time being, unless you are interested in fixing the problem, I'd advise to not install USBpcap on Windows To Go system. |
|
Hello, is there any status report of the state of this issue in 2020 with USBPcap 1.5.4.x suggested by the Wireshark 3.4.0 installer? I am using Windows 10 Pro (v2004) with Secure Boot disabled and have never had any previous installation of USBPcap nor Wireshark on this device. Thanks in advance. |
|
I remember having this issue many years ago... dk when scroll up to my last comment? But if you're using Windows, your options for connecting remotely might be a bit limited. If you use GNU/Linux like me, then you could probably still SSH into your computer, though you prob won't have this issue in the first place on that. If you do ever get locked out by this then your only hope would probably be to boot into recovery to regain command access over windows to uninstall USBPcap. |
|
how can i download it |
|
Please help resolve this error: Error transferring http://admin@localhost:3080/v2/projects/912af3b5-fd4f-4096-805c-61151d16f91e/links/8ab832b0-d88f-4baa-b59a-9419b3220c37/pcap - server replied: Bad Request (localhost:3080) |
and others
I installed USBPcap on my laptop and it worked fine, without restarting. I managed to create dumps with it.
However, after the restart, my mouse was not working. Looking in devices, windows report a problem on USB host controller. Running troubleshoot of windows try to reinstall driver of the USB HC but fails to do it. After deinstalling USBPcap, the troubleshoot manage to reinstall drivers and everything works (no restart needed).
The USB bus of my laptop is Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller.
The text was updated successfully, but these errors were encountered: