Windows 10 gets shutdown instead of going to sleep/hibernateLaptop shutdown right after lid is closedHow do I...

Two field separators (colon and space) in awk

Can someone publish a story that happened to you?

How does Captain America channel this power?

Equally distributed table columns

Who was the lone kid in the line of people at the lake at the end of Avengers: Endgame?

Cyclomatic Complexity reduction JS

Retract an already submitted recommendation letter (written for an undergrad student)

Can't get 5V 3A DC constant

What causes platform events to fail to be published and should I cater for failed platform event creations?

Pre-plastic human skin alternative

Why was the Spitfire's elliptical wing almost uncopied by other aircraft of World War 2?

Covering null sets by a finite number of intervals

Thesis on avalanche prediction using One Class SVM

How could Tony Stark make this in Endgame?

What to do with someone that cheated their way through university and a PhD program?

"The cow" OR "a cow" OR "cows" in this context

basic difference between canonical isomorphism and isomorphims

Initiative: Do I lose my attack/action if my target moves or dies before my turn in combat?

How to limit Drive Letters Windows assigns to new removable USB drives

Read line from file and process something

How does Nebula have access to these memories?

How to denote matrix elements succinctly

a sore throat vs a strep throat vs strep throat

How to not starve gigantic beasts



Windows 10 gets shutdown instead of going to sleep/hibernate


Laptop shutdown right after lid is closedHow do I prevent an Asus Q301LA laptop from shutting down when I am actually selecting sleep?Getting a MBP to hibernate/standby after some specific time spent in sleep even when plugged inComputer doesn't shut down, hibernate or sleepIssue with Windows 10 Lock Screen ShutdownUnwanted shutdown during sleep after `powercfg.exe /hibernate off` on my laptopWhy Windows 10 won't wake up from prolonged sleep (or hibernate or shutdown) conditions?Windows 10 hibernates instead of shutting down, even though fast startup is disabledWindows 10 auto hibernation with the lid closedWindows 10 Laptop Hibernate and Shutdown Freeze Midway to Complete Power Down






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







11















It's a long time problem - Windows 10 is shutting down instead of going to sleep or hibernate.



All the power settings are set to sleep/hibernate/nothing for power button/closing lid/idle etc. And still - sometimes it's just getting shutdown!



Any idea?




Windows 10, Version 1607 build 14393.726
Laptop - Asus N550JV





Updates:





  • April 2018: Version 1709 build 16299.371


    • Still happening, I even went through a complete drive wipe and clean install.




  • May 2018: Version 1803 build 17134.1 - still happening.










share|improve this question

























  • Are you saying your machine shutdowns instead of going to sleep/hibernate after a period of time. If that's the case you should say that specifically.

    – Ramhound
    Mar 16 '17 at 13:46






  • 1





    just to be sure, you understand that a hibernated system is effectively the same as a powered off system until you power it back on, at which point it goes through a long load phase (which it calls Resuming) before presenting a login screen. Correct? Some folks still thinkg Sleep and Hibernate are essentially the same thing, so just want to be clear.

    – Frank Thomas
    Mar 16 '17 at 13:55











  • @Ramhound not only after being idle for a period of time. I can choose manually sleep or hibernate and it will shutdown sometimes.

    – arieljannai
    Mar 16 '17 at 15:51











  • @FrankThomas Sure, I use hibernate when I'm going to be idle more time, so the battery is saved as it was off, but I still get all of my things as they were. And of course sleep when I plan using it again soon.

    – arieljannai
    Mar 16 '17 at 15:51











  • just noticed I haven't mentioned it's a laptop. I've updated the question

    – arieljannai
    Mar 16 '17 at 15:52


















11















It's a long time problem - Windows 10 is shutting down instead of going to sleep or hibernate.



All the power settings are set to sleep/hibernate/nothing for power button/closing lid/idle etc. And still - sometimes it's just getting shutdown!



Any idea?




