Did you attempt to write a test for this and it didn't work because of previous CoInitialize? Looks good otherwise.

I expected the existing tests to be able to detect/catch/reproduce the issue.

In my case, the issue occurred only on Windows Server 2012 R2, and not on Windows Server 2019 or 2022 for example.

The last entry in the log was written by LOG(L"Checking whether WMI query '" << query << L"' returns any results");.

The application crashed with exception code C0000005, a memory error indicating an access violation.

I'm guessing that it was the release of CComPtr<IWbemClassObject> pclsObj which would have been called after CoUninitialize that caused the error.

Maybe running the tests on Windows Server 2012 R2 would reproduce the issue, but I never tried.