After installing Wireshark, in the “Capture “-> “Options” does not have a single capture interface.
Question why
Win10 compatibility issues caused. is required to uninstall Winpcap and reinstall Win10pcap
The solution
(a) to download and install win10Pcap, download links: http://www.win10pcap.org/download/
note: prior to install Wireshark off, otherwise an error during the installation.
n>
Read More:
- (transfer) using Wireshark package capture software to prompt the NPF driver isn’t running solution
- After upgrading windows 11, Wireshark can’t get list of interfaces: packetgetadapternames reports an error
- The local network card cannot be obtained by opening Wireshark
- Using Fiddler to capture mobile app
- Wireshark filtering HTTP packets
- Installation user interface mode not supported solution
- Centos-7 set boot to enter the text interface (not enter the graphical interface)
- Sina world of Warcraft 3.1.3 compressed package cannot be executed. Solution: failed to open archive interface.MPQ
- To solve the problem of C # calling excel interface error, prompt: the COM object of Microsoft. Office. Interop. Excel. Applicationclass is forcibly converted to the interface type “Microsoft. Offi”
- Centos7 installation interface without interface
- Failed to capture snapshot of output files for task ‘ :packagePreDebug’ property ”outputDirectory’
- CodeBlocks environment error the compiler could not find a solution to the problem
- Solution for flash back of vs2015 running interface
- Python error: importerror: DLL load failed: unable to find the specified module solution
- Error: solution to the problem of cannot find module ‘webpack / bin / config yargs’
- Free dynamic screen capture drawing tool under MAC: KAP
- JS exception capture: the usage and example analysis of onerror() in window
- Solution to electron error “cannot find module app”
- Solution to the problem that OpenGL can’t find glew32.dll in vs2019
- Rselenium packet capture chain home network (Part 2: data storage and fault tolerance management)