Windows 10, Version 1607 build 14393.726
Laptop - Asus N550JV





Updates:





  • April 2018: Version 1709 build 16299.371


    • Still happening, I even went through a complete drive wipe and clean install.




  • May 2018: Version 1803 build 17134.1 - still happening.










share|improve this question

























  • Are you saying your machine shutdowns instead of going to sleep/hibernate after a period of time. If that's the case you should say that specifically.

    – Ramhound
    Mar 16 '17 at 13:46






  • 1





    just to be sure, you understand that a hibernated system is effectively the same as a powered off system until you power it back on, at which point it goes through a long load phase (which it calls Resuming) before presenting a login screen. Correct? Some folks still thinkg Sleep and Hibernate are essentially the same thing, so just want to be clear.

    – Frank Thomas
    Mar 16 '17 at 13:55











  • @Ramhound not only after being idle for a period of time. I can choose manually sleep or hibernate and it will shutdown sometimes.

    – arieljannai
    Mar 16 '17 at 15:51











  • @FrankThomas Sure, I use hibernate when I'm going to be idle more time, so the battery is saved as it was off, but I still get all of my things as they were. And of course sleep when I plan using it again soon.

    – arieljannai
    Mar 16 '17 at 15:51











  • just noticed I haven't mentioned it's a laptop. I've updated the question

    – arieljannai
    Mar 16 '17 at 15:52














11












11








11


5






It's a long time problem - Windows 10 is shutting down instead of going to sleep or hibernate.



All the power settings are set to sleep/hibernate/nothing for power button/closing lid/idle etc. And still - sometimes it's just getting shutdown!



Any idea?




Windows 10, Version 1607 build 14393.726
Laptop - Asus N550JV





Updates:





  • April 2018: Version 1709 build 16299.371


    • Still happening, I even went through a complete drive wipe and clean install.




  • May 2018: Version 1803 build 17134.1 - still happening.










share|improve this question
















It's a long time problem - Windows 10 is shutting down instead of going to sleep or hibernate.



All the power settings are set to sleep/hibernate/nothing for power button/closing lid/idle etc. And still - sometimes it's just getting shutdown!



Any idea?




Windows 10, Version 1607 build 14393.726
Laptop - Asus N550JV





Updates:





  • April 2018: Version 1709 build 16299.371


    • Still happening, I even went through a complete drive wipe and clean install.




  • May 2018: Version 1803 build 17134.1 - still happening.







windows-10 sleep shutdown power-management






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 6 '18 at 12:20







arieljannai

















asked Mar 16 '17 at 13:42









arieljannaiarieljannai

1,37221026




1,37221026













  • Are you saying your machine shutdowns instead of going to sleep/hibernate after a period of time. If that's the case you should say that specifically.

    – Ramhound
    Mar 16 '17 at 13:46






  • 1





    just to be sure, you understand that a hibernated system is effectively the same as a powered off system until you power it back on, at which point it goes through a long load phase (which it calls Resuming) before presenting a login screen. Correct? Some folks still thinkg Sleep and Hibernate are essentially the same thing, so just want to be clear.

    – Frank Thomas
    Mar 16 '17 at 13:55











  • @Ramhound not only after being idle for a period of time. I can choose manually sleep or hibernate and it will shutdown sometimes.

    – arieljannai
    Mar 16 '17 at 15:51











  • @FrankThomas Sure, I use hibernate when I'm going to be idle more time, so the battery is saved as it was off, but I still get all of my things as they were. And of course sleep when I plan using it again soon.

    – arieljannai
    Mar 16 '17 at 15:51











  • just noticed I haven't mentioned it's a laptop. I've updated the question

    – arieljannai
    Mar 16 '17 at 15:52



















  • Are you saying your machine shutdowns instead of going to sleep/hibernate after a period of time. If that's the case you should say that specifically.

    – Ramhound
    Mar 16 '17 at 13:46






  • 1





    just to be sure, you understand that a hibernated system is effectively the same as a powered off system until you power it back on, at which point it goes through a long load phase (which it calls Resuming) before presenting a login screen. Correct? Some folks still thinkg Sleep and Hibernate are essentially the same thing, so just want to be clear.

    – Frank Thomas
    Mar 16 '17 at 13:55











  • @Ramhound not only after being idle for a period of time. I can choose manually sleep or hibernate and it will shutdown sometimes.

    – arieljannai
    Mar 16 '17 at 15:51











  • @FrankThomas Sure, I use hibernate when I'm going to be idle more time, so the battery is saved as it was off, but I still get all of my things as they were. And of course sleep when I plan using it again soon.

    – arieljannai
    Mar 16 '17 at 15:51











  • just noticed I haven't mentioned it's a laptop. I've updated the question

    – arieljannai
    Mar 16 '17 at 15:52

















Are you saying your machine shutdowns instead of going to sleep/hibernate after a period of time. If that's the case you should say that specifically.

– Ramhound
Mar 16 '17 at 13:46





Are you saying your machine shutdowns instead of going to sleep/hibernate after a period of time. If that's the case you should say that specifically.

– Ramhound
Mar 16 '17 at 13:46




1




1





just to be sure, you understand that a hibernated system is effectively the same as a powered off system until you power it back on, at which point it goes through a long load phase (which it calls Resuming) before presenting a login screen. Correct? Some folks still thinkg Sleep and Hibernate are essentially the same thing, so just want to be clear.

– Frank Thomas
Mar 16 '17 at 13:55





just to be sure, you understand that a hibernated system is effectively the same as a powered off system until you power it back on, at which point it goes through a long load phase (which it calls Resuming) before presenting a login screen. Correct? Some folks still thinkg Sleep and Hibernate are essentially the same thing, so just want to be clear.

– Frank Thomas
Mar 16 '17 at 13:55













@Ramhound not only after being idle for a period of time. I can choose manually sleep or hibernate and it will shutdown sometimes.

– arieljannai
Mar 16 '17 at 15:51





@Ramhound not only after being idle for a period of time. I can choose manually sleep or hibernate and it will shutdown sometimes.

– arieljannai
Mar 16 '17 at 15:51













@FrankThomas Sure, I use hibernate when I'm going to be idle more time, so the battery is saved as it was off, but I still get all of my things as they were. And of course sleep when I plan using it again soon.

– arieljannai
Mar 16 '17 at 15:51





@FrankThomas Sure, I use hibernate when I'm going to be idle more time, so the battery is saved as it was off, but I still get all of my things as they were. And of course sleep when I plan using it again soon.

– arieljannai
Mar 16 '17 at 15:51













just noticed I haven't mentioned it's a laptop. I've updated the question

– arieljannai
Mar 16 '17 at 15:52





just noticed I haven't mentioned it's a laptop. I've updated the question

– arieljannai
Mar 16 '17 at 15:52










4 Answers
4






active

oldest

votes


















4














Many people have had this error and oftentimes the cause is different, but I want to post a solution I found that completely solved it for me. This problem is caused by an erroneous driver in Windows (that is why Linux and Safe Mode work fine). In most cases, it seems that the device responsible is 'Intel(R) Management Engine Interface' (under 'System devices' in device manager). To solve the problem, you need to right-click and disable the device or roll back the driver to anything older than 11.xxx, don't uninstall the device because you will need to reinstall it manually if this does not fix the problem. For me, disabling it worked and the computer now behaves normally.



I know this will not fix the problem for 100% of cases, but this is the most commonly successful solution that I have found online. I have also found people saying sound card and graphics drivers are to blame, but I have not tested those so I am not sure.






