Update 4:Core Temp version 1.9 has Microsoft's signature on the drivers now, so it should work fine on any Windows 10 machine.

Update 3: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.

Update 2:I placed an order for an EV code signing certificate. It will probably take a while for me to get it and to receive the hardware token by mail, though. As soon as I get it, Core Temp will be updated with properly signed drivers and this issue will be resolved. Until then you can keep using version 1.0 RC9, as it's the latest one that will still work.http://www.alcpu.com/CoreTemp/oldversions/CT10-rc9.zip

In case you encounter this problem with the latest 1.1 version (or future versions) please read this post for some information on the problem.

The source of the problem is the new digital signature of the Core Temp driver. This version comes with an updated driver, which is signed with the new digital signature certificate.This certificate can only sign using the SHA-2 algorithm, and can't co-sign using the deprecated SHA-1 algorithm that older operating systems support. Because of this, Windows can't interpret this signature and considers it invalid. Thus a 64bit OS will not allow the driver to load and start.Windows 7 requires a patch to add support for SHA-2 based digital signatures. You must have SP1 installed for the patch to work on your OS. (Sadly at this time this version will not run on Windows Vista 64bit, and I'm looking for a solution)This update is required for Core Temp 1.1 and all future versions to work (in case you encounter this problem), otherwise you can keep using 1.0 RC9.http://www.alcpu.com/CoreTemp/oldversions/CT10-rc9.zip

It seems to be an odd problem with your machine. Core Temp works fine on Win10, but on your specific machine Windows can't validate the digital signature of the driver.I'm not sure what the reason for this problem is yet, but with more information I can try to find out.Please go to Event Viewer, Windows Logs, System. There should be a series of "Errors" with ALSysIO info in it.Take a screenshot of this and post it here please.

I agree. Something is odd about this particular "Windows 10 Insider Build 14379" PC, because I did more testing, and Core Temp v1.1 installs and runs just fine on my other 3 "Windows 10 Insider Build 14379" PCs.

For the PC with the problem, when I launch Core Temp v1.1, it immediately generates 48 events in Event Viewer. 16 sets of the following 3 messages, below.

I'll try to troubleshoot further, by uninstalling apps that may be interfering (like Visual Studio Community 2015? Intel Extreme Tuning Utility? CPUID?)... but if you have any insight into the cause of this problem, I'd love to have it fixed.

Log Name: SystemSource: Application PopupDate: 7/4/2016 11:28:10 PMEvent ID: 26Task Category: NoneLevel: InformationKeywords: ClassicUser: N/AComputer: SpeedDescription:The description for Event ID 26 from source Application Popup cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\??\C:\Users\Jacob\AppData\Local\Temp\ALSysIO64.sys failed to load

the message resource is present but the message is not found in the string/message table

So I just installed Insider build 14366 which is the latest one available for download as an ISO from Microsoft. On that OS Core Temp is actually working just fine.Both the test versions I sent to you and the released 1.1.Did you update to this build through MS or did you use some sort of method to construct the ISO to install it? I think it's possible that non-official builds could be broken in certain aspects.Of course it's possible that MS changed something in 14379 which broke the way Windows interprets the digital signature I have.

Please do the following:Start --> MMC --> File --> Add\Remove snap in.Add Certificates for Local Computer. Click OK.In the list go to Trusted Root Certificates Authorities --> Certificates, right click Certificates and Export list. This will create a text file.Do the same for Third Party Root Certificates Authorities.Please upload these files. I'd like to take a look, see if I can find anything that's wrong there.

The ALSysIO service failed to start due to the following error: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

The iocbios2 service failed to start due to the following error: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

... it will run, but doesn't allow me to see/edit any my CPU features/overclocks.The old version, "Intel® Extreme Tuning Utility (Intel® XTU) v6.0.2.8.exe", installs and runs just fine with no problems.

I spent the better part of this evening, testing.- Upgrading from Visual Studio 2015 Update 2, to Visual Studio 2015 Update 3... did not fix the problem.- Uninstalling Visual Studio 2015... did not fix the problem.- Uninstall other related components (SQL Server, components, Speech components)... did not fix the problem.- Uninstall all Redistributables... did not fix the problem.- Uninstall Oculus Rift software... did not fix the problem.

I've noticed that there are items in the Windows Feedback app, indicating that this might be a semi-widespread issue on the 14xxx Windows 10 Insider builds. People are complaining about updated CPU drivers that don't work/install/start, and updated audio drivers that don't work/install/start, all with the error "Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source."

My current hunch is that, perhaps on a UEFI BIOS (which my main rig has), recent Insider builds have problems with newer signed executables. As a reminder, Core Temp 1.1 installed just fine and works, on all of my 3 other non-UEFI PCs.

If I'm feeling up for it, I might consider a fresh reinstall of this Insider (my main) partition, this-coming weekend. But I'd LOVE for you to convince me not to Please?

Keep in mind, Core Temp 1.1 was working just fine on my 3 other PCs that were using the same build. So, I now suspect that the certificate store was updated/reset/fixed when the new build was installed, and that this still could be a problem if something messed it up in the first place, like Visual Studio.

I'll do a little more testing in the upcoming days, but I'm very relieved that I don't have to reinstall my partition

What the crap.... I had a notification that said "Finish installing device software", I clicked it, I restarted, and now the 2 programs don't work again. Making progress to ironing this out! But I don't know what that notification did.

The goal is to determine what "Finish installing device software" actually does to my machine, and also determine if it's causing my problem.Are we having fun yet? I'll report back when I know more.

PS: For some reason, I'm NOW getting an actual error during the installation of XTU 6.1.2.8. It still installs, and then fails to register the service, and then launches with most overclocking options missing. If I uninstall the new version, and install the old version, the old version works just fine.

The error is:Program Compatibility AssistantA digitally signed driver is requiredWindows blocked the installation of a digitally unsigned driver. Uninstall the program or device that uses the driver and check the publisher's website for a digitally signed version of the driver.

Hmm.. Well, my test results are basically: The same problem is happening on Build 14385 on this PC, and .. I was able to use the newer versions right after installing the Build, and after clicking "Finish installing device software"... but after the first restart, they didn't work. The certificate stores remained the same. I honestly don't know what's going on yet.

My next test will involve restarting, WITHOUT clicking the "Finish installing device software".

Sorry it feels like I'm grasping at straws. Doing the very best that I can. Once I run out of valid tests for the "build upgrade" scenario, then I will proceed to "fresh-install partition from ISO". Not looking forward to it lol!

I finally managed to get my test machine updated to the latest build - 14385. I have not seen any dialogs to "finish installing device software". And Core Temp works just fine.I suspect that there could be some driver package which messes some things up with the driver signature enforcement (or the certificate store) on your machines.

Still trying to troubleshoot this problem (before throwing in the towel and rebuilding the partition... a task for next weekend perhaps).Anyway, sfc did not return any problems. If you can think of anything else you want me to try, let me know.

I did another test with the new Windows 10 Build 14388, released today. I installed the build, was able to use Core Temp 1.1, restarted the PC, and then was unable to use it. So, I've concluded that the problem has nothing to do with the "Finish installing device software" notification. But I'm no closer to solving the problem.

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