- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It would install properly before the Anniversary update. The driver signature needs to be updated.
- Tags:
- Devices
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello everyone,
New tool is available, please go here: https://downloadcenter.intel.com/download/24075/Intel-Extreme-Tuning-Utility-Intel-XTU-?product=66427 Download Intel® Extreme Tuning Utility (Intel® XTU)
Version: 6.1.2.11 (Latest)
Date: 8/22/2016
As for the Intel® Hardware Accelerated Execution Manager (Intel® HAXM) this is owned by a different team and I would recommend that you go here: https://software.intel.com/en-us/forums/android-applications-on-intel-architecture Android* Applications on Intel® Architecture
I have already reported it and I can see a lot of posts on the community.
Please let me know the results with the new XTU.
Regards,
Ronny G
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello CowMix:
I just wanted to let you know that we replicate this same scenario in our lab, and we were able to install the XTU without any problem, after doing the Windows® 10 latest update, and with secure boot enable and disable.
So, at this point, one of the things to try will be to un-install it from the control panel:
Once you get into control panel, look for that option that says: "programs and features" then look for the XTU program, select it and you will see an option at the top of the list that says: "Uninstall".
After that, try to install the XTU tool again from the following link:
https://downloadcenter.intel.com/download/24075/Intel-Extreme-Tuning-Utility-Intel-XTU-?product=66427 https://downloadcenter.intel.com/download/24075/Intel-Extreme-Tuning-Utility-Intel-XTU-?product=66427
Any questions, please let me know.
Alberto
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have the same problem. It appears that the issue happens with a clean installation (not upgrading) of the build 14393.10 of Windows 10.
Even disabling Driver Signature Enforcement, XTU will work untill a reboot.
Here is a link to MSDN for more infos: https://blogs.msdn.microsoft.com/windows_hardware_certification/2016/07/26/driver-signing-changes-in-windows-10-version-1607/ Driver Signing changes in Windows 10, version 1607 – Windows Hardware Certification blog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can confirm the same issue. It was working on Windows 10 but I did a fresh install of Windows 10 this morning and now I get that error message about the driver not being digitally signed - so it blocks the proper installation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same Issue here.
I was an upgrade so it shouldn't affect me ...but I did a System Refresh to revert to a clean install after updating, so I'm assuming that's why. I tried to boot w/ Driver Signature Enforcement Disabled and it still wouldn't let me install it. What are the chances Intel will release a digitally signed installer for this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello:
Thank you very much to all the peers on this thread for the information provided.
We will try to replicate this issue in our lab, as soon as I get any results I will post all the details on this thread.
Any questions please let me know.
Alberto
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Were you able to replicate the issue in the lab? I can also confirm that disabling Secure Boot is a temporary fix for this problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello CowMix:
We are still trying to replicate the issue.
As soon as I get any results, I will post them on this thread.
Are you login into Windows® as an administrator?
You can try to do that by right clicking on the on the XTU file and choose: 'run as administrator".
Please let me know the results of trying that.
Any questions, please let me know.
Alberto
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can also confirm that I tried "Run as Administrator" for both during installation, and even after the driver signing error to see if would run normally anyways. As mentioned by previous poster, even with error the XTU application finishes the install but when you run the application you don't have any of the usual functionality. (Cannot do any CPU adjustments).
Hope that helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello CowMix:
I just wanted to let you all know that I replicate the issue in our lab, and I installed Windows® 10 Home 64 bit from scratch, installed the chipset, management engine, graphics, LAN, audio and wireless drivers, after that, I did the Windows 10 anniversary update, and after that I installed the XTU version 6.1.2.8 with no problems at all, I did not get the message: "A digitally signed driver is required"
So, we will do further research in order to find out what might be the reason why that message is showing.
Any questions, please let me know.
Alberto
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I believe you didn't have the problem we're having because when UPDATING to Windows 1607 (OS build 14393.10) everything works. The problems comes when you do a FRESH INSTALL of Windows Versions 1607 (or in my case using Windows "Reset this PC" feature, which does a clean install.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Alberto,
We all appreciate your help in resolving this issue. I am another user who did a fresh install of Windows 10 (with the anniversary update already installed) and it will not accept the current driver signature. Instead of installing Windows 10 and then installing the anniversary update, try in your lab with the Windows Media Creation Tool. This will allow you to install a clean version of Windows with the Anniversary Update already installed. Here is a link:
https://www.microsoft.com/en-us/software-download/windows10/ Windows 10
You can download the tool and save it to a USB, which will be your recovery media. Then clear the hard drive where Windows is currently installed, and do the fresh install. When you go to install XTU this time, you'll notice it installs fine, but you get a warning that the driver can't be installed because it doesn't have the right digital signature. That's the issue.
Thank you again for your help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello:
I just wanted to let you all know that we will try to replicate the issue using the ISO file for the Windows® anniversary update and the Windows® Media Creation Tool.
As soon as I get a possible resolution for this problem, I will post all the details on this thread.
Any questions, please let me know.
Alberto
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Alberto,
"Perfect, I will try that, even though we also did that already, we installed he anniversary update on a PC that had Windows® 10 already installed and the results were the same."
Updating and/or Windows 10 default recovery options are not the same as using the refresh tool. The refresh tool allows you to install a fresh version of the Anniversary update. Make sure you select to wipe everything when going through the options. If that does not work you can try installing from an ISO created using the Media Creation Tool.
Once you have replicated the issue, you can fix it by following the Microsoft's guidelines here:
https://blogs.msdn.microsoft.com/windows_hardware_certification/2016/07/26/driver-signing-changes-in-windows-10-version-1607/ Driver Signing changes in Windows 10, version 1607 – Windows Hardware Certification blog
Microsoft has changed the way that kernel drivers have to be signed only for fresh installs of the Anniversary update. This is why you can't replicate the issue when updating because that still allows the old signing process. You need to resign the driver using the process stated in the link above and the problem will be fixed.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello:
I just wanted to let you all know that I tried to replicate the issue once again, and the results are the following:
Scenario 1:
I used the Windows Media Creation Tool from the following link:
https://www.microsoft.com/en-us/software-download/windows10/ https://www.microsoft.com/en-us/software-download/windows10/
To install a clean version of Windows® 10 with the Anniversary Update 1607 already installed, clear the hard drive where Windows® is currently installed, and do the fresh install, and I was able to install the XTU tool without any problems, no error message at all.
Scenario 2:
I used the Windows Refresh Tool from the following link:
https://www.microsoft.com/en-us/software-download/windows10startfresh https://www.microsoft.com/en-us/software-download/windows10startfresh
To start with a clean install of the Anniversary Update, I did not install Windows® 10 from scratch and then update to the Anniversary update, I ran this tool on a NUC that already has the update installed, and the results were the same, I was able to install XTU without any problems, there was no error message: "A digitally signed driver is required for Intel Overclocking Device Driver"
So, based on the information above, I just wanted to verify at which point is when you get the error message.
Is it when you try to install the XTU?
Or you can install it, but when you try to use it, then is when you get the error message?
Any questions, please let me know.
Alberto
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In my case, it installs fine but just after the installation is finished and before even launching xtu I get a little window telling me that it couldn't install the driver you mentioned, and then when I launch xtu it's working but a lot of information is missing regarding my cpu for example and I can't use it like I normally did.
Like the others, on a fresh install of Windows 10 with anniversary update.
Edit: to be clear, it's exactly like the screenshot on the first post, install of xtu is successful but the driver was not accepted by windows, as a result xtu does not work as intended.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Still the same error for me. I just installed Windows 10 1607 on a XPS 9550 (with Secure Boot ON, just to be clear) on an empty drive from USB.
When I try to install XTU the installation ends "successfully", but after a few seconds pops up a small error window saying that the Intel driver lacks a proper signature.
I can open XTU, but is completely useless: I cannot see neither modify any parameter.
But if I temporarly disable the Driver Signature Enforcement XTU seems to work...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello:
I just wanted to let you all know that I tried to replicate the issue once again, and the results are the following:
Scenario 1:
I used the Windows Media Creation Tool from the following link:
https://www.microsoft.com/en-us/software-download/windows10/ https://www.microsoft.com/en-us/software-download/windows10/
To install a clean version of Windows® 10 with the Anniversary Update 1607 already installed, clear the hard drive where Windows® is currently installed, and do the fresh install, and I was able to install the XTU tool without any problems, no error message at all.
Scenario 2:
I used the Windows Refresh Tool from the following link:
https://www.microsoft.com/en-us/software-download/windows10startfresh https://www.microsoft.com/en-us/software-download/windows10startfresh
To start with a clean install of the Anniversary Update, I did not install Windows® 10 from scratch and then update to the Anniversary update, I ran this tool on a NUC that already has the update installed, and the results were the same, I was able to install XTU without any problems, there was no error message: "A digitally signed driver is required for Intel Overclocking Device Driver"
Scenario 3:
I used the ISO file to install Windows® 10 that contains the anniversary update 1607, I used it with Daemon tool® to do a clean installation, I got the tool from the following link the following link:
http://daemon-tools-lite.en.softonic.com/ http://daemon-tools-lite.en.softonic.com/
And the result was the same, I was able to install the XTU with no problems and no error message.
NOTE: These links are being offered for your convenience and should not be viewed as an endorsement by Intel of the content, products, or services offered there.
So, based on the information above, I just wanted to verify at which point is when you get the error message.
Is it when you try to install the XTU?
Or you can install it, but when you try to use it, then is when you get the error message?
Any questions, please let me know.
Alberto
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello:
Thank you very much for that information, we really appreciate any details on this matter.
The case is now under investigation, as soon s I get a possible resolution I wil post all the details on this thread.
Any questions, please let me know.
Alberto
![](/skins/images/7FC17B7B85029576C25F1E43CE255B51/responsive_peak/images/icon_anonymous_message.png)
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page