This is our old Q&A Site. Please post any new questions and answers at

I just downloaded the source zip of Wireshark 1.4.6, built it on Windows XP SP3, and tried starting it from the Visual Studio 2008 debugger. When Wireshark starts, I get this error message box:

Child dumpcap process died: Exception 0xc0000135

This message box also appears when I try to open the "Capture Options" or "Interface List" dialog. From "Capture Options", the interface list only shows one entry: \Device\NPF_{D0C748F9-7B75-453D-A585-0813AE3B8A13}

This problem does not occur if I start the executable itself (not via the VS debugger). It seems like some VS setting is not correct.

How can I resolve this problem? Thanks.

P.S. I see that there have been similar problems without a [known] solution:


asked 27 Apr '11, 15:03

bstn's gravatar image

accept rate: 14%

edited 27 Apr '11, 17:50

Bill%20Meier's gravatar image

Bill Meier ♦♦

Found the problem: Exception 0xc0000135 is the Windows error code for "DLL not found".

Solution: Edit project properties to add a reference path to the project's output directory (where the necessary DLLs are found)...

From Visual Studio 2008:

  1. Open menu Project > Properties
  2. Expand tree node Common Properties > Framework and References
  3. From Additional reference search paths, click the Add Path... button
  4. Browse to project's output directory (e.g., c:\sandbox\wireshark-1.4.6\wireshark-gtk2)
  5. Click OK
permanent link

answered 27 Apr '11, 15:59

bstn's gravatar image

accept rate: 14%


An alternative:

To create the project/Solution. in VS, do File ! Open ! Project/Solution of the executable in the wireshark-gtk2 directory (rather than using the executable in the top-level directory).

That is:

....\wireshark-gtk2\wireshark.exe (or tshark.exe or ...)

if this is done, then there will be no need to set additional search paths.

(27 Apr '11, 17:35) Bill Meier ♦♦

Ah, very cool. I had created a Project From Existing Source (before I had the binary) and used VS instead of the command line to build the binary. My method is somewhat painful because VS runs make before every debugging session. Doing it your way is much faster: exclusively use the command line to build and VS to debug. It would be great if someone updated the Developer's Guide to indicate these simple steps (there's currently a TODO comment for Debug Environment Setup).

(28 Apr '11, 09:14) bstn
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 27 Apr '11, 15:03

question was seen: 3,591 times

last updated: 28 Apr '11, 09:14

p​o​w​e​r​e​d by O​S​Q​A