But, the new issue happens even without installing the Legacy loopback adapter. The workaround for Issue 1173 was to not install the loopback adapter. This issue is present with WinPcap API-compatible mode enabled OR disabled.This is not reproducible on all PCs, just certain users."net stop npcap" - This allows web browsing to work again.Confirmed via Device Manager that no previous Loopback adapters were installed.Default options to use Npcap were used (all boxes, including Legacy loopback adapter were NOT checked) Install Wireshark-win64-3.2.1.exe (This includes Npcap 0.9986).Clean system: Uninstall previous Wireshark + Npcap.Web browsing stops working after starting Wireshark/Npcap 0.9986 I believe that I'm having the same issue with users here as well. This might not be the case, might be due to having started a loopback capture first then switching adapters. Note that Wireshark requires Npcap to be running to even start a capture on any interface. The issue happens even when capturing on a non-loopback interface.Stopping Npcap after the interfaces load and then attempting to start a capture on one results an error message: The capture session could not be initiated on interface '\Device\NPF_' (Error opening adapter: The system cannot find the device specified.When Npcap is installed, Wireshark will not properly load all of the capture interfaces unless Npcap is running.Tried Wireshark capture on "Adapter for loopback traffic capture".Reinstalled Npcap 0.9983 (left all 4 installation option boxes unchecked, including the legacy loopback support box).
Confirmed that Wireshark captures on other interfaces did not show the reported weird behavior.Thanks for the response! I tried the following but am still seeing the issue:
0 kommentar(er)
