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

wmiobject access via "root/OpenHardwareMonitor" does not work in Windows 10 #864

Closed
crysman opened this Issue Oct 6, 2016 · 8 comments

Comments

Projects
None yet
6 participants
@crysman
Copy link

crysman commented Oct 6, 2016

We've upgraded one machine to W10pro. Since then my powershell scripts stopped working. Theproblem is that calling

get-wmiobject -namespace "root/OpenHardwareMonitor" -Class Sensor

does not produce any output. The same script on Win server 2012R2 works just fine.

However, calling

get-wmiobject -namespace "root/OpenHardwareMonitor" -List

works.

What might be the problem? Any ideas? Thank you.

@akej74

This comment has been minimized.

Copy link

akej74 commented Oct 10, 2016

Probably unrelated, but I'm running the following in Python successfully on Win 10:

hwmon = wmi.WMI(namespace="root\OpenHardwareMonitor")
sensors = hwmon.Sensor(["Name", "Parent", "Value", "Identifier"], SensorType="Temperature")

@allstone

This comment has been minimized.

Copy link

allstone commented Nov 23, 2016

Yup, WMI does not work on my home PC too. Running latest cumulative updates winver 1607 build 14393. I checked and OpenHardwareMonitor does not write any sensor data under "root/OpenHardwareMonitor" at all, it is empty. Should OpenHardwareMonitor ask and receive some elevated privileges now? Btw, everything works on windows connected under the domain and privileges managed externally.

@crysman

This comment has been minimized.

Copy link

crysman commented Jan 2, 2017

Please, could anyone dive-in into this?
It is not working under administrator account either.
-class Hardware neither works.

@zXLestath587Xz

This comment has been minimized.

Copy link

zXLestath587Xz commented Jan 4, 2017

I have the same problem after update my Windows 10 x64 Build 10240 to the last Build 14393.576
(https://support.microsoft.com/en-us/help/4004227/windows-10-update-kb3206632)

Everything was working fine before update.

@crysman

This comment has been minimized.

Copy link

crysman commented Feb 6, 2017

Any chance of fixing this OpenHardwareMonitor WMI API bug? :/

Still not working in latest 0.8.0 beta

@dwilhelm

This comment has been minimized.

Copy link

dwilhelm commented Feb 6, 2017

I've never looked at the OpenHardwareMonitor WMI info before, so maybe I'm doing something differently, but I don't have any problem getting output on Windows 10 Pro, either with PowerShell or Python.

There's no output when OHM is not running, but that's the same as on Windows 7 for me (again with both PowerShell and Python).

In case it matters, I'm an admin on all test machines.

@DarthDestroyer

This comment has been minimized.

Copy link
Contributor

DarthDestroyer commented Feb 6, 2017

like @dwilhelm said:

  1. OHM must run in the background!
  2. OHM must be started as admin (but that is already necessary to receive all sensor data)

btw: the latest version is => http://openhardwaremonitor.org/files/openhardwaremonitor-v0.8.0.3-alpha.zip

for further debug, i would love to see a report uploaded!

@crysman

This comment has been minimized.

Copy link

crysman commented Feb 7, 2017

OK, I've made further research and tests.
Conclusion: 0.8.0 works, 0.7.1 doesn't

I've found that we had been using an older version of OHWM (0.7.1) on one particular W10 machine, which, indeed, is not working properly. 0.7.1 does work, though, without any trouble on Windows Server 2012R2 machines.

On the other hand, the last try witch freshly downloaded 0.8.0 (yes, it is the latest stable now according to the official download page - http://openhardwaremonitor.org/downloads/) has worked now!

Thanks for your time and sorry for misleading info.

@crysman crysman closed this Feb 7, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment