MacBook Air Black Screen after macOS Catalina Update

How were you able to determine the unidentified authors? Were you in the extensions folder?

Apple's tech support is actually scheduled to call me later today to learn more about the issue I had with my specific build of Catalina OS. I'll keep you posted on any developments.

Even though Catalina disables 32-bit apps, I found (on my second try) that it was better to remove them and any non-apple extensions before upgrading to Catalina. 

What I am curious about (I too have a black screen after Catalina) is how to access the areas for kernals etc when the screen is black and nothing works

This just happened to my MacBook Air and it is a 2019 model!

I have the same problem.

After updating Catalina, my MacBook Pro was left on a black screen. Apple support could not solve the problem.

I've been with a paperweight for 1 month.

Why isn't this problem getting any coverage in the media? It's like it doesn't exist and Apple doesn't care.

I am facing the same thing. I have a Macbook air early 2014 model, 8GB Ram and 256 HD. Every time i have upgraded the OS this happened, not just Catalina.

Without having my MacBook in front of me, I can't remember. But this link might help:

http://osxdaily.com/2012/01/12/how-to-manually-install-kernel-extensions-in-mac-os-x/

I think it's in the Library/Extensions folder. And you should be able to sort by author. Apple will be the vast majority of them. But there may be some 3rd party extensions for you to check on.

Good news, so far. After successfully reverting to Mojave, I ”cleaned up” my MBA by uninstalling all 32-bit apps, disabled unnecessary extensions, removed leftover remmenants of apps, etc., etc., using CleanMyMac. Then, after completing a “just in case” TimeMachine backup, I installed Catalina again, and so far I have been able to put the MBA to sleep and wake it up normally after several minutes, and I have left it to go to sleep, left it for half an hour, and woke it up normally.

Clearly, my mid-2012 MBA was not obsolete, nor did it have any hardware issues or midi factions that could be blamed for the weird behavior.

But why doesn’t Apple monitor these forums and provide help when a flagship product decides it won’t work on a previously working machine?

If I have problems after a much longer “sleep,” I will post here.

After updating my 2015 MacBook a few days ago (which took about 12 hours), everything seemed to be working fine. Then yesterday, after using it and it working normally, I connected it to the charger. When I went to use it again a couple hours later, the screen was dark. The keyboard was still lighting up though so I knew it was on. When I tried holding it under light, I could faintly see the desktop. I called Apple support and they had me do the run of the mill resets but nothing changed and I was told I would have to bring it in for repair. So today I scheduled my Genius Bar appointment and was simply told I would need to shell out $475 plus tax to replace the display. I have not had any problems with this laptop for the four years I have owned it, and the fact that it went from functioning normally to unusable from sitting on my dining room table for two hours seems more like a software malfunction than a $500+ hardware issue.

This was a garbage response form Apple. I had the same experience. I reverted to Mojave (not easy) and after doing some clean up to simplify my system, reinstalled Catalina and it has been generally okay since. I have a macbook Air 2012 edition.

The apple technician doesn't know what he is taking about.

I had this same issue. Upgraded to Catalina and after my 2019 Macbook Pro went to sleep, it would wake up with a black screen. I could play with the finger print login, play/hear Spotify, etc but see nothing but a black screen. I went through 3 apple support calls with the typical solutions to NVRAM reset, SCM reset, repair Disk Utility....none of this worked.

I read the comments below and took a risk with deleting 3rd party kernel extensions in the Library/Extension folder. Deleted all extensions prior to 2019 (i just bought this mac in July), and rebooted the Mac. The issue was instantly resolved.

Very irritating that I went through 3 separate calls with support, they also had me download maleware software to scan my mac (i've never used this type of software in my 15 years of using mac products). The solution was posted in these comments below, and you would think that support would know of this solution...