High CPU Usage by WMI When Running Multiple Standard Sandboxes

zipi

New member
Hello everyone,

I am experiencing an issue where the WMI (Windows Management Instrumentation) process consumes a significant amount of CPU when I open several Standard Sandboxes using Sandboxie. When I increase the number of sandboxes, the WMI process seems to struggle, causing my CPU to become overloaded and, at times, to collapse entirely.

I am currently using the free version of Sandboxie and am not a sponsor at this moment. However, I am curious to know if this issue might be resolved in the paid versions or if there are any recommended configurations to help mitigate the high CPU usage related to WMI.

Thank you for your assistance!
 
Hello,

There is no difference in terms of correctness of behavior, between being a supporter or not, only in features that are available and possibly in terms of compatibility, considering the compartment type boxes.

The behavior you are describing does not sound normal.

What version of Windows are you using and which version of Sandboxie do you use?
 
You can try to use the template "BlockAccessWMI" via Sandbox Options > Advanced Options > [Privacy] "Prevent sandboxed processes from accessing system details through WMI"

(or Sandbox Options > App Templates > [Templates] Category: Miscellaneous Name: Block Accessing WMI)

Both add the following to the Sandboxie.ini for the sandbox(es) you enable it for.
Code:
Template=BlockAccessWMI

This was added to prevent sandboxed apps to use WMI to learn something about the system, maybe it is also useful to stop your problem.
 
You can try to use the template "BlockAccessWMI" via Sandbox Options > Advanced Options > [Privacy] "Prevent sandboxed processes from accessing system details through WMI"

(or Sandbox Options > App Templates > [Templates] Category: Miscellaneous Name: Block Accessing WMI)

Both add the following to the Sandboxie.ini for the sandbox(es) you enable it for.
Code:
Template=BlockAccessWMI

This was added to prevent sandboxed apps to use WMI to learn something about the system, maybe it is also useful to stop your problem.
That was the perfect solution, thank you very much for the help.
 
You are welcome. I am glad that this is working for you.

If that turns out to be an issue that effects more users, there might be a root-cause that needs to be fixed.
 
Back
Top