Graham Bloice
changed
bug 9609
| What |
Removed |
Added |
| Status |
IN_PROGRESS
|
RESOLVED
|
| Resolution |
---
|
NOTOURBUG
|
Comment # 14
on bug 9609
from Graham Bloice
Thanks for the dump, but sendspace is a horrific place to visit.
Anyway, the call stack:
sysfer.dll!00000000663e9b27() Unknown
KERNELBASE.dll!CreateFileInternal () Unknown
KERNELBASE.dll!CreateFileW () Unknown
KERNELBASE.dll!CreateFileA () Unknown
Packet.dll!0000000000f54a6d() Unknown
Packet.dll!0000000000f526d6() Unknown
Packet.dll!0000000000f52ee5() Unknown
Packet.dll!0000000000f53bcc() Unknown
Packet.dll!0000000000f55baa() Unknown
wpcap.dll!0000000180002227() Unknown
dumpcap.exe!pcap_findalldevs(pcap_if * * a, char * b) Line 449 C
which shows that dumpcap is calling into WinPCap (wpcap.dll and Packet.dll)
which is then calling into the kernel trying to open a file (CreateFilexxx),
but is blocked in sysfer.dll.
Googling around this seems to be part of Symantec Endpoint protection. I found
this link
(http://www.symantec.com/connect/articles/crreating-application-control-exclusions-symantec-endpoint-protection-121)
with some workarounds, but basically it's now up to you to resolve this with
Symantec, either by removing their software, or taking the case up with their
support.
I'm going to mark this entry as RESOLVED NOTOURBUG, but if you do pursue it
with Symantec please post back here on how you got on.
You are receiving this mail because:
- You are watching all bug changes.