Windows 10 64bit shut down bug

[Alex Sinov]

From time to time, Windows does two things that drive me insane:

• It shuts down, but the computer itself remains on
• It gets stuck in the "Shutting down" animation and I have to force-shut down it

I have searched for a solution, and I found one that suggested I disable "Fast startup", which I did, to no success.

The other one (http://geekslab.altervista.org/laptop-wont-shutdown-in-windows-10-heres-the-fix/) says

The problem is actually not related to Windows 10 itself. Your laptop won’t shut down on Windows 10 because of an Intel driver issue!
The bugged driver is the Intel Management Engine Interface (EMI), version 11.x. The driver can be found on Device Manager – System Devices.
The solution, therefore, is to manually downgrade the above driver, waiting for Intel’s fix of this weird bug.

I went to the Intel page and all it lists and it's fairly new are versions of EMI for Intel NUC or compute sticks.
The first one that's for desktop computers is from 2013.

Naturally, I'm kinda fearful to apply a driver that's not for a desktop computer. What do you guys advise me to do?

 

[Jembo]

I had this exact issue. I just disabled it completely in device manager. Solved the issue & haven't had a problem in 2 months.

 

[Bubbaleone]

It's also been my experience that IME isn't a requirement for your home network PC to operate properly. Unless one is in a business/production environment where remote access of other PCs occurs on a regular basis (the environment IME is intended to support), you can simply uninstall it. .

.

 

[Puffnstuff]

My mom's pc, a hp, has the same issue periodically with hanging on shutdown and she's on a clean install of 10.

 

[Alex Sinov]

OK, I just disabled it. Will report on the results.

 

[mikeymikec]

OP posts thread with an assertion in the title that there's a bug in Win10, then in the OP states that the bug isn't in Win10.

The only thing I'm aware of that's affected by disabling or not installing IMEI is that you won't get many sensor readings from say HWMonitor and the like.

Btw, IMO you've either got the wrong driver or this bug only affects a specific implementation of IMEI (I don't know if there are specific implementations, though I am vaguely aware that there's a firmware update system for IMEI which may also be affected by a BIOS update, perhaps also worth considering?). I've built a few H170 chipset Win10 machines, IMEI is installed and none of them exhibit the issues you mentioned.

The other thing I would try is uninstalling IMEI then Win10 will very likely to and install it itself from WU; it might install a more compatible version than what you've got (and yes, IMEI updates come through WU).

The opposite possibility might be the case, perhaps the mobo manufacturer's IMEI driver works better on your board than the one that may have been installed automatically by WU? In System Properties you could disable WU auto driver installation after reinstating the original driver to see if that helps.

 

[Alex Sinov]

Thanks for the reply, but now I'm a bit puzzled.

It's also been my experience that IME isn't a requirement for your home network PC to operate properly. Unless one is in a business/production environment where remote access of other PCs occurs on a regular basis (the environment IME is intended to support), you can simply uninstall it. .

.

The only thing I'm aware of that's affected by disabling or not installing IMEI is that you won't get many sensor readings from say HWMonitor and the like.

So this driver is for business/production environment, or for hardware monitoring?

 

[mikeymikec]

So this driver is for business/production environment, or for hardware monitoring?

https://www.kernel.org/doc/Documentation/misc-devices/mei/mei.txt

 

[Alex Sinov]

Thanks for the link, but I'm not sure I am as literate in this language as you.
Meaning I don't understand much.

 

[Mushkins]

Thanks for the reply, but now I'm a bit puzzled.
So this driver is for business/production environment, or for hardware monitoring?

It's for low-level hardware monitoring in a business environment. Basically it puts hooks out there that centralized monitoring and remote access software can grab onto to manage PCs remotely. No driver, no hooks. No hooks, no remote management.

99.9% of home users and small/medium businesses don't need it. It's specifically designed with the enterprise in mind, AKA corporate IT managing and monitoring 1000's of PCs.

 

[nerp]

Intel doesn't provide easy to find links for the latest drivers anymore. Your best bet is by letting Windows Update handle it or by trolling Intel support forums. They post new versions of Intel GFX drivers and even beta drivers in there.