mac wont wake from sleep after Catalina upgrade

I HAVE THE FIX.....so far. After spending 2 hours on a chat with Apple support this is what worked.

Go to Finder > Go > Go to folder. Type in Library/Extensions and once there, find and delete any of these that may show up there, in order.

MCTTriggerGraphics.plugin

Trigger5Core.kext

MCTTrigger6USB.kext

MCTTrigger2.kext

DJTVirtualDisplayDriver.kext

Then go to /Library/LaunchDaemons and find and delete tw.com.mct.TriggerDriver.plist

Then go to /Library/LaunchAgents and find and delete tw.com.mct.TriggerDriver.plist

Then empty trash and restart the computer.

I've had the same issue since installing the first Public Beta a while back. Talked to Apple. Tried the whole Safe Boot, NVRAM, PRAM etc. to no avail. I didn't have any of the kext files on my laptop, so couldn't delete them.

Quite disappointing as I'd finally switched back to Mac after a 5 year stint with Windows laptops!

However, I then remembered a maintenance tool I used on my Mac back in the day whenever something wasn't working quite right: OnyX.

I ran the Maintenance functions once a few days ago and since then I have not had any sleep wake failures.

https://www.titanium-software.fr/en/onyx.html

More information here:

https://en.wikipedia.org/wiki/OnyX

https://www.lifewire.com/onyx-software-review-4100656

I hope this helps others and if my issue returns, I'll update folks here.

My problem was "Dropbox" and I performed the same tasks as did you with the guidance of Apple Support. Once Dropbox was removed the sleep problem was resolved.

HP Scanner hasn't caught up with Catalina so unfortunately it does not work and we are relegated to using Apple Image.

Eureka!!

I finally found the right solution to my problems. Let's summarise.

The problem:

Some Apple computers, like my MBA 11"has sleep wake failure with NVME 3rd party blades with Catalina (not tested with High Sierra). I was force to upgrade my Sierra version in order to be able to use the blade and install the OS.

Diagnostic:

The root problem is the hibernate function, which is related to sleeping. It failed some times, but the more time sleeping the highest probability to get sleep wake failure.

And that's because at some time, when sleeping, the system may go to hibernation mode, which implies that the memory is written to the disk (the blade) as an sleepimage file. And this causes the problem when trying to wake up.

First approach (workaround) to solve the problem:

The behaviour of sleeping function is set by "pmset" command via terminal. In my case these were my PowerManagementSETtings:

MBAJ:~ jorge$ pmset -g 

System-wide power settings:

Currently in use:

 standbydelaylow      10800

 standby              1

 halfdim              1

 hibernatefile        /var/vm/sleepimage

 gpuswitch            2

 powernap             0

 disksleep            0

 standbydelayhigh     86400

 sleep                10 (sleep prevented by sharingd)

 autopoweroffdelay    28800

 hibernatemode        25

 autopoweroff         1

 ttyskeepawake        1

 displaysleep         10

 highstandbythreshold 50

 acwake               0

 lidwake              1

note: hibernatemode 25 didn't worked for me, but thank you to Dimon1983 to put me on the right track to solve my problem.

To understand these parameters, use "man pmset" command. You will see how is the sleep-hibernate-wake relationship. Then, to avoid the failure I suggest to make it imposible the hibernation. This can be reached by this command:

$ pmset -a hibernatemode 0 standby 0 autopoweroff 0

But this is a workaround, a provisional solution, because hibernate is a good feature, which permits energy saving and more importantly, it prevents memory loss if the computer runs out of battery (when unplugged). So, here it comes the good solution.

How to solve the problem definitely:

The hibernation issue resides on the NVME driver, which seems to be on the Macbook ROM. In order to fix the issue, there is a way to replace that old driver with a new one.

This has been achieved by very good guru, called Cmd+Q, as you can see on this forum:

https://forums.macrumors.com/threads/upgrading-2013-2014-macbook-pro-ssd-to-m-2-nvme.2034976/page-65#post-26224320

There you can find his comment and a link to a very good, and complex too, guide. Who said life was easy? I'll try in a near future, when I have some spare time. For now, I am always aware not to leave my MB without energy for so long.

Thank you to all of you to let me find the way to fix that issue.

Go to folder /library/extensions and if there is a file in that folder "Trigger5Core.kext", move it to the trash and empty the trash.

This did the trick for me!

@fleurdelis8

I was having the same issues as everyone and tried the NVRAM with no luck. I did follow your instructions on Use safe mode to isolate issues with your Mac - Apple Support, and put my Mac Pro 15 to sleep in safe mode a few times and restarted. It is working great and the new Catalina appears to be faster, charges the battery faster and is much brighter on the screens.

I am having an issue with Displaylink working to drive my 3 24" monitors which I will look for any relevant posts.

Thank you for posting this suggestion!

Chris

Thanks Dobxdog.

Deleting "Trigger5Core.kext" solved my issue. I use a J5 Create Boomerang docking station and I think the file relates to it in some way. Having thought about it I realized that when the computer was actually plugged in to the docking station I didn't have the problem, it only occurred when I was using the computer independently of the docking station.

I tried the NVRAM reset and the SMC reset, in addition to the safe mode approach. The NVRAM and SMC solutions did not work. When in safe mode, I could successfully put my Macbook Air to sleep. After messing with login items without much success, I turned to third party menu items. After disabling some of those, the Mac now wakes from sleep as it should. I'll keep monitoring to make sure the solution sticks for me.

I did everything that was suggested on here and nothing worked. I even went back to Mojave and then upgraded again to no avail. I finally erased the hard drive and did a clean install of Catalina. It is fixed now, but it created two other hard drives on my computer during this process. So not sure what the deal is with this OS, but it's definitely not Apple's usually great OS. This is the first time I have ever had an issue with an upgrade or an OS.

I tried several suggestions in this thread, and uninstalling displaylink seems to have fixed it for now.

from kc_825 post

https://support.displaylink.com/knowledgebase/articles/1925041-macos-catalina-10-15-black-screen-or-only-one-mon

I gave up and erased my Macintosh - HD and reinstalled Catalina and it now wakes from sleep like it is supposed to. After 3 hours of phone time with Apple support, numerous hours trying everything listed here and other sites, and two data captures sent to the "Engineers" I threw in the towel. Actually, glad I did it as I have an early 2013 MBP and a lot of junk builds up. Freed up a ton of space and gained a little speed. The only thing that didn't survive the erase/reinstall were my messages, but still think it's fixable since they're on my phone...there must be a sync or setting that pulls them back to Mac.

Another application was running with startup. I also canceled that from startup and now I have flawless wake up each time. Get rid of any apps that work in the background. Also any apps that run idle.

Resetting the NVRAM worked for me. (MBA early 2015 model)

Thank you for the help. Resetting the NVRAM/PRAM fixed my issue. iMac (21.5-inch, Late 2013)

My issue got fixed after applying the lates update for Catalina. 10.15.1