Intel Management Engine Interface (this Device Cannot Start. (code 10))

So looking at device manager I see a yellow exclamation point next to this system device. What can I do to fix this and does this cause problems with windows updates that I have been having lately? The driver version installed is 11.0.5.1189 dated 3/28/2016. I have used Intel Driver and Support Assistant but it didn't help. In fact it made me download a graphic driver that is actually older than the one already installed.
My Specs:
Motherboard
ASRock Z77 Extreme4 (CPUSocket)
CPU
Intel Core i5 3570K @ 3.40GHz
Ivy Bridge 22nm Technology
RAM
16.0GB Dual-Channel DDR3 @ 799MHz (11-11-11-28)
Graphics
DELL M770 (1280x1024@60Hz)
Intel HD Graphics 4000 (ASRock)
1024MB ATI AMD Radeon R7 200 Series (Sapphire/PCPartner)
CrossFire Disabled

 

Here are 3 fixes you can try.
https://www.drivereasy.com/knowledg...e-this-device-cannot-start-on-windows-solved/

 

Please tell us your operating system.
I recommend you do some diagnostic tests and let us know the results.
First, run Intel Management Engine Verification Utility https://downloadcenter.intel.com/download/19009/Intel-Management-Engine-Verification-Utility It requires your system has Net Framework 3.5 or higher which is here: https://www.microsoft.com/en-us/download/details.aspx?id=21
Second, run SFC Utility http://www.majorgeeks.com/files/details/sfc_utility.html
Third, Fix with DISM or System Update Readiness Tool (SURT) https://support.microsoft.com/en-us...-by-using-the-dism-or-system-update-readiness
Fourth, run SFCFix http://www.majorgeeks.com/files/details/sfcfix.html and post a copy of the text file it produces to this thread. Keep all logs produced from these diagnostics.

 

For some reason it is working now when I took a look at device manager and after I restarted the PC. I did fiddle around with some things before the restart. I did uninstall and reinstalled the driver as well as disabled it. I don't know what worked but I am going to follow your instructions anyway because this problem has occurred before. Currently I am running the verification utility but it been running for about 6 hours as I am working on the PC. I am thinking of closing it and instead running it on safe mode. What do you think?

 

You really need to identify the operating system.

It shouldn't matter which mode the verification utility. Info on it indicates it should do okay even in the background. Here are some FAQs https://www.intel.com/content/www/us/en/support/articles/000005974/software/chipset-software.html
Safe mode might do things faster. I've no idea how long it should take.

Another diagnostic to do is chkdsk /f to fix logical errors on the drive the next time you reboot. See the following for how to do it https://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/

 

Windows 7 Ultimate 6.1.7601.24023 Service Pack 1 64-bit.

 

Currently I am using 2 driver managers: Driver Booster 5.2 free version and SnailDriver 2 Lite. This morning IME was working fine according to device manager but Driver Booster 5.2 popped up suggesting I update drivers for Intel 7 series/C216 Chipset Family PCI Express Root Port (about 6 ports, Driver version 10.1.1.40 dated 01/03/2017). Incidentally SnailDriver is suggesting to update to Driver version 10.1.2.77 dated 08/03/2016. After the reboot device manager informs that the IME cannot start. I also tried to install .NET Framework 4.5 but the installation stopped because it detected "same or higher version of .NET Framework 4.5 has already been installed on this computer." I am currently running verification utility.

 

So I did some digging. I was experiencing some BSOD (errors 019, d1) which seem to be driver related and found that one way of isolating the problem is through a clean boot. Therefore I used msconfig and noticed that Intel ME was disabled. By enabling it at reboot and it seems to have solved the problem. The verification utility still seems to take a long time to function and it doesn't work at safe mode (at safe mode it requests to look into the UEFI motherboard). I don't what I could change at the motherboard.

 

Don't run the verification anymore for the time being. Whichever driver manger you updated with yesterday, run its rollback/restore feature for those drivers that you updated. Tell me if IME works again and if you still have BSOD issues. There are a couple of rules, many of us follow, when if comes to drivers. "Don't fix it if it isn't broke" and get it from the OEM first, if you need one. Driver managers are good at listing the latest drivers, but terribly poor at identifying those meant for your system. Friday and yesterday, IME was working. Then you ran a driver managers update and now IME is broke and you're getting BSODs. What does that tell you?

If you are still getting BSODs after doing the driver rollback, my advice is to open a third thread at Sysnative in the BSOD subforum. Yesterday, I went over your threads in the Updates and Hardware forums there. My advice to you is to not run any programs on your own unless a specialist requests you do so. Else, things can get more complicated fast. I also think you should clear issues and resolve the help threads with a priority, BSOD first, Updates second, IME (this thread) third, and Hardware (video slicing/streaming) fourth.

 

