After upgrading wireshark 2.0.5 to the newest 2.2.0 Wireshark is stuck at the splash screen with 99% and the message "Initializing tab listeners". I'm running windows 10 and WinPCAP 4.1.3 Anyone seen this before? Regards Jeppe asked 08 Sep '16, 07:38 Pixelweb edited 12 Sep '16, 23:50 sindy showing 5 of 11 show 6 more comments |
One Answer:
The issue affects only users who have installed USBPcap (or, possibly, also those who run their own extcap applications) and who have a lot of USB and/or bluetooth devices connected. The behaviour is explained in detail in Bug 12845. If you are affected, you are welcome to help resolve the bug by following the instructions given in the comments to the Question and contribute the information directly to the bugzilla or as another Comment here. answered 12 Sep '16, 23:58 sindy |
Downgraded back to 2.0.5 and Wireshark is running again.
Do you have any custom plugin installed? If yes, does Wireshark start properly if you remove it?
As I crashed into the same issue, I've given it some time and I've filed Bug 12845. The good news is that it seems that only the first start after reboot is affected, and that if you don't need live capturing from USB, removing
USBPcapCMD.exe
from theextcap
directory probably hides the issue completely.I am having the same issue and a uninstall and re-install did not fix the issue. I updated from 2.05 64-bit.
Sindy, THANKS for the suggestion to remove the USBCAPCMD.EXE file from the extcap directory. I had to reboot the computer to remove the file and I can now launch Wireshark and Wireshark Legacy 64-bit without it hanging.
I currently do not do much capturing from USB and will wait for the next release for a possible long term fix.
@Pixelweb, @PLCMAN58, could you please help localize the issue?
Open the plain command shell (not Powershell!), go to the directory where USBPcap is installed (if default installation paths are used, it is
C:\Program Files\USBPcap
), and issue the following commands:USBPcapCMD --extcap-interfaces
This should list something similar to the following:
interface {value=\\.\USBPcap1}{display=USBPcap1} interface {value=\\.\USBPcap2}{display=USBPcap2}
Then, for each
\\.\USBPcapX
you get as avalue
on your system, issue a commandc:\Program Files\USBPcap>USBPcapCMD.exe --extcap-config --extcap-interface \\.\USBPcapX
(replacing the last X with 1 .. whatever the number of root hubs in your system), and paste the complete output of all of them to a Comment here?An example output for
c:\Program Files\USBPcap>USBPcapCMD.exe --extcap-config --extcap-interface \\.\USBPcap3
on my system is:
arg {number=0}{call=--snaplen}{display=Snapshot length}{tooltip=Snapshot length}{type=integer}{range=0,65535}{default=65535} arg {number=1}{call=--bufferlen}{display=Capture buffer length}{tooltip=USBPcap kernel-mode capture buffer length in bytes}{type=integer}{range=0,134217728}{default=1048576} arg {number=2}{call=--capture-from-all-devices}{display=Capture from all devices connected}{tooltip=Capture from all devices connected despite other options}{type=boolflag}{default=true} arg {number=3}{call=--capture-from-new-devices}{display=Capture from newly connected devices}{tooltip=Automatically start capture on all newly connected devices}{type=boolflag}{default=true} arg {number=99}{call=--devices}{display=Attached USB Devices}{tooltip=Select individual devices to capture from}{type=multicheck} value {arg=99}{value=1}{display=[1] Obecn├Ż rozbo─Źova─Ź USB}{enabled=true}
Yours may be much longer at least for one of the
\\.\USBPcapX
.@Pixelweb, you don't need to reinstall back to 2.2.0 if you haven't yet, the result of the USBPcap which came along the 2.0.5 will provide the necessary information as well.
@sindy I get the error no matter if USBPcap is installed or not. Currnetly my C:\ProgramFiles\USBPcap-directory is present but completely empty Regards Jeppe
@Pixelweb, please check the contents of your
C:\Program Files\Wireshark\extcap
directory. If there is something, let me know what it is, rename the wholeextcap
directory to something likeextcap_x
and create an emptyextcap
one next to it, and then try running Wireshark 2.2.0 again. I'm afraid the uninstall doesn't always tidy up completely. Hiding the originalextcap
directory from Wireshark by renaming it should eliminate any hangovers.@sindy, c:\program files\wireshark\extcab contains one file: USBPcapCMD.exe I have renamed extcap dir to extcap_x and created a new dir called extcab which is empty.
I uninstalled wireshark 2.0.5 and installen version 2.2.0 - without installing the USBPcap driver. During the installation I was asked if I wanted to uninstall 2.0.5 first which I accepted.
When the 2.2.0 install was complete the extcap_x dir was still present but the empty extcab dir was gone.
Now version 2.2.0 opens up fine both the new GUI and the Legacy version.
Thanks for your help :-) Best regards Jeppe
@Pixelweb, I'm glad it has helped you, but now please help the development team by following the steps I've given above, using the
USBPcapCMD.exe
located in your extcap_x directory :-)@sindy, Sorry :-) Here it comes:
Regards Jeppe