EvtOpenLog API getting stuck on internal lock

DN 1 Reputation point

We have the exact same problem that was seen and described here:


We are seeing this on Windows 10 October 2018 Update (version 1809).

The answer was very unsatisfactory - naturally a container needs to protect itself with a lock, but it is very poor code that locks a container and THEN makes network requests to get whatever will be put into the container. Locks shouldn't be held while network requests are made.

This seems like a bug in the Windows Event functions (at least EvtOpenLog from what we see here).

Are there any fixes? Work-arounds? Any way to probe and determine a call will lock before making it?

Windows API - Win32
Windows API - Win32
A core set of Windows application programming interfaces (APIs) for desktop and server applications. Previously known as Win32 API.
2,412 questions
{count} votes