Npcap driver service fails to start with System error 2: The system cannot find the file specified
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 592
- PR merge metrics
- No merged PRs in 30d
Description
I am running the latest version of Wireshark under Windows 10 64bit Home Edition
I am getting an Error whenever running the Capture Interface:
Adapter for Loopback Traffic Capture.
Error = The capture session could not be initiated on interface '\Device\NPF_Loopback' (Error opening adapter: A device which does not exist was specified. (433)).
I uninstalled NPCAP, Wireshark and re-installed them with the latest versions.
- npcap version 0.9987
- USBPCAP 1.5.3
- Wireshark version Wireshark-win64-3.2.2
However, I am still getting the same above error.
Under Windows PowerShell, prompt I typed: Get-Service npcap.
Status Name DisplayName
Stopped npcap Npcap Packet Driver (NPCAP)
I also ran the following steps:
Step 1: Run the command prompt as administrator (right click -> run as administrator)
Step 2: type the following in the cmd: net start npcap
Error = System error 2 has occurred. The system cannot find the file specified.
What ncap file extension is it looking for and which directory should it be located?
I also attached a copy of the ncap diagnostic report:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached DiagReport-20200304-144430.txt and the reported Get-Service npcap and net start npcap results. Determine why the Npcap driver service cannot find its required file and confirm that the service starts and loopback capture works afterward.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100