Wireshark launches, but where the capture interfaces should be there is nothing — No interfaces found, or No interfaces can be displayed. Wireshark itself is fine; it cannot see the machine's network interfaces. The cause is almost always a capture driver or a permission, and it differs by platform.
Fixes for Windows 11/10/7, Linux and macOS, in the order that resolves reports fastest.
Triage: what does the empty list look like?
| Symptom | Platform | Go to |
|---|---|---|
| Empty list right after a fresh install or an upgrade | Windows | Causes 1, 6 |
| Worked before Windows update / reboot, gone after | Windows 11 | Causes 1, 3 |
| Works with sudo, empty as normal user | Linux | Cause 2 |
| Empty after macOS update or on a new Mac | macOS | Cause 4 |
| Empty inside RDP, VM, or WSL | any | Cause 5 |
| Interfaces exist in the OS, not in Wireshark | any | Causes 3, 6 |
1. Windows: Npcap is missing, broken, or stopped
Wireshark on Windows captures through Npcap (the modern driver; the old WinPcap is deprecated and not installed by current Wireshark versions). If Npcap did not install, was removed, or its service is not running, Wireshark has nothing to capture through — the interface list is empty.
- Re-run the Wireshark installer and make sure Install Npcap is checked — or install Npcap separately from its official site.
- Check the service: services.msc → Npcap (or "Npcap Packet Driver") → status Running, startup Automatic. Start it and reopen Wireshark.
- After any Npcap install or repair: reboot. Half the "it still doesn't work" reports end here.
2. Linux: capture permissions
On Linux the empty list is almost always permissions — dumpcap (Wireshark's capture helper) may not be allowed to read interfaces:
- Quick test: sudo wireshark. If interfaces appear, it is a permission problem, not a driver problem.
- The proper fix: add your user to the capture group (the installer asks: "Allow non-superusers to capture packets" — answer yes, then log out and back in): sudo usermod -aG wireshark $USER, and confirm dumpcap keeps its capabilities: getcap /usr/bin/dumpcap should print cap_net_admin,cap_net_raw.
- Minimal/WSL/container images may not carry the group or capabilities at all — install wireshark from the distribution's package so the helper is set up properly.
3. The interface is disabled — or the driver binding is stale
The OS has interfaces; Wireshark's list is empty or missing the one you need:
- Confirm the OS sees them: ip link (Linux), ipconfig /all (Windows), ifconfig (macOS). If they are missing there too, this is an OS/driver problem, not Wireshark.
- Windows: Device Manager → network adapters → the adapter is Enabled. Disable/enable it once; a stuck binding clears.
- Windows: Npcap binds per adapter type — a VPN or virtual adapter installed its own driver stack and displaced the capture binding. Repair Npcap after installing VPN software, in that order.
4. macOS: privacy permission for the capture helper
Recent macOS versions gate packet capture behind privacy approval (System Settings → Privacy & Security):
- Look for Wireshark (or its BPF/capture helper) under the privacy entries and approve it; macOS prompts on first capture — the prompt is easy to miss and hard to find again.
- After a macOS update the grant can reset. Re-approve, then reopen Wireshark.
- On a brand-new Mac, launching Wireshark once before capturing is enough to trigger the prompt.
5. You are capturing in the wrong place
- Remote Desktop: Wireshark lists the interfaces of the machine it runs on — the remote one, over the RDP session, not your laptop.
- Virtual machines: the guest lists the guest's virtual NICs. Host traffic needs the host's Wireshark (or the hypervisor's capture on the virtual switch).
- WSL: WSL is a separate system — install Wireshark on Windows for Windows interfaces, or inside WSL for the WSL ones.
6. Upgrade leftovers
Wireshark upgraded across a major version (or over an old WinPcap install) with the driver left behind from the previous stack. Clean reinstall: uninstall Wireshark and Npcap/WinPcap, reboot, install current Wireshark fresh with Npcap. Settings survive; the driver stack gets rebuilt — which is the point.
Confirm the fix
| Check | Expected result |
|---|---|
| Open Wireshark → welcome screen | Interfaces listed with live sparklines of traffic |
| Capture → start on the active interface | Packets flow; no permission dialog blocks it |
| Linux only: repeat as non-root | Still lists interfaces — group/capabilities persisted |
Interfaces listed but nothing captures? That is a different failure — the capture starts and shows zero packets: Wireshark Not Capturing Packets. For the tool itself: the Wireshark guide.
Frequently asked questions
Why does Wireshark say "no interfaces found"?
Wireshark cannot reach the system's capture layer — on Windows that means Npcap is missing or stopped, on Linux the user lacks capture permissions, on macOS the privacy grant is missing. The interface list is a symptom; the driver or permission is the cause.
How do I fix Wireshark on Windows 11?
Repair or reinstall Npcap (Wireshark installer option), confirm the Npcap service is running and automatic, and reboot. If it broke right after a Windows update or a VPN install, the driver binding was displaced — reinstall Npcap after the VPN software.
Why is Wireshark not showing interfaces on Linux?
Capture permission. Running with sudo proves the diagnosis; the proper fix is the wireshark group plus dumpcap capabilities so you never capture as root.
What is Npcap?
The packet-capture driver Wireshark uses on Windows (the maintained successor to WinPcap). Wireshark's UI is only half the installation — without Npcap running, there is nothing to capture through.
Do I need to be root/administrator to see interfaces?
To see the list, no. To capture, the OS must allow it — Windows via Npcap's install-time grant, Linux via group/capabilities, macOS via privacy approval. None of them require running Wireshark itself as root once configured.