MacBook Air Reboots/Restarts After Catalina Security Update 2022-001

[Andrew73875]

Hello!

I've updated my MacBook Air 2020 (Intel) with the latest security update 2022-001 and it started to reboot after going to sleep. When it boots again it shows the error screen, but sometimes it doesn't. This happens when I'm just closing the laptop or when it goest to sleep itself. I've tried to reset nvram, boot into a safe mode but nothing helps.

I've also contacted Apple Support and they couldn't help either. They recommended to wipe everything out or install Catalina again.

Does anyone have a similar issue? Thanks!

 

[Andrew73875]

There are no crash reports. The last activity before rebooting from the log:

[MY MAC NAME] com.apple.xpc.launchd[1] (com.apple.AddressBook.abd): Service only ran for 1 seconds. Pushing respawn out by 9 seconds.
[MY MAC NAME] com.apple.xpc.launchd[1] (com.apple.mdworker.shared.05000000-0300-0000-0000-000000000000[796]): Service exited due to SIGKILL | sent by mds[116]
[MY MAC NAME] com.apple.xpc.launchd[1] (com.apple.mdworker.shared.03000000-0400-0000-0000-000000000000[797]): Service exited due to SIGKILL | sent by mds[116]
[MY MAC NAME] (com.apple.mdworker.shared.0D000000-0500-0000-0000-000000000000[791]): Service exited due to SIGKILL | sent by mds[116]
[MY MAC NAME] (com.apple.mdworker.shared.07000000-0300-0000-0000-000000000000[804]): Service exited due to SIGKILL | sent by mds[116]
[MY MAC NAME] com.apple.xpc.launchd[1] (com.apple.mdworker.shared.09000000-0300-0000-0000-000000000000[803]): Service exited due to SIGKILL | sent by mds[116]
[MY MAC NAME] com.apple.xpc.launchd[1] (com.apple.mdworker.shared.10000000-0300-0000-0000-000000000000[806]): Service exited due to SIGKILL | sent by mds[116]
[MY MAC NAME] com.apple.xpc.launchd[1] (com.apple.mdworker.shared.02000000-0100-0000-0000-000000000000[808]): Service exited due to SIGKILL | sent by mds[116]
[MY MAC NAME] com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0A000000-0300-0000-0000-000000000000[807]): Service exited due to SIGKILL | sent by mds[116]
[MY MAC NAME] timed[127]: settimeofday({0x61f9493e,0x909e0}) == 0
[MY MAC NAME] com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.user.501): Service "com.apple.xpc.launchd.unmanaged.loginwindow.163" tried to register for endpoint "com.apple.tsm.uiserver" already registered by owner: com.apple.TextInputMenuAgent

 

[hs601]

I have exactly same experience since I applied patch yesterday.

 

[Andrew73875]

The only way I was able to fix it is to install Catalina again (without erasing anything), all information stays intact. You can download installer from Apple website here https://support.apple.com/en-us/HT211683 It will redirect you to AppStore.

Once installed, Catalina will offer to download the latest security update again (2022-001). Just click no and disable automatic updates in settings.

I've also installed the previous security update 2021-008 (19H1615). It's available for download from Apple here https://support.apple.com/kb/DL2087?locale=en_US

After that everything works great. The only exception is iTunes Store which doesn't load pages anymore.

I also recommend to let Apple know about this issue by submitting feedback here http://apple.com/feedback

 

[NeonIbis]

I think I have this issue too... I installed the security update (also a Safari update, I think?) on my 2020 Intel MBA. Now it seems to restart itself while sleeping. I also cannot play streaming media in Safari (though I can in Firefox); I don't know if others have experienced this? I would say that battery drain and processor heat have increased, too. Anyway, I will try downloading and reinstalling the OS soon, though that is annoying as my internet is very slow. First time I've had such a severe 'adverse reaction' to a security update!

 

[smunro]

I'm having the same issue. Installed the security update, and now my 2020 Macbook Pro shuts itself down at some point after I put it to sleep. I've only seen an error message generated once.

The suggested workaround, while viable, is a PITA, and, of course, it leaves your machine vulnerable to whatever vulnerabilities the security update addressed. Apple needs to get after this.

 

[NeonIbis]

Has anyone tried upgrading instead of reinstalling Catalina? I was wondering if going to Big Sur might get the security fixes without the weird crashing/bugs...

 

[Andrew73875]

I did not, but upgrading to Big Sur or Monterey should fix everything as it would be a new system. Same as reinstalling Catalina.

 

[NeonIbis]

Thank you - I'm yet to give it a try but will report back when I do... for the moment I'm shutting down every night. The safari issue remains.

 

[fred44nl]

hi,
I solved the problem temperarely, but changing the energy setting sleep to 0.
this means that my Macbook Air will always be active.
well, it drains the battery.

I used the following command in teminal:
sudo pmset -a sleep 0

 

[NeonIbis]

I've been shutting mine down entirely at night. But I've now had the computer suddenly shut down on me while I was using it (so, not just while sleeping). The fans ramped up, then roared suddenly, louder than I've ever heard, then the Mac went dead. It started up again and said there was an error, but I couldn't work out what.

I have noticed that something called 'syspolicyd' has started using huge amounts of CPU and getting the fans going, when I all I'm doing is (e.g.) viewing Macrumors in one safari tab. I don't know if this is related or some other weird issue. I'm scared to run updates on my iMac (my main computer) now, in case it also develops these weird bugs. Very frustrating.

 

