That truly sucks, and your mac is compatible. thats sad...i came here to contemplate an upgrade from 14.3.1 on my 5,1, but the doubt has krept in.I'm on an intel-based Macbook Pro 16 from late 2019 and still getting multiple crashes per day on Sonoma 14.4.1. This is just getting ridiculous and I'm honestly wondering if it was a mistake to go to MacOS from Windows. I might just wipe my Macbook and try and go back to Ventura this weekend. FYI, I had no issues before upgrading to 14.4.0
Oh man. Is no one else seeing this issue or something similar? Every time I come back to my M1 MBP when the Screensaver is running and continue to use my Mac again, the Keyboard Backlight is staying all the way down to 0%/Off. I've even reinstalled macOS from DFU mode and set it up as new and it happens without installing any of my apps yet. Just a straight up default install. It's not like the Keyboard Backlight is broken, I can still turn it all the way back up. I have it set to turn off after 30 seconds of inactivity, and that part works just fine. It's just when coming back to it when the Screensaver comes on. And what's weird is I have a hot corner setup to start the Screensaver, and this doesn't happen when invoking that, only when there's inactivity and then the Screensaver comes on. Then the Keyboard Backlight stays off. So annoying.I'm still seeing an issue where my M1 MBP Keyboard Backlight slider gets set to all the way off after the Screensaver comes on. Doesn't matter what Screensaver I choose. I've checked apps like Amphetamine to make sure they're not at fault..
FB13647085
I'm on an intel-based Macbook Pro 16 from late 2019 and still getting multiple crashes per day on Sonoma 14.4.1. This is just getting ridiculous and I'm honestly wondering if it was a mistake to go to MacOS from Windows. I might just wipe my Macbook and try and go back to Ventura this weekend. FYI, I had no issues before upgrading to 14.4.0
FYI, just an update, still getting multiple crashes daily and now I can no longer do Time Machine backups because it says the Data volume has become corrupted. Booted into Recovery Mode to run the First Aid disk utility and it can't fix it. So tomorrow I'm going to erase the entire volume and go back to Ventura. Hopefully it's not a physical issue with the SSD but I do have AppleCare coverage until the end of this year. I'm currently saving everything in the cloud as I currently don't trust this Macbook Pro.I'm on an intel-based Macbook Pro 16 from late 2019 and still getting multiple crashes per day on Sonoma 14.4.1. This is just getting ridiculous and I'm honestly wondering if it was a mistake to go to MacOS from Windows. I might just wipe my Macbook and try and go back to Ventura this weekend. FYI, I had no issues before upgrading to 14.4.0
Please keep us posted. I also have a MacBook Pro 16 from 2019 and this concerns me.FYI, just an update, still getting multiple crashes daily and now I can no longer do Time Machine backups because it says the Data volume has become corrupted. Booted into Recovery Mode to run the First Aid disk utility and it can't fix it. So tomorrow I'm going to erase the entire volume and go back to Ventura. Hopefully it's not a physical issue with the SSD but I do have AppleCare coverage until the end of this year. I'm currently saving everything in the cloud as I currently don't trust this Macbook Pro.
If switching to Ventura fixes my issues, I'll know Sonoma was the issue, if it doesn't then I'll assume my SSD has become physically damaged (maybe due to Sonoma 14.4 crashes??) and I can contact AppleCare support for repairs. I'll post an update next week.
So, unfortunately for me, it appears I have an issue with the storage system on my Macbook Pro. While I didn't have any issues prior to Sonoma 14.4, I think the weeks of multiple daily crashes put enough strain on my system to cause something to physically fail. After installing Ventura it only took about 45 minutes into setting stuff up for it to crash again. I'll have to contact AppleCare coverage and am probably looking at a motherboard replacement. On a side note, Ventura seems noticeably snappier than Sonoma.FYI, just an update, still getting multiple crashes daily and now I can no longer do Time Machine backups because it says the Data volume has become corrupted. Booted into Recovery Mode to run the First Aid disk utility and it can't fix it. So tomorrow I'm going to erase the entire volume and go back to Ventura. Hopefully it's not a physical issue with the SSD but I do have AppleCare coverage until the end of this year. I'm currently saving everything in the cloud as I currently don't trust this Macbook Pro.
If switching to Ventura fixes my issues, I'll know Sonoma was the issue, if it doesn't then I'll assume my SSD has become physically damaged (maybe due to Sonoma 14.4 crashes??) and I can contact AppleCare support for repairs. I'll post an update next week.
It is very perplexing why Apple allows iCloud to suck so badly. It's an internal part of the ecosystem, and yet it's routinely horrible.I was affected, lost some very important documents and photos, and still not fixed after installind 14.4.1
I've had this same issue for what seems like Months, actually. No real 'Fix' for this from what I've found.I am having the same problem as this thread on the latest MacOS Sonoma 14.4.1 on Macbook Air M2 13 inch
https://forums.macrumors.com/thread...-focus-after-closing-any-application.2384794/
Relaunching Finder fixes the problem, but the issue comes back on the next reboot, even after removing all login items. The issue does not occur in safe mode.
I notice that the problem only happens if I leave Finder as the last active app before restarting (leave MacOS to show Desktop). For example, if I leave Chrome open and restart, the issue will not happen. The option to reopen windows when logging back in is checked.
The issue also happens with a new Admin user.
You can test this out by doing these steps:
- Leave finder the last active app (show the Desktop)
- Restart with the option to reopen windows checked
- After restarting, open Chrome or any other apps
- Open System settings
- Close System settings -> focus switched to finder instead of Chrome (or any other last apps) -> the problem
Has anyone had the same issue and found the solution? Thanks for your comments.
Glad I’m not alone. What macOS version you’ve had this problem with? And did you try a clean MacOS reinstall?I've had this same issue for what seems like Months, actually. No real 'Fix' for this from what I've found.
I’m on macOS 14.4.1, and I’ve reinstalled macOS on my M1 machine just recently. Been having this issue almost all of Sonoma.Glad I’m not alone. What macOS version you’ve had this problem with? And did you try a clean MacOS reinstall?
Thanks. Let's file a bug report and hopefully Apple will fix this issue http://www.apple.com/feedbackI’m on macOS 14.4.1, and I’ve reinstalled macOS on my M1 machine just recently. Been having this issue almost all of Sonoma.
I don't see this issue on my MBA M2 running MacOS 14.4.1Oh man. Is no one else seeing this issue or something similar? Every time I come back to my M1 MBP when the Screensaver is running and continue to use my Mac again, the Keyboard Backlight is staying all the way down to 0%/Off. I've even reinstalled macOS from DFU mode and set it up as new and it happens without installing any of my apps yet. Just a straight up default install. It's not like the Keyboard Backlight is broken, I can still turn it all the way back up. I have it set to turn off after 30 seconds of inactivity, and that part works just fine. It's just when coming back to it when the Screensaver comes on. And what's weird is I have a hot corner setup to start the Screensaver, and this doesn't happen when invoking that, only when there's inactivity and then the Screensaver comes on. Then the Keyboard Backlight stays off. So annoying.
Sorry but may I ask did you try the test that I mentioned by doing the following steps:I've had this same issue for what seems like Months, actually. No real 'Fix' for this from what I've found.
Sorry but may I ask did you try the test that I mentioned by doing the following steps:
Because there is a comment says that there is no issue: https://forums.macrumors.com/thread...closing-any-application.2424078/post-33092561
- Leave finder the last active app (show the Desktop)
- Restart with the option to reopen windows checked
- After restarting, open Chrome or any other apps
- Open System settings
- Close System settings -> focus switched to finder instead of Chrome (or any other last apps) -> the problem