You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: