Benches MacBooks

3

MacBook Pro won't sleep when I close the …

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

My MacBook Pro (13-inch, Late 2011) won't sleep when I close the lid and it won't wake up when I open it. I've tried resetting the SMC and NVRAM, but neither did anything. It's really annoying having to tell it to sleep every time by going into the menu bar, clicking "sleep", and closing the lid very carefully so that it won't wake up while closing. I didn't used to have this problem, but after I upgraded my RAM and hard-drive and updated to macOS High Sierra it became an issue. Did I cause this? Does anyone have an idea of how this happened? How do I fix this? What have I not tried yet?

3 replies

Sign in or join Beachball Help to reply.

  1. 0

    leroydouglas

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    If resetting the SMC hhttp://support.apple.com/kb/ht3964 for your particular Mac does not resolve the issue

    then To trouble shoot further you can:

    Try a SafeBoot  https://support.apple.com/en-us/HT201262 sometime clearing these caches is all it takes.

    Takes noticeable longer to get to the login screen, does a 5 minute disk repair before it fully boots up, and certain system caches, dynamic loader cache, etc. get cleared and rebuilt.

    This test will tell you if third party interference; extensions etc are not loaded in safe boot mode.

    Test issue in another user (or guest user) account  https://support.apple.com/en-us/HT204443

    This will tell you if it a universal issue or isolated to your user/admin account. 

  2. 0

    Tayjay24

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I just tried the SafeBoot, and it solve my problem. I don't know what this issue is at this point. If this doesn't end up ever getting fixed, I can just use Hot Corners to put the display to sleep and continue to carefully close the lid to keep it asleep. Thanks for trying.

  3. 0

    leroydouglas

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I just tried the SafeBoot, and it solve my problem.

    Thanks for the feedback. Glad this solved the problem.

    In many cases this is all it takes— clearing these system caches using the safe boot.

    I would not anticipate any further issues here.