EvtOpenLog API getting stuck on internal lock

Question

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

https://learn.microsoft.com/en-us/answers/questions/98127/using-evtquery-in-parallel-is-block-each-other.html

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?