fixed: Sensors are not recognized (Windows 10 Insider Preview Builds 16273, 16275, 16278)

[norti]

Hi Fiery!

On the latest Windows Insider build from today

and with the latest beta of AIDA64

most of the sensors are not recognized. Can you please look into this? Or should I reinstall AIDA64 and see if this solves the problem?

Thanks!

norti

[kpo127]

Same here. Reinstall did not help. Thanks

[Trigger2142]

Same here. Should I go back a version?

 

[kpo127]

I don't think it would help. I just uninstalled it and waiting for a fix or even a response. Since it's close to rtm something must have changed.

[kpo127]

Another build just released, same issue build 16275 release 3

[kpo127]

There are 6 entries on Windows Insiders Feedback, up vote if you want.

[kpo127]

 

• Drag files here to attach, or choose files...
  Max total size 11.59MB
   
• Insert other media

Uploaded Images

•  
•  

 

[ViRuS2k]

I'm having the same issue, latest beta of aida32 on windows build 16275 RC3 

no sensor information is being detected apart from gpu voltages not even motherboard information is being detected or proper cpu detection either or psu detection....

and that's on the latest aida32 build 5.92.4337

 

this issue has happened because of the last 2 windows 10 insider build updates if you want it working again your going to need to revert back 2 build updates on windows 10

or wait for a aida64 fix with update.....

[norti]

So it seems, it's a Windows 10 bug, hopefully they will fix this until the Fall Update.

[Fiery]

We wanted to wait to tell final judgement on this issue until we have more info and more input.  It's a Windows 10 bug indeed that plagues Windows 10 Insider Build 16273 and 16275, but only the 64-bit editions.  It prevents certain software to install and use its otherwise perfectly fine kernel driver.  The issue affects several software, not just AIDA64.  We're already working on a workaround, but we also expect Microsoft to fix this up soon.  I'll post a message into this topic once we have an update.

[Fiery]

We've implemented a workaround for this issue in the latest beta version of AIDA64 Extreme available at:

https://www.aida64.com/downloads/latesta64xebeta

After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

Let me know how it works  

[pbcopter]

The work around in the beta, 4341 fixed this problem for me. 

[kpo127]

Same here. Thank you.

[kpo127]

New Windows build 16278 just released, and Aida64 is broken again, same as before latest beta was released.

Edited August 29, 2017 by kpo127
add screen shot

[norti]

20 hours ago, Fiery said:

We've implemented a workaround for this issue in the latest beta version of AIDA64 Extreme available at:

https://www.aida64.com/downloads/latesta64xebeta

After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

Let me know how it works  

It worked (although temperature updates were a little slow)... until W10 Insider build 16278 dropped in 

[Fiery]

3 hours ago, norti said:

It worked (although temperature updates were a little slow)... until W10 Insider build 16278 dropped in 

You're right, 16278 carries on the issue. We need to release one more AIDA64 hotfix to get around it again.  We'll do that tomorrow or worse case Friday.  I'll post a message into this topic once the new AIDA64 beta build is available for download.

[Fiery]

Here's the new AIDA64 beta that implements the previous workaround for Win10 Insider Preview Build 16278 as well:

https://www.aida64.com/downloads/latesta64xebeta

This time we've made it a bit more future-proof by enabling the workaround between all Win10 builds in the range of 16273 and 16500.

[kpo127]

Thank you Fiery. Works great. 

[Fiery]

1 hour ago, kpo127 said:

Thank you Fiery. Works great. 

Thank you for your feedback.  The workaround should work with RS4 Insider Preview Build 16353 as well

[kpo127]

You're welcome. I am not on skip ahead ring since who knows what Microsoft does anymore and doesn't tell.

[kpo127]

Working fine on 16281 also, thanks.

[Fiery]

On ‎2017‎. ‎09‎. ‎02‎. at 8:08 AM, kpo127 said:

Working fine on 16281 also, thanks.

Thank you for your feedback