search

emoacht / Monitorian

A Windows desktop tool to adjust the brightness of multiple monitors with ease
https://www.microsoft.com/store/apps/9nw33j738bl0
MIT License
3.3k stars 154 forks source link

When WMI is disabled, app crashes #610

Closed dzid26 closed 1 month ago

dzid26 commented 1 month ago
image

exception.log Based on log message, I guess I disabled some service? But it doesn't say which one.

emoacht commented 1 month ago

Thank you for reporting. This error (0x80070422) seems to be raised when WMI service cannot be started.

Two questiions:

  1. Have you disabled WMI service?
  2. Your PC is laptop?
dzid26 commented 1 month ago

Yes, I had the WMI disabled because it keeps using between 0-5% cpu which adds to overall constant CPU usage and laptop heating.

After enabling WMI and restarting Windows, Monitorian started to work again.

emoacht commented 1 month ago

WMI is almost essential to control an internal monitor because such functinality is only provided by WMI. Technically it is possible to avoid calling WMI if this app only handles external monitors. But there would be no substantial reason for adding such mode.

dzid26 commented 1 month ago

That explains why I was getting only external monitor control in Twinkle app! Hah.

Maybe it would be wise to try/catch missing WMI and indeed just control external monitors in that case.

I hate WMI cpu usage with HP laptop with HP drivers. I don't like Intel 11th gen and Windows either. (It burns my skin.)

Anyway, thanks, for the interesting input.

emoacht commented 1 month ago

Killing exceptions caused by absence of WMI silently is easy. But WMI is a part of API of Windows and commonly used. An app does not inform users of APIs that it uses. Disabling WMI may or may not lead an unexpected behavior of apps and you may or may not notice it. I guess it usally would not cause serious issue but no one knows.