I've added a new advanced config option
Disks_MaxDegreeOfParallelism that controls how many threads the Scanner uses to query WMI for disk / controller information at startup. We use 10 threads by default to speed up the initial disk enumeration. This has never been a problem, so I don't think that this is a "bug" and I'm not changing our default behavior.
However, that's the only thing that I can think of that would affect WMI in this "freezing" case.
To conclude this:
The line of code where it's locking up is not buggy, so there is nothing to fix on our end. WMI is simply freezing upon receiving our query. I'm sure that it would freeze the same way if any other application issued the same query (perhaps other queries are affected as well).
- WMI needs to be functional and not freeze when we issue that query.
Since this is not dependent on any of our code, I don't see what we can do on our end to resolve this freeze. We can only offer suggestions on how to repair that OS's WMI functionality.