ALCPU Forums

1.0 RC9 loads for me without the Driver wont load issue (later ones have the issue, funny though as it has only occurred since i re-installed windows 10 Pro. Previously on my old win 10 pro installation, 1.4.1 worked flawlessly)..

Also 1.0 RC9 does not show temps in the CPU gadget.. CPU gadget reports CoreTemp is not running..

Any solutions?

As explained in this thread, this issue only affects clean installations of Win10 AU. Any older OS upgraded to AU will not have this new driver signature enforcement.
Please read the last post I made (on the previous page).

Make sure you turn on .Net 3.5 in Windows features to get the gadget to work right.

Secure boot disabled = Core temp driver loaded



On Server 2016

hey alcpu so i have literally just formatted my pc with a fresh install of windows 10 and core temp will install fine but as soon as i go to open it all i keep getting is "Driver has failed to load. This program will not continue." is there a fix for this?

The only solution right now is to use version 1.0 RC9.
http://www.alcpu.com/CoreTemp/oldversions/CT10-rc9.zip
More info here: http://www.alcpu.com/forums/viewtopic.p ... =50#p14206

I too had to re-install Windows 10, so now I can't use Core Temp anymore. Installing version 1 RC 9 is not an option. I use the program in combination with the System Monitor desktop-gadget to not only display core temperatures, but also processor frequency. The problem is that RC 9 does not display the CPU frequency of my processor (Intel Atom Z3700) right. It always reports a frequency of 1333 MHz, even when the processor is in Turbo mode on a frequency higher or lower than the standard 1333 Mhz. Version 1.5.1 did display the right frequency (until I had to re-install W10AU), So,please find a solution to the driver signing problem.

Hi,

I want to report that I also can't install Core Temp. wanted to do so after reading in detail the very extensive and incidentally very recently (yesterday) updated "Intel Temperatures Guide" here:
http://www.tomshardware.co.uk/forum/id- ... 1480693270

My build and Windows 10 installation is brand new from Dec 27 or so. I have installed all updates and quite a few utilities, pretty much all of them work. Core Temp is one rare odd man out.

I'm wondering, why is there a need to use this particular certificate scheme you are using with Comodo? Pretty sure none of the other utilities I've installed use anything like that, or if they do, theirs work. Is it because of security that Core Temp uses this? (I mean, couldn't we just check signatures manually as when downloading a linux iso?)

My build is this one:
http://www.passmark.com/baselines/V9/di ... 4377821047
http://www.userbenchmark.com/UserRun/2435570

All the best,
Raul

Some of you people need to read and be more understanding, hes stated he knows the issue and is working to fix it and it requires money and time. some people are so ungrateful and demanding. thanks for all the work, i feel naked without coretemp

@Ilex @raulinbonn:

The Coolest wrote:The only solution right now is to use version 1.0 RC9.
http://www.alcpu.com/CoreTemp/oldversions/CT10-rc9.zip
More info here: http://www.alcpu.com/forums/viewtopic.p ... =50#p14206

BxH013 wrote:Some of you people need to read and be more understanding, hes stated he knows the issue and is working to fix it and it requires money and time. some people are so ungrateful and demanding. thanks for all the work, i feel naked without coretemp

Thank you.

My surface pro 4 and diy pc running win 10 and both get driver load failure error

I appreciate the reports guys, but it's not really helping as the issue is well known by now.
Sadly there were some setbacks in the funds department, sorry.

@java2 please check the post above yours.

I found that v1.5.1 have two signatures signed by SHA1 and SHA2 certificates.
For 1.0 RC9 (workable on my pc) just have one signature signed by same SHA2 certificate. Just wonder why 1.5.1 have dual signatures and windows 10 may not be able to authenticate SHA1 signature, SHA1 signing should be deprecated in win10.

The Coolest wrote:I appreciate the reports guys, but it's not really helping as the issue is well known by now.
Sadly there were some setbacks in the funds department, sorry.

@java2 please check the post above yours.

SHA256 isn't supported by Vista and by Win7 (without SP), thus the file appeared as if it was unsigned on those operating systems. This isn't a big issue for the executable, but it also prevented the OS from loading the drivers... Dual signature allows older OS to see a valid signature, and it also allows the file to have a valid and more secure SHA256 signature, which has already become a requirement.
It's common practice, you can see that CPU-z has dual signatures as well.

Just FYI, I have had much difficulty with MS on these driver digital signatures with the latest preview updates on Windows 10. I asked MS to give us a GPO to exempt hardware ID's from the security. They said they would take that under consideration for a future update. I have lab equipment using old USB drivers that just don't work anymore. I know this is all out of scope for your issues, but thought I would pass it on and let everyone know this is a big issue for a lot of people.

Hello
i just tried to install Version 1.6 on a Win 10 x64 machine and got 'error driver failed to load' when i rebooted
the earliest version that i can run is 1.0RC9
Thank you
Wøødy

OS Name Microsoft Windows 10 Pro
Version 10.0.14393 Build 14393
System Manufacturer MSI
System Model MS-7978
Processor Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz, 3192 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. B.90, 2016-12-21
SMBIOS Version 3.0
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer MSI
Platform Role Desktop
Secure Boot State On
PCR7 Configuration Binding Not Possible
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = "10.0.14393.206"
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 16.0 GB
Available Physical Memory 11.8 GB
Total Virtual Memory 17.0 GB
Available Virtual Memory 12.3 GB
Page File Space 1.00 GB
Page File C:\pagefile.sys
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

@Woody033
Please read the topic above.
Specifically the first part of the first post with the links to the relevant posts.

The Coolest wrote:@Woody033
Please read the topic above.
Specifically the first part of the first post with the links to the relevant posts.

My apologies The Coolest...

Is there an expected resolution for this issue in the near future?
Bob

Just an update. I placed an order for an EV code signing certificate.
Validation, processing and shipment of the hardware token will most definitely take some time, though. I hope it won't take longer than a month, but I'm not sure since we're just getting started.

is this the same issue like bluescreen on boot with "cricical service failure" ?
0x0000005A

It isn't. I replied to your thread.

The Coolest, thanks for the feedback. Bob

I had to clean install Windows 10 (which updated me to the Creators Update) and now Coretemp will not start at all. It give the Driver has failed to load error. I am running Windows 10 Home 15063.250

Suggestions?

Please read the first post of this thread:
http://www.alcpu.com/forums/viewtopic.p ... 082#p14082

The Coolest wrote:Please read the first post of this thread:
http://www.alcpu.com/forums/viewtopic.p ... 082#p14082

Did and done. I am a bit annoyed Core Temp 1.7 starts fine on my Surface Pro 4 (also has Creators Update) but will not on my Alienware after a clean install. M$ needs to get it together.