share|improve this answer
























  • Thanks for the answer! What version of the driver do you have?

    – arieljannai
    Apr 24 '17 at 9:38











  • I had a sub version of 9.xxx. Tried also updating to 11.xxx to check if maybe it's the opposite from your situation - but no luck. Still no working

    – arieljannai
    Apr 24 '17 at 9:49











  • @arieljannai Darn. I have 11.xxx and I just disabled the device entirely. I guess your problem is with a different driver. Just to be sure, boot into safe mode and see if the problem stops.

    – Syd Lambert
    Apr 24 '17 at 13:46











  • Thanks! I upgraded to 11.7 from 11.0 and (if you see this message after I close and open the lid) it solved the issue. It worked!

    – Ariel Popovsky
    Jul 30 '18 at 22:23



















2














So I had the same issue since the last Windows update (also an Asus laptop).
Finally managed to resolve it. I think what happened was that it somehow lost the original settings, became null or something.
To resolve just go to the power setting option and under the "When I close the lid" change it to "do nothing" and save. Then open it again and change it back to "Sleep" and save.
Should work now.






share|improve this answer
























  • Sounds pretty weird, but since nothing worked until now I'll give it a shot

    – arieljannai
    Mar 22 '17 at 12:05






  • 1





    Unfortunately it didn't solve it

    – arieljannai
    Apr 24 '17 at 9:49



















0














This seems to be in general related to power management of the device Intel(R) Management Engine Interface in Device Manager under System devices.



Intel(R) Management Engine Interface in Device Manager, System devices



In device properties, You can uncheck/ untick the Allow the computer to turn off this device to save power option. This is described graphically here (also the source of the screenshots!).



Untick the Allow the computer to turn off this device to save power option






