Wireshark-users: [Wireshark-users] Re: The procedure entry point EventSetInformation could not be

From: Guy Harris <gharris@xxxxxxxxx>
Date: Mon, 22 Sep 2025 16:57:23 -0700
On Sep 22, 2025, at 3:41 PM, Michael Webb <m-h-w@xxxxxxxxxxxxxxxx> wrote:

> My OS is Windows 7 home and I get the following message when launching wireshark:

We don't directly call EventSetInformation(); however, we *do* call other Windows event tracing routines that might themselves call EventSetInformation().

The only place I know of where we'd call those routines would be in the "extcap" module that supports capturing events from Windows event tracing, but the error report says that the call is being made by Wireshark.exe, not etwdump.exe, so apparently we're calling it somewhere, or we're calling a routine that calls it somewhere. Does any developer know a reason why anything in the Wireshark program, or libraries it uses, would call EventSetInformation()?

Note that the last version of Wireshark that officially supports Windows 7 is Wireshark 3.2:

	https://wiki.wireshark.org/Development/LifeCycle

What version of Wireshark is this?

> Please advise.

If you're running a version of Wireshark newer than 3.2, my advice would be to use Wireshark 3.2 instead, given that you're running Windows 7.