I saw in your Sysnative Updates thread you have an issue withKB4074598. This might shed some light. https://support.microsoft.com/en-us/help/4074598/windows-7-update-kb4074598
Also, https://www.bleepingcomputer.com/ne...curity-updates-unless-avs-set-a-registry-key/
Take note of the "a .reg file" link in the Bleeping article. AVAST might still be late to the party and "a .reg file" fix might solve the issue. You can check your registry for the correct key setting by running regedit.exe>edit>search>qualitycompat to see if the keys match what is in the MS link. If the keys match, run the update again. Whatever the result, advise the Sysnative specialist.

 

As far as the registry is concerned, I get 0x00000000 (0) instead of 0x00000000. I did the rollback as you suggested and I can see that Intel ME is fine. Although I see that many Intel services are not running event though I set them up to enable. If I do the reg fix then I should back up the reg.

 

I think you're okay with 0x00000000 (0). That's what I show on mine. I run MSE for AV and MS took care of things for me already without me having to make the reg change.
Grats on the rollback. Something to check in services is that the two Intel(R) Management and Security services are started and on Automatic (Delayed Start).

 

I only see Intel(R) Management and Security Application Local Management Service. I don't see the other one.

 

I still would like to see SFCFix results as I requested in post #3. But you should download and run the W7x64 SURT package from the link I gave there and run the SFC Utility from the given link. Once SURT and SFC are done, run SFCFix to give an exception basis report (txt), short and concise. This report will give me an idea on how good the system is and what to pursue next.

 

OK. I ran the W7x64 SURT package (Windows6.1-KB947821-v34-x64.msu) which I have in the past on several occasions. Then I ran SFC Utility and then SFCFix. How do I post sfclogs.txt?
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-02-26 20:13:11.378
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 0
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 15
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.



Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2018-02-26 20:26:30.614
----------------------EOF-----------------------

 

Click Upload a File at the bottom right of your new post.

 

Okay on only one service. I suspect it might be related to the diff betweeen Ultimate and Home.

The good news is you aren't missing nor have any corrupt system files. However, the 15 SURT corruptions likely are related to KB4074598 failing to install. You need to post the SFCFix.txt to your Sysnative thread along with SURT log, which I suspect you might need to zip/rar. Keep the SFC Utility txt handy in case S'maniac asks for it, too. Its the same as a CBS log.

 

How do I get the SURT log?

 

Look in C:\Windows\Logs\CBS\CheckSUR.log

 

Here is a tutorial on checksur.log https://www.sevenforums.com/tutoria...eadiness-tool-checksur-log-file-analyzis.html

 

I posted the logs over at Sysnative and waiting for a response. Being curious I decided to use WindowsUpdate.diagcab and see what happens. After running it I saw that it did several things including registry "fixes" and gave a windows update error of 0x800f081f. After rebooting the computer I see that Intel ME is down again so I figured it must have been from the registry changes. I go to Intel to scan for drivers and as I posted before when I attempted to install the drivers the installation mentions that the drivers in the computer are newer than the ones to be installed. I install the drivers anyway. So I figure out that the drivers that were mentioned during the installation were the Intel audio driver and not the display driver that were newer. After another restart from this Intel installation, I see on device manager that everything is fine. I go to Intel for another scan and it states that everything is up to date. Now the Intel Audio Driver that were mentioned I got from SnailDriver. SnailDriver has "???(R) ????" Version 6.16.00.3200 dated 06/22/2017 321.95kb. The Intel Audio Driver I installed is Intel(R) Corporation 6.16.0.3154 dated 09/09/2014.

 

Well I went to sysnative and it seems that the intel situation has been resolved. I have uninstalled Driver Booster and SnailDriver. The Windows Update has also been resolved and Intel verification never did work.

 

Thank you for closing the loop here on this thread. After I did some some further checking, it seems the IME verification isn't currrently meant to work on your computer. Windows updates have become a huge problem for W7 users. MS has become adept at breaking things, month by month, with poor update deployment. Here is a forum dedicated to achieving the least pain from updates.
https://www.askwoody.com/ Click on the MS-DEFCON System to get an idea of what's happening.
Check out this CW article https://www.infoworld.com/article/3...repare-for-the-windows-781-patchocalypse.html If you are interested in Group B, which I am in, then PKCano spells it out in the "Bluelist" https://www.askwoody.com/forums/top...-of-group-b-monthly-updates-for-win7-and-8-1/ It gives a strategy for both W7 & W8 B'ers. Basically, I only install "security only", but only after Woody goes to DEFCON 3 or higher.