Network interfaces do not come up during reboot after installing Wireshark on Windows Server 2012 R2
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 592
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I have VMs in Azure running windows server 2012 R2 and having 2 network interfaces, I tried to install wireshark:
- I have installed latest Wireshark (3.4.5 64-bit) on the VM
- Rebooted the VM
- After reboot VM became unreachable
- logging in to the VM via serial console shows ipconfig /all has only one loopback interface
- uninstalled wireshark and npcap from commandline and rebooted the VM, network interfaces came up.
This is an older problem happened on older versions also. Last good known wireshark version is 2.6.4.
Do you have any idea what is blocking network interfaces? What logs/configs should I check?
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
No source files, tests, or entry points are named. Start by reproducing the Wireshark 3.4.5 and Npcap installation on a Windows Server 2012 R2 VM with two network interfaces, then collect the requested logs and configuration before and after reboot. Done means identifying what prevents the interfaces from loading and documenting a verified fix or a precise regression cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100