Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rigor mortis? Or are we past that? #20

Open
g40 opened this issue Mar 20, 2024 · 0 comments
Open

Rigor mortis? Or are we past that? #20

g40 opened this issue Mar 20, 2024 · 0 comments

Comments

@g40
Copy link

g40 commented Mar 20, 2024

A fantastically useful tool for WMI work. Highly recommended though read on.

I'm building from source using VS2022. Everything works as expected until (I think) cache expiries apply and connections are dropped.

For example, the image below shows live connections to various instances of MSFT_Disk. With a cache timeout default of 60minutes the explorer will stop enumerating and displaying running instances if left for a long time (i.e. overnight). A restart of the explorer does not seem to help. It is almost as if the cache is persisted somewhere.

I've solved this by bypassing the cache, setting the timeout to 0. There is, of course, a cost, it can take quite some time for WMI to respond.

Does anyone have any insights?

And is anyone else actively working on the codebase?

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant