Core Temp 1.1 - 1.8.1 - Driver failed to load

[catcher40]

Any news on the driver not loading problem with windows 10 x64 pro creators update. still using CT10-rc9.

[The Coolest]

After what seemed like an eternity and a lot of headaches and runabouts, I can finally say that my certificate is on its way.
So I hope that within 2-4 weeks I should have it and be able to sign drivers in a way that Win10 will find acceptable.

[catcher40]

Nice, thank you for all the time and effort you've put into this.

[justen_m]

Yes, thanks for all the effort! My systems feel naked without Core Temp running and the temps down in my task bar for each core.

I just wiped the drive on my old system, re-installed Windows 10 Creators Update, and Core Temp 1.7 wouldn't work. It did before. Reading this entire thread, I realized why. My old system, I turned off Secure Boot. This time, I wanted to keep it around, probably best, security-wise heading into the future. I downloaded 1.0rc9 that you linked to and that works fine with Secure Boot enabled. Thanks for that link, too.

So, in 2-4 weeks, what new version will have the new certificate? 1.8... or 2.0!

[fjsorg]

After what seemed like an eternity and a lot of headaches and runabouts, I can finally say that my certificate is on its way.
So I hope that within 2-4 weeks I should have it and be able to sign drivers in a way that Win10 will find acceptable.

Hello The Coolest,
With your latest version, I did not have a crash to load the drivers.
To see with time

lol FJ

[The Coolest]

@justen_m

It could be a hotfix, or a new version, depending on the state of development. Since I don't consider this to be a new feature, or even a bug fix.

@fjsorg

This is only a problem on Clean Win10 Anniversary\Creator's Update installations with Secure Boot enabled in the BIOS.

[justen_m]

It could be a hotfix, or a new version, depending on the state of development. Since I don't consider this to be a new feature, or even a bug fix.

We know it's not a bug. Don't make it a hotfix! This isn't a bugfix, but it adds support for a new version of Windows. That _is_ new functionality. As a software engineer (retired), I am saying, I think this merits a bump to 2.0. It will help you, support-wise. Just tell people to upgrade. Much easier than explaining why they should. You have the opportunity to cut support for antique software. Take it!

[The Coolest]

Well, my perspective on this is a little different.
It's Microsoft's artificial limitation imposed on software developers. Core Temp still runs fine on all Windows 10 releases if that 'feature' of the OS is disabled.
Also, up until a few years ago Core Temp even ran on Windows NT 3.51, but sadly after I moved away from Visual Studio 2008, it became impossible, so right now it requires a minimum of Win2k + sp4 + a few hotfixes. Personally, I like backward compatibility, a lot

[fjsorg]

Well, my perspective on this is a little different.
It's Microsoft's artificial limitation imposed on software developers. Core Temp still runs fine on all Windows 10 releases if that 'feature' of the OS is disabled.
Also, up until a few years ago Core Temp even ran on Windows NT 3.51, but sadly after I moved away from Visual Studio 2008, it became impossible, so right now it requires a minimum of Win2k + sp4 + a few hotfixes. Personally, I like backward compatibility, a lot

Hello,

I do not agree. I have a lot of PCs under W10 (a dozen, Acer, Asus, Dell, HP, " in Secure Boot " under 1607 and 1703 ... with Core Temp 1.7 ... there is no problem.

The problem, it is serious, but hardware ... Motherboard Asus latest generation ... Like mine X99 ... I am not too dissatisfied, but in three years I had good numbers of bugs

But maybe I'm not on the right topic

But if you speak French, tell me in MP. I'm not sure I understand English. Sorry

[fjsorg]

Hello,


I will continue there, The Coolest , You will move as needed

(Asus X99-Deluxe/ i7-5820K)

http://i.imgur.com/zuuXRJs.jpg

http://i.imgur.com/eWWAoMt.jpg >>>>> But if I put Storages Devices, preferably Uefi drivers ... Ben it changes nothing at all ... for Core Temp ... for W7 / W8.1 and W10 this boot

http://i.imgur.com/DAkewlF.jpg

Ok ^^^^ ?

If something is not good ... say it ?

I boot in safe mode under W10 Pro 1703 (is installed in Uefi)

... in Legacy under Pro W7 / W8.1 (It is installed in double boot mbr)

It's correct ? ^^^^

I do not know, but it works ... Not without evil ... lol ... ah ah ah

@ + FJ

[The Coolest]

Well, i don't know how it works, as long as it does.
Microsoft does allow to load drivers in some situations, I guess in your specific case it works.

[fjsorg]

Well, i don't know how it works, as long as it does.
Microsoft does allow to load drivers in some situations, I guess in your specific case it works.

Hello,

I'm talking about PC builder, laptop in general.

[matsuda0707]

I installed 1.8 today, but error telling "driver failed to load" sa same sa 1.7.1.
My PC is MS Surface pro 3 and Windows10 pro 1703 (creative update).

[siliconman01]

"Driver failed to load" error continues to occur with Core Temp V1.8.1 on Windows 10x64 Pro Build 15063.332 V1703.

[spooki3]

Hi The Coolest

I believe the driver failed to load problem is limited to Asus products. Loads lot of different PC's in a month and only Asus motherboard Pc gives this error by me. All other work fine even with 1.81 but Asus boards all give driver load problem.

Maybe it is hardware compatibility problem with Asus boards.

[The Coolest]

It's not, please read first post.

[gk1957]

I'd like to report that CoreTemp 1.8.1 loads successfully on my ASUS Z170-PRO MB running Win 10 x64 Pro v1703 (w/June patches). I had checked v1.7 in March and it was not working. Since then, I've installed the v1703 Win 10 feature update and at least one BIOS update. I'm guessing one (or both) of those two updates helped!

[fjsorg]

Hello,

Sorry, on all my PC under W10, they support very well version 1.8.1

On my main machine (Asus X99-Deluxe, i7-5820K), under W10 OK version 1.8.1, under W7 / W8.1 error load drivers every time, back to Core Temp 1.7.1
(Finally under W8.1, this is load error with both versions, 1.7.1 and 1.8.1)


Greetings

[fjsorg]

Hi The Coolest

I believe the driver failed to load problem is limited to Asus products. Loads lot of different PC's in a month and only Asus motherboard Pc gives this error by me. All other work fine even with 1.81 but Asus boards all give driver load problem.

Maybe it is hardware compatibility problem with Asus boards.

Hello,

It is almost certain

(On Asus Rog G75V, with W10 and version 1.8.1 no load worries)

[Naki]

Exactly nothing to do with ASUS or any one particular mainboard manufacturer, sorry! The program's creator already explained the issue reason quite clearly several times, so please do not question that.
You could have as ASUS or ASRock or GIGABYTE/etc mainboard, and it could fail. And you could have another one from same brand, but a different socket/generation, and it could work just fine with Core Temp.
So, not brand-dependent at all - likely more like some Intel chipsets/mobos work, others not. Same for AMD ones.

Please note Core Temp, any version, works fine for me on 6-7 separate WIndows 10 PCs, but these are all quite old compared to what is popular in 2016-2017 - most of them are Intel socket 1155, with just 2-3 PCs on the a bit newer socket 1150.
So, I tend to think older mobos more likely work, and newer ones are more likely to fail.

[Jacob Klein]

...
The program's creator already explained the issue reason quite clearly several times, so please do not question that.
...
likely more like some Intel chipsets/mobos work, others not. Same for AMD ones.
...
So, I tend to think older mobos more likely work, and newer ones are more likely to fail.

Why would you say "the dev made it clear what the issue is", and then you continue to guess?!?
Did you even READ post 1? Did you even LOOK at the reference links within post 1?

Let me try to clear it up for you a bit.

It is my understanding that 64-bit PCs, running a modern updated/patched 64-bit OS, recently require that signed drivers be signed more-stringently (drivers must be signed with newer safer algorithms). The dev had to work out how to purchase materials needed to make that happen. The fix has not yet been released. We suspect that the problem may be limited to users who are running "Safe Boot" in their BIOS. If you are hitting the problem currently, then turning "Secure Boot" to OFF in your BIOS, *might* help as a workaround, as it seems the OS recognizes this and relaxes the security a bit. Or you could use 1.0 RC9, which was signed at a "digital signature time" that was before the cutoff, and as such is still "accepted" by the OS, allowing the driver to load, even if "Secure Boot" is ON.

It has NOTHING to do with CPU type or motherboard manufacturer. Sheesh.

[Naki]

I am NOT hitting the problem currently, on ANY of my many PCs - all running Windows 10 64-bit OS, all using Secure Boot/UEFI AND latest Core Temp version. Yes, the developer explained this clearly. I am sorry if you cannot get it.
I do know newer PCs, which I have none of, cannot properly work sometimes.

I am not guessing anything. The issue is clear and will be fixed, it just takes some time (and cash to be paid by the dev!).

[Jacob Klein]

Secure boot is an option within the UEFI settings. Are you absolutely sure you have it enabled? Also, are you absolutely on version 1703 or 1607? Just trying to learn more about the issue.

[The Coolest]

This issue affects systems that have Secure Boot enabled and have a clean Windows 10 Anniversary or Creator's update install. If you had the original Windows 10 (or older version) installed and then upgraded to the latest release, your system won't be affected.
It's possible that there will be situations in which this digital signature enforcement will be disabled even on clean installs, but I'm not aware of what it may be.

[Jacob Klein]

Thank you for the clarification!