ALCPU Forums

Please read the first post of this thread.

Synergiance wrote:As the title says, I'm getting a message saying the driver failed to load and core temp can't run, after updating to 1.1, my previous version works fine, so I have that running, not sure what changed with the driver in 1.1 that caused it to refuse to load but I'd like to help diagnose if I can

What OS are you using?

Fyi, regarding my situation, I still have the same problem with Windows 10 Build 14390, but I've decided not to reinstall the partition this weekend. Maybe next weekend . . .

I reinstalled my partition. I'm not having the signature problem, so far, but I'm still on Windows 10 Release (1511). I've hopped back into the Fast ring, and am awaiting to be targeted with the Windows 10 Insider (1607) build - Will let you know the result after it's upgraded.

This applies to Windows 10x64 Pro Build 14393.10

I am having this same issue of the driver failing on Core Temp V1.1 on my Dell XPS 8700 on a fresh install of Build 14393.10. On this specific computer, I started experiencing the problem 14393.50 upgraded to 14393.10 via Windows Update....and that's when I decided to format and do a fresh install in an effort to resolve the issue.

I'm not experiencing this problem on my Surface Pro tablet or my home built ASUS ROG Maximus VIII Extreme computers, both with Windows 10x64 Build 14393.10 upgraded via Windows Update.

Malwarebytes Anti-Exploit was having the exact same problem as Core Temp V1.1. The developers issued a new build with countersigned Microsoft digital certificates and that fixed Anti-Exploit

https://forums.malwarebytes.org/topic/1 ... nt-1054724

Sorry for the delay in response. I got it upgraded to the 1607 version, and now all is well.
So, I have no idea really what the true problem was, but somehow my security store must have been corrupted on my previous installation. This new installation is working great!
Keep up the great work!

Well, I now have 2 machines with this problem. One is a Dell XPS 8700; the other is a MS Surface Pro tablet. Both of these computers I formatted and performed a total re-install of Windows 10 x64 Pro Build 14393.10. So the issue/bug appears to be quite solid when a fresh install of Windows 10 x64 Pro is performed.

Same problem here: Core temp 1.1 driver failed to load on a complete fresh windows 10 installation (version 1607 build 14393.10)

Core Temp V1.2 did not resolve the driver failure issue on Windows 10x64 Pro Build 14393 or 14901.

Core Temp 1.2 - Driver failed to load in windows 10 PRO X 10.0.14901.1000.rs_prerelease.160805-1700. Really Bad.

Can you confirm that, on a completely fresh install of Windows 10 (with NO OTHER SOFTWARE), that Core Temp still fails for you?

Hi guys, I am aware of that. I'll be working on figuring out what's causing this problem.

This is a known issue and it's beeing worked on. Try 1.0 RC9, it should still work.
http://www.alcpu.com/CoreTemp/oldversions/CT10-rc9.zip

Hey guys, could you please try the following?

1. Download this file: https://support.comodo.com/index.php?/D ... al-ca-root
2. Right click and install it.
3. Try to start Core Temp again.

Hi, I've been following along here, with a brand-new install of Win 10 v1607 where CoreTemp 1.1 / 1.2 won't load. I downloaded the above cert and opened it for inspection with Windows Explorer.

Under "Certificate Information" it says "Windows does not have enough information to verify this certificate". Hmm. The certification path includes just "AddTrust External CA Root" and its status is: "The issuer of this certificate could not be found."

I checked my cert store and there is indeed a valid "AddTrust External CA Root" cert, in the "Trusted Root Certification Authorities" branch of the store, issued by and issued to "AddTrust External CA Root", and certified by "The USERTrust Network(TM)".

So it looks like it should work but I'm guessing something is broken in the cert chain between those two. And no, CoreTemp 1.2 did not run after I installed the downloaded cert, sorry!

I tried the cert and Core Temp 1.2 driver still fails.

Please note that there are several selectable elements when installing this Cert via Windows 10 x64, Can you state specifically which items to select during the installation of the cert? Maybe I selected the wrong items.

RC9 does work on my machines but I'd surely like to run the latest versions.

Here's some interesting information.
Turning off Secure Boot may enable the driver to work.
http://www.thewindowsclub.com/driver-si ... windows-10

When secure boot is off, core temp 1.2 is working with a clean install windows 10 anniversary update.

But is it harmfull that secure boot is off??

Yes, disabling "Secure Boot" does permit Core Temp v1.2 to run. HOWEVER, I don't think its the best step to take (disabling Secure Boot) to maintain maximum security on one's system.

Alright, at least everything seems to make a lot more sense now.
I also agree that disabling Secure Boot is not something I would normally recommend. I was only asking to check and see whether it would work.

What this means is that I will have to get an EV Code Signing certificate, which is usually a lot more expensive than normal certificates. In addition to that not all providers can supply an EV certificate. The company I work with is currently in process of enabling the EV certificate program, so we will have to wait until that is available.

Core Temp 1.2 - Driver failed to load. The same problem With 1.1. With the 1.0 RC9 work FLAWLESS.

=(

Please read the last few posts above.

Ok, esto me canso. La culpa del problema siempre es de los demás. El programa / driver posterior a la versión 1.0 RC9 FUNCIONAL MAL / TIENE ERRORES GROSEROS y el autor insiste con que el error es de los demás cuando está a la vista que no puede / no sabe resolver los errores de programación. Voy a tener que buscar una solucion ALTERNATIVA por el momento y regresare mas adelante a ver si finalmente estos errores se han resuelto. Bye To all.

Rayitas wrote:Ok, esto me canso. La culpa del problema siempre es de los demás. El programa / driver posterior a la versión 1.0 RC9 FUNCIONAL MAL / TIENE ERRORES GROSEROS y el autor insiste con que el error es de los demás cuando está a la vista que no puede / no sabe resolver los errores de programación. Voy a tener que buscar una solucion ALTERNATIVA por el momento y regresare mas adelante a ver si finalmente estos errores se han resuelto. Bye To all.

Google Translate
Ok, this I get tired. The problem is always the fault of others. The program / rear driver to version 1.0 RC9 FUNCIONAL MAL / HAS gross errors and the author insists that the error is of others when it is visible that can not / can not solve programming errors. I'll have to find an alternative solution for the moment and be back later to see if finally these errors have been resolved. Bye To all.

All 64bit Windows operating systems since Windows Vista require drivers to be digitally signed.
RC9 works fine because it uses an older driver, which was digitally signed in February, by an old digital signature certificate, and it doesn't fall into the range of Microsoft's new signature enforcement methods. The drivers in the new versions were signed in early July, and it looks like the date is beyond the threshold where Microsoft has implemented their new signature enforcement methods.
Obtaining a digital signature is not a small investment, especially for developers of free software. But obtaining an EV certificate is a lot more costly than the 'standard' variety you can get today at acceptable rates.
I just want to make it clear that there are no "programming" errors to fix, and that I'm not blaming anybody, I just was not aware of this issue prior to it becoming a problem.
The company I purchased the current digital signature certificate from told me that they will be launching an EV digital certificate program very soon, and I will be looking at upgrading what I have right now to it when finances allow.

Driver has failed to load

Win 10 x64 (1607 14393.67)