Jacob Klein wrote: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.
Yes - I am sure. I have latest 1703 version Creators Update now, but I am using Windows 10 for a long time, so I have had various previous versions of OS 10 too before this last one. The Coolest - thanks so much for the extra explanation!
Last edited by Naki on Tue Jun 20, 2017 6:10 pm, edited 1 time in total.
i think it is caused by UEFI secure boot, coretemp 1.8.1 is works once i disabled the secure boot (simply change the bios's secure boot -> os type -> other os).
secure soot is often enabled by default on ASUS motherboards.
spooki3 wrote: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.
Last edited by java2 on Wed Jun 21, 2017 3:34 pm, edited 1 time in total.
I am on Windows 10 Version Version 1703 Build 15063.413 with an Intel Core i7 6500U Processor. Core temp 1.8.1 gives me the Driver failed to load issue also. I wanted to put this out there since the last post was a while back. Please let me know if you can help me. I found a small work around but it is a dangerous one. Do an advanced restart, change startup settings and turn off option 7. That will allow Core Temp to run. All versions because it disables Driver signing verification.
Also a note that when I try to disable secure boot my OS fails to load at all and I have to force power down and reset the option in the Bios.
Is it that complicated to implement the UEFi Secure Boot support for Core Temp? Or is the issue non-related? Because I have secure boot enabled on my server [C236 + Xeon] and it works like charm. And I have secure boot enabled on my workstation [X99 + i7] and it's for naught.
Any clue when this issue could be fixed? It's haunting the Core Temp for some year now.
Kind regards
uplink
Workstation cpu: Intel Core i7 6850k @ 4.7 GHz [1.482 vcore] | cpu cooling: EK XLC-Predator 360 | ram: Corsair Dominator 32 GB with Dominator Lights Addon [yay!] | mobo: Asus X99 Deluxe II | vga: Asus Strix GTX 1080 Ti OC | vga cooling: Stock Strix cooler | hdd: N/A | ssd 1: PCi-e Intel 750 1.2 GB | ssd 2: 2 x U.2 Intel 750 1.2 GB @ sw raid0 | psu: SeaSonic Prime SSR-850TD | psu cables: CableMod White Set | case: Fractal Define R5 BlackOut Edition | fans: 6x Corsair ML 120 Pro White | lcd: Acer X34A | sound: Creative X7 | receiver: Onkyo TX-NR616 | speakers: harman/kardon HKTS 35 | mouse: Asus Rog Spatha | keyboard: Microsoft Natural 4000
Server cpu: Intel Xeon E3-1275 V6 | cpu cooling: SilentiumPc Fortis 3 he1425 v2 | ram: Kingston HyperX 16 GB non-ECC | mobo: Asus p10s ws | vga: iGPU | hdd: 4 x WD Red Pro 3TB @ raid0 & raid1 | ssd 1: M.2 Samsung 960 Evo 256 GB | psu: Be quiet! DARK POWER PRO 11 550W | psu cables: stock | case: Fractal Define R5 White Edition | fans: 4x Corsair ML 140 | sound: disabled
I expect to have an update out early next month that will sort this problem out.
You're welcome to read the first post in this thread to understand why this problem is happening.
The Coolest wrote:I expect to have an update out early next month that will sort this problem out.
You're welcome to read the first post in this thread to understand why this problem is happening.
Sorry for me being dumb. Didn't find this thread. Anyway, great job on the program. Will send u some cash as a support! [and I did ]
Workstation cpu: Intel Core i7 6850k @ 4.7 GHz [1.482 vcore] | cpu cooling: EK XLC-Predator 360 | ram: Corsair Dominator 32 GB with Dominator Lights Addon [yay!] | mobo: Asus X99 Deluxe II | vga: Asus Strix GTX 1080 Ti OC | vga cooling: Stock Strix cooler | hdd: N/A | ssd 1: PCi-e Intel 750 1.2 GB | ssd 2: 2 x U.2 Intel 750 1.2 GB @ sw raid0 | psu: SeaSonic Prime SSR-850TD | psu cables: CableMod White Set | case: Fractal Define R5 BlackOut Edition | fans: 6x Corsair ML 120 Pro White | lcd: Acer X34A | sound: Creative X7 | receiver: Onkyo TX-NR616 | speakers: harman/kardon HKTS 35 | mouse: Asus Rog Spatha | keyboard: Microsoft Natural 4000
Server cpu: Intel Xeon E3-1275 V6 | cpu cooling: SilentiumPc Fortis 3 he1425 v2 | ram: Kingston HyperX 16 GB non-ECC | mobo: Asus p10s ws | vga: iGPU | hdd: 4 x WD Red Pro 3TB @ raid0 & raid1 | ssd 1: M.2 Samsung 960 Evo 256 GB | psu: Be quiet! DARK POWER PRO 11 550W | psu cables: stock | case: Fractal Define R5 White Edition | fans: 4x Corsair ML 140 | sound: disabled
I can't PM directly 'cause this account is still too new, but the preview build for 1.8.2 appears to be working perfectly on Win10 ver 1703 with no such driver error, great work!
Muffin wrote:I can't PM directly 'cause this account is still too new, but the preview build for 1.8.2 appears to be working perfectly on Win10 ver 1703 with no such driver error, great work!
yo muffin (great usrname btw)....where do i download this preview build?
Core Temp V1.9 x64 is working great on all my systems which have Windows 10x64 Pro Build 15063.447 V1703 and Insider Build 16237. Thanks for all your effort to make this very useful application work successfully on Windows 10.
Windows 10 x64 Pro on ASUS Maximus VIII Extreme motherboard, i7-6700k CPU, 64 gbyte RipJaws DDR4 3200 RAM, Samsung 970 Pro NVMe M.2 512 gbyte SSD, Samsung 850 Pro 512 gbyte SSD, EVGA Nvidia GeForce 980 Ti (Home Built System) Windows 10 x64 Pro on Dell 8700 SE desktop, Intel i7 4770 CPU, 24 gbyte RAM, Samsung 850 EVO mSata 512 gbyte SSD, Samsung 850 Pro 512 gbyte SSD, AMD R270 graphics, Windows 10 x64 Pro on Dell XPS 15 (9575) 2in1 laptop/tablet
ASUS RT-AC88U router, 8 tbyte WD My Cloud Mirror.External Drive, 100 Mbps cable Internet, Google Chrome, MS Office 2016 (Local), Casper 10, DisplayFusion (3 Flat Panel Displays per system) Kaspersky Internet Security 2020, Malwarebytes 3, SpywareBlaster, HostsMan, Quicken, Weather Watcher Live, Sticky Password 8, Unchecky, WD Smartware, CyberLink PowerDVD 19, and many more.
To The Coolest:
I just tested Core Temp 1.8.2 (from the CoreTemp27.rar you linked to in a pvt msg), and the 64-bit version works great on my Win 10, UEFI, Secure Boot, i3-7200U system. Yeah!
[quote="The Coolest"]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.
I'm sorry but where is version 1.9 ?
My apologies for not replying sooner (the PM notification went into my spam folder). I installed the updated 1.8.1 and it ran successfully on Windows 10. Updated to 1.9 and it is also running without the unsigned driver warning. The only issue I had was the old Windows gadgets would no longer interface with Coretemp. That was solved by using temp monitors with Rainmeter.
It was enabled but still would not work. Tenforums theorized Microsoft specifically disabled gadget interface with the .Net framework with the Fall Creator's update. Guess they caught wise to the 3rd party Windows gadget patches.
radji wrote:It was enabled but still would not work. Tenforums theorized Microsoft specifically disabled gadget interface with the .Net framework with the Fall Creator's update. Guess they caught wise to the 3rd party Windows gadget patches.
Which gadget pack/software did you use prior to RainMeter, please?
No, please note Microsoft did not catch up (yet - hopefully they will not ever). I use 8GadgetPack on my Windows 10 PCs - I have several - and it works fine with '2017 Fall Creator's update Insider Preview build, same way it worked with CU (released April/May 2017), AU and older versions of the Windows 10 OS.
You can download it here: http://8gadgetpack.net/
Like with every new Windows 10 build I update to, I just have to fix the 8GadgetPack installation, which it alerts me to do on first login after the new Windows 10 build update.
All my gadgets work fine, but I do not use Core Temp gadgets here, I can check those also.
radji wrote:It was enabled but still would not work. Tenforums theorized Microsoft specifically disabled gadget interface with the .Net framework with the Fall Creator's update. Guess they caught wise to the 3rd party Windows gadget patches.
I have had no problems using 8GadgetPack v23.0, on any flavor of Windows 10, including Fast Ring builds and Fast vNext Ring builds. Granted, I don't use any CoreTemp plugins, but the gadgets I normally use are working just fine, including one that requires .NET 3.5 (and has Windows 10 auto-install it).