[Kahakapao]

Same issue with frequent shut downs while sleeping/closed on a 2020 MBA after installing Security Update 2022-001 Catalina. sudo pmset -a hibernatemode 0 and sudo pmset -a autopoweroff 0 did not help. Most unexpected shut downs reported as "5", "Correct Shut Down.":

% log show --style syslog --predicate 'eventMessage contains "shutdown cause"'
Filtering the log data using "composedMessage CONTAINS "shutdown cause""
Skipping info and debug messages, pass --info and/or --debug to include.
wTimestamp                       (process)[PID]  
2022-01-29 16:36:12.806213-1000  localhost kernel[0]: (AppleSMC) Previous shutdown cause: 1
2022-01-30 09:24:04.824209-1000  localhost kernel[0]: (AppleSMC) Previous shutdown cause: 5
2022-01-31 11:02:29.439946-1000  localhost kernel[0]: (AppleSMC) Previous shutdown cause: 5
2022-01-31 17:30:22.310645-1000  localhost kernel[0]: (AppleSMC) Previous shutdown cause: 5
2022-01-31 18:34:50.622112-1000  localhost kernel[0]: (AppleSMC) Previous shutdown cause: -11
2022-01-31 23:37:47.142878-1000  localhost kernel[0]: (AppleSMC) Previous shutdown cause: 5
2022-01-31 23:46:43.824318-1000  localhost kernel[0]: (AppleSMC) Previous shutdown cause: 3
2022-02-01 16:14:19.359026-1000  localhost kernel[0]: (AppleSMC) Previous shutdown cause: 5
2022-02-01 18:56:12.634366-1000  localhost kernel[0]: (AppleSMC) Previous shutdown cause: 5

 

[Andrew73875]

That explains why most of the time there's no error message after rebooting. And probably the reason why Apple is not fixing it, because there are no automatic crash reports. They are simply not getting any information about these reboots.

 

[smunro]

I get the same results from log show - all shutdowns are correct.

I wonder if the security update can be reinstalled, and if that would make a difference?

 

[fred44nl]

I get the same results from log show - all shutdowns are correct.

I wonder if the security update can be reinstalled, and if that would make a difference?

I did re-install the update.
the problem is remaining.
so, you can spare yrself the trouble

 

[smunro]

Okay, thanks for letting me know. Guess we just wait for Apple to fix it, or update to Big Sur or Monterey.

 

[Andrew73875]

Would be great if Macrumors could publish the news about this issue on the main page. I wonder how many people out there who don't read this forum. They must be thinking that it's just them having this issue or there's something wrong with their Mac.

 

[samuelandjw]

I had exactly the same issue. Reinstalling Catalina and security update 2021-008 according to OP's suggestion solved the problem. This issue had been a nightmare for me. I'm not sure whether to install future security updates.

 

[jent]

Happening to me on macOS Big Sur 11.6.3 with a 13" 2020 Intel MacBook Pro. I get a message upon restart that the system crashed. It doesn't seem to happen if I manually sleep the system.

 

[smunro]

Happening to me on macOS Big Sur 11.6.3 with a 13" 2020 Intel MacBook Pro. I get a message upon restart that the system crashed. It doesn't seem to happen if I manually sleep the system.

With the Catalina security update, the system does not seem to be crashing, which is the weird thing. Look at the log posted above: shutdowns are all normal, no sign of kernel panics, no message indicating a crash.

 

[NeonIbis]

I downloaded the full Big Sur installer today and installed that. I don't want to speak too soon (I'm yet to leave the computer asleep overnight), but Safari will now play video content again, Syspolicyd isn't constantly blasting the fans, and battery usage seems reasonable. So far, so good... This is a 2020 Intel Macbook Air, previously running Catalina with the latest updates.

 

[NeonIbis]

Further update: I left the MBA sleeping overnight and it didn't crash/restart! So, going from Catalina to Big Sur seems to have worked in my case.

I see that jent above had issues with the Big Sur security update. Perhaps try downloading the full installer? That's what I did (as I was on Catalina and didn't want to go to Monterey).

 

[Kernel Panicuser]

Hi everyone, I just got registered for responding this post. I do suffer this issue this week, and I litteraly had cauchemar on feeling helpless in dream?. Like many of you, a reinstall resolve the kernel panic. I've already sent the feedback to Apple, and I hope we can do more for help resolve the problem. By the way, I didn't got crash report neither after kernel panics and restarts.

 

[Andrew73875]

We should also submit this issue to macrumors here https://www.macrumors.com/share.php with a link to this thread. Story title can be something like "Some users experience unexpected restarts and shutdowns after Catalina Security Update 2022-001". Maybe they will publish an article which would be very helpful.

 

[Kernel Panicuser]

Another strange thing, I've followed this order of updates :
1) reinstall Catalina,
2) Safari 15.3 et device support update
3) security update 2021-08

After all that, I've noticed System Preferences pushed the same updates that I had done in step 2. So I redone the updates, and found some trace : the version of Safari has been changed a little (see image 1), perhaps due to the security update which was released earlier than Safari 15.3 (the correct version see image 2). Notice that just the last number is different (4.9.1.7 VS 4.9.1.8).