share|improve this answer































    0














    Just solved the issue on my laptop. In my case, I had to update to the latest Intel MEI driver (or replaced it with the right version? See note below).



    Steps I took:




    • Went to Intel Download Center and searched for Intel MEI

    • Looked for "Intel® Management Engine Driver for Windows 8.1* and Windows® 10", downloaded, and extracted.

    • In Device manager, under System Devices, I right clicked Intel(R) Management Engine Interface, then Update Driver -> Browse my Computer -> Browse.

    • Navigated and selected the consumer MEI driver under ConsWindowsDriverPackagesMEIwin10

    • Clicked next. I was informed that the driver had been successfully installed. The driver version reflected that, changing from 11.some.thing into 1904.12.0.1208

    • Rebooted


    On next reboot, I tested stuff out, and everything worked fine. The shutdown instead of sleep issue was fixed.



    I'm guessing that Windows Update installed the wrong drivers for my laptop given that the version numbers are wildly different. In contrast to another top voted answer, I had to update as there was nothing to roll back to.






    share|improve this answer






















      protected by Community Aug 24 '17 at 16:48



      Thank you for your interest in this question.
      Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



      Would you like to answer one of these unanswered questions instead?














      4 Answers
      4






      active

      oldest

      votes








      4 Answers
      4






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      4














      Many people have had this error and oftentimes the cause is different, but I want to post a solution I found that completely solved it for me. This problem is caused by an erroneous driver in Windows (that is why Linux and Safe Mode work fine). In most cases, it seems that the device responsible is 'Intel(R) Management Engine Interface' (under 'System devices' in device manager). To solve the problem, you need to right-click and disable the device or roll back the driver to anything older than 11.xxx, don't uninstall the device because you will need to reinstall it manually if this does not fix the problem. For me, disabling it worked and the computer now behaves normally.



      I know this will not fix the problem for 100% of cases, but this is the most commonly successful solution that I have found online. I have also found people saying sound card and graphics drivers are to blame, but I have not tested those so I am not sure.






      share|improve this answer
























      • Thanks for the answer! What version of the driver do you have?

        – arieljannai
        Apr 24 '17 at 9:38











      • I had a sub version of 9.xxx. Tried also updating to 11.xxx to check if maybe it's the opposite from your situation - but no luck. Still no working

        – arieljannai
        Apr 24 '17 at 9:49











      • @arieljannai Darn. I have 11.xxx and I just disabled the device entirely. I guess your problem is with a different driver. Just to be sure, boot into safe mode and see if the problem stops.

        – Syd Lambert
        Apr 24 '17 at 13:46











      • Thanks! I upgraded to 11.7 from 11.0 and (if you see this message after I close and open the lid) it solved the issue. It worked!

        – Ariel Popovsky
        Jul 30 '18 at 22:23
















      4














      Many people have had this error and oftentimes the cause is different, but I want to post a solution I found that completely solved it for me. This problem is caused by an erroneous driver in Windows (that is why Linux and Safe Mode work fine). In most cases, it seems that the device responsible is 'Intel(R) Management Engine Interface' (under 'System devices' in device manager). To solve the problem, you need to right-click and disable the device or roll back the driver to anything older than 11.xxx, don't uninstall the device because you will need to reinstall it manually if this does not fix the problem. For me, disabling it worked and the computer now behaves normally.



      I know this will not fix the problem for 100% of cases, but this is the most commonly successful solution that I have found online. I have also found people saying sound card and graphics drivers are to blame, but I have not tested those so I am not sure.






      share|improve this answer
























      • Thanks for the answer! What version of the driver do you have?

        – arieljannai
        Apr 24 '17 at 9:38











      • I had a sub version of 9.xxx. Tried also updating to 11.xxx to check if maybe it's the opposite from your situation - but no luck. Still no working

        – arieljannai
        Apr 24 '17 at 9:49











      • @arieljannai Darn. I have 11.xxx and I just disabled the device entirely. I guess your problem is with a different driver. Just to be sure, boot into safe mode and see if the problem stops.

        – Syd Lambert
        Apr 24 '17 at 13:46











      • Thanks! I upgraded to 11.7 from 11.0 and (if you see this message after I close and open the lid) it solved the issue. It worked!

        – Ariel Popovsky
        Jul 30 '18 at 22:23














      4












      4








      4







      Many people have had this error and oftentimes the cause is different, but I want to post a solution I found that completely solved it for me. This problem is caused by an erroneous driver in Windows (that is why Linux and Safe Mode work fine). In most cases, it seems that the device responsible is 'Intel(R) Management Engine Interface' (under 'System devices' in device manager). To solve the problem, you need to right-click and disable the device or roll back the driver to anything older than 11.xxx, don't uninstall the device because you will need to reinstall it manually if this does not fix the problem. For me, disabling it worked and the computer now behaves normally.



      I know this will not fix the problem for 100% of cases, but this is the most commonly successful solution that I have found online. I have also found people saying sound card and graphics drivers are to blame, but I have not tested those so I am not sure.






      share|improve this answer













      Many people have had this error and oftentimes the cause is different, but I want to post a solution I found that completely solved it for me. This problem is caused by an erroneous driver in Windows (that is why Linux and Safe Mode work fine). In most cases, it seems that the device responsible is 'Intel(R) Management Engine Interface' (under 'System devices' in device manager). To solve the problem, you need to right-click and disable the device or roll back the driver to anything older than 11.xxx, don't uninstall the device because you will need to reinstall it manually if this does not fix the problem. For me, disabling it worked and the computer now behaves normally.



      I know this will not fix the problem for 100% of cases, but this is the most commonly successful solution that I have found online. I have also found people saying sound card and graphics drivers are to blame, but I have not tested those so I am not sure.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Apr 23 '17 at 23:49









      Syd LambertSyd Lambert

      1737




      1737













      • Thanks for the answer! What version of the driver do you have?

        – arieljannai
        Apr 24 '17 at 9:38











      • I had a sub version of 9.xxx. Tried also updating to 11.xxx to check if maybe it's the opposite from your situation - but no luck. Still no working

        – arieljannai
        Apr 24 '17 at 9:49











      • @arieljannai Darn. I have 11.xxx and I just disabled the device entirely. I guess your problem is with a different driver. Just to be sure, boot into safe mode and see if the problem stops.

        – Syd Lambert
        Apr 24 '17 at 13:46











      • Thanks! I upgraded to 11.7 from 11.0 and (if you see this message after I close and open the lid) it solved the issue. It worked!

        – Ariel Popovsky
        Jul 30 '18 at 22:23



















      • Thanks for the answer! What version of the driver do you have?

        – arieljannai
        Apr 24 '17 at 9:38











      • I had a sub version of 9.xxx. Tried also updating to 11.xxx to check if maybe it's the opposite from your situation - but no luck. Still no working

        – arieljannai
        Apr 24 '17 at 9:49











      • @arieljannai Darn. I have 11.xxx and I just disabled the device entirely. I guess your problem is with a different driver. Just to be sure, boot into safe mode and see if the problem stops.

        – Syd Lambert
        Apr 24 '17 at 13:46











      • Thanks! I upgraded to 11.7 from 11.0 and (if you see this message after I close and open the lid) it solved the issue. It worked!

        – Ariel Popovsky
        Jul 30 '18 at 22:23

















      Thanks for the answer! What version of the driver do you have?

      – arieljannai
      Apr 24 '17 at 9:38





      Thanks for the answer! What version of the driver do you have?

      – arieljannai
      Apr 24 '17 at 9:38













      I had a sub version of 9.xxx. Tried also updating to 11.xxx to check if maybe it's the opposite from your situation - but no luck. Still no working

      – arieljannai
      Apr 24 '17 at 9:49





      I had a sub version of 9.xxx. Tried also updating to 11.xxx to check if maybe it's the opposite from your situation - but no luck. Still no working

      – arieljannai
      Apr 24 '17 at 9:49













      @arieljannai Darn. I have 11.xxx and I just disabled the device entirely. I guess your problem is with a different driver. Just to be sure, boot into safe mode and see if the problem stops.

      – Syd Lambert
      Apr 24 '17 at 13:46





      @arieljannai Darn. I have 11.xxx and I just disabled the device entirely. I guess your problem is with a different driver. Just to be sure, boot into safe mode and see if the problem stops.

      – Syd Lambert
      Apr 24 '17 at 13:46













      Thanks! I upgraded to 11.7 from 11.0 and (if you see this message after I close and open the lid) it solved the issue. It worked!

      – Ariel Popovsky
      Jul 30 '18 at 22:23





      Thanks! I upgraded to 11.7 from 11.0 and (if you see this message after I close and open the lid) it solved the issue. It worked!

      – Ariel Popovsky
      Jul 30 '18 at 22:23













      2














      So I had the same issue since the last Windows update (also an Asus laptop).
      Finally managed to resolve it. I think what happened was that it somehow lost the original settings, became null or something.
      To resolve just go to the power setting option and under the "When I close the lid" change it to "do nothing" and save. Then open it again and change it back to "Sleep" and save.
      Should work now.






      share|improve this answer
























      • Sounds pretty weird, but since nothing worked until now I'll give it a shot

        – arieljannai
        Mar 22 '17 at 12:05






      • 1





        Unfortunately it didn't solve it

        – arieljannai
        Apr 24 '17 at 9:49
















      2














      So I had the same issue since the last Windows update (also an Asus laptop).
      Finally managed to resolve it. I think what happened was that it somehow lost the original settings, became null or something.
      To resolve just go to the power setting option and under the "When I close the lid" change it to "do nothing" and save. Then open it again and change it back to "Sleep" and save.
      Should work now.






      share|improve this answer
























      • Sounds pretty weird, but since nothing worked until now I'll give it a shot

        – arieljannai
        Mar 22 '17 at 12:05






      • 1





        Unfortunately it didn't solve it

        – arieljannai
        Apr 24 '17 at 9:49














      2












      2








      2







      So I had the same issue since the last Windows update (also an Asus laptop).
      Finally managed to resolve it. I think what happened was that it somehow lost the original settings, became null or something.
      To resolve just go to the power setting option and under the "When I close the lid" change it to "do nothing" and save. Then open it again and change it back to "Sleep" and save.
      Should work now.






      share|improve this answer













      So I had the same issue since the last Windows update (also an Asus laptop).
      Finally managed to resolve it. I think what happened was that it somehow lost the original settings, became null or something.
      To resolve just go to the power setting option and under the "When I close the lid" change it to "do nothing" and save. Then open it again and change it back to "Sleep" and save.
      Should work now.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Mar 21 '17 at 14:41









      talwekslertalweksler

      211




      211













      • Sounds pretty weird, but since nothing worked until now I'll give it a shot

        – arieljannai
        Mar 22 '17 at 12:05






      • 1





        Unfortunately it didn't solve it

        – arieljannai
        Apr 24 '17 at 9:49



















      • Sounds pretty weird, but since nothing worked until now I'll give it a shot

        – arieljannai
        Mar 22 '17 at 12:05






      • 1





        Unfortunately it didn't solve it

        – arieljannai
        Apr 24 '17 at 9:49

















      Sounds pretty weird, but since nothing worked until now I'll give it a shot

      – arieljannai
      Mar 22 '17 at 12:05





      Sounds pretty weird, but since nothing worked until now I'll give it a shot

      – arieljannai
      Mar 22 '17 at 12:05




      1




      1





      Unfortunately it didn't solve it

      – arieljannai
      Apr 24 '17 at 9:49





      Unfortunately it didn't solve it

      – arieljannai
      Apr 24 '17 at 9:49











      0














      This seems to be in general related to power management of the device Intel(R) Management Engine Interface in Device Manager under System devices.



      Intel(R) Management Engine Interface in Device Manager, System devices



      In device properties, You can uncheck/ untick the Allow the computer to turn off this device to save power option. This is described graphically here (also the source of the screenshots!).



      Untick the Allow the computer to turn off this device to save power option






      share|improve this answer




























        0














        This seems to be in general related to power management of the device Intel(R) Management Engine Interface in Device Manager under System devices.



        Intel(R) Management Engine Interface in Device Manager, System devices



        In device properties, You can uncheck/ untick the Allow the computer to turn off this device to save power option. This is described graphically here (also the source of the screenshots!).



        Untick the Allow the computer to turn off this device to save power option






        share|improve this answer


























          0












          0








          0







          This seems to be in general related to power management of the device Intel(R) Management Engine Interface in Device Manager under System devices.



          Intel(R) Management Engine Interface in Device Manager, System devices



          In device properties, You can uncheck/ untick the Allow the computer to turn off this device to save power option. This is described graphically here (also the source of the screenshots!).



          Untick the Allow the computer to turn off this device to save power option






          share|improve this answer













          This seems to be in general related to power management of the device Intel(R) Management Engine Interface in Device Manager under System devices.



          Intel(R) Management Engine Interface in Device Manager, System devices



          In device properties, You can uncheck/ untick the Allow the computer to turn off this device to save power option. This is described graphically here (also the source of the screenshots!).



          Untick the Allow the computer to turn off this device to save power option







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Aug 15 '18 at 16:28









          AdamKaliszAdamKalisz

          40946




          40946























              0














              Just solved the issue on my laptop. In my case, I had to update to the latest Intel MEI driver (or replaced it with the right version? See note below).



              Steps I took:




              • Went to Intel Download Center and searched for Intel MEI

              • Looked for "Intel® Management Engine Driver for Windows 8.1* and Windows® 10", downloaded, and extracted.

              • In Device manager, under System Devices, I right clicked Intel(R) Management Engine Interface, then Update Driver -> Browse my Computer -> Browse.

              • Navigated and selected the consumer MEI driver under ConsWindowsDriverPackagesMEIwin10

              • Clicked next. I was informed that the driver had been successfully installed. The driver version reflected that, changing from 11.some.thing into 1904.12.0.1208

              • Rebooted


              On next reboot, I tested stuff out, and everything worked fine. The shutdown instead of sleep issue was fixed.



              I'm guessing that Windows Update installed the wrong drivers for my laptop given that the version numbers are wildly different. In contrast to another top voted answer, I had to update as there was nothing to roll back to.






              share|improve this answer




























                0














                Just solved the issue on my laptop. In my case, I had to update to the latest Intel MEI driver (or replaced it with the right version? See note below).



                Steps I took:




                • Went to Intel Download Center and searched for Intel MEI

                • Looked for "Intel® Management Engine Driver for Windows 8.1* and Windows® 10", downloaded, and extracted.

                • In Device manager, under System Devices, I right clicked Intel(R) Management Engine Interface, then Update Driver -> Browse my Computer -> Browse.

                • Navigated and selected the consumer MEI driver under ConsWindowsDriverPackagesMEIwin10

                • Clicked next. I was informed that the driver had been successfully installed. The driver version reflected that, changing from 11.some.thing into 1904.12.0.1208

                • Rebooted


                On next reboot, I tested stuff out, and everything worked fine. The shutdown instead of sleep issue was fixed.



                I'm guessing that Windows Update installed the wrong drivers for my laptop given that the version numbers are wildly different. In contrast to another top voted answer, I had to update as there was nothing to roll back to.






                share|improve this answer


























                  0












                  0








                  0







                  Just solved the issue on my laptop. In my case, I had to update to the latest Intel MEI driver (or replaced it with the right version? See note below).



                  Steps I took:




                  • Went to Intel Download Center and searched for Intel MEI

                  • Looked for "Intel® Management Engine Driver for Windows 8.1* and Windows® 10", downloaded, and extracted.

                  • In Device manager, under System Devices, I right clicked Intel(R) Management Engine Interface, then Update Driver -> Browse my Computer -> Browse.

                  • Navigated and selected the consumer MEI driver under ConsWindowsDriverPackagesMEIwin10

                  • Clicked next. I was informed that the driver had been successfully installed. The driver version reflected that, changing from 11.some.thing into 1904.12.0.1208

                  • Rebooted


                  On next reboot, I tested stuff out, and everything worked fine. The shutdown instead of sleep issue was fixed.



                  I'm guessing that Windows Update installed the wrong drivers for my laptop given that the version numbers are wildly different. In contrast to another top voted answer, I had to update as there was nothing to roll back to.






                  share|improve this answer













                  Just solved the issue on my laptop. In my case, I had to update to the latest Intel MEI driver (or replaced it with the right version? See note below).



                  Steps I took:




                  • Went to Intel Download Center and searched for Intel MEI

                  • Looked for "Intel® Management Engine Driver for Windows 8.1* and Windows® 10", downloaded, and extracted.

                  • In Device manager, under System Devices, I right clicked Intel(R) Management Engine Interface, then Update Driver -> Browse my Computer -> Browse.

                  • Navigated and selected the consumer MEI driver under ConsWindowsDriverPackagesMEIwin10

                  • Clicked next. I was informed that the driver had been successfully installed. The driver version reflected that, changing from 11.some.thing into 1904.12.0.1208

                  • Rebooted


                  On next reboot, I tested stuff out, and everything worked fine. The shutdown instead of sleep issue was fixed.



                  I'm guessing that Windows Update installed the wrong drivers for my laptop given that the version numbers are wildly different. In contrast to another top voted answer, I had to update as there was nothing to roll back to.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered yesterday









                  GeneGene

                  1308




                  1308

















                      protected by Community Aug 24 '17 at 16:48



                      Thank you for your interest in this question.
                      Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                      Would you like to answer one of these unanswered questions instead?



                      Popular posts from this blog

                      VNC viewer RFB protocol error: bad desktop size 0x0I Cannot Type the Key 'd' (lowercase) in VNC Viewer...

                      Tribunal Administrativo e Fiscal de Mirandela Referências Menu de...

                      looking for continuous Screen Capture for retroactivly reproducing errors, timeback machineRolling desktop...