I have Wireshark 2.0.1 on Windows 7 64-bit on a Dell Latitude E5550. If I use the menu system to do Open, Save As... and several other operations in the File menu Wireshark quietly exits. I think the problem I have relates to Qt. I recreated the problem and used procmon to trace Wireshark exiting. I noticed Wireshark fiddling about with some Dell Backup stuff! It turns out that the Dell Backup program uses Qt5, but a different revision to Wireshark. I’m getting some sort of weird interaction between Wireshark and Dell Backup program, I think relating to two revisions of a DLL called Qt5Core.dll. It gets in a right old state; at one point Wireshark is executing code inside a Dell Backup Restore DLL! Thinking about it now I guess the Dell code might be a minifilter, although it looks as though the main thread stack has been corrupted. I know – you want to know what the fix is, don’t you? So do I? I'll do some more work on this later, but I thought I'd check if this is a known problem and if there is already a fix. asked 16 Feb '16, 02:08 PaulOfford |
One Answer:
See bug 12036. answered 16 Feb '16, 03:05 grahamb ♦ |
Great catch Graham. Cheers.