Screenshots fail after upgrade from Sonoma to Sequoia 15.1 plus other related issues on MBP M1

Ok, I did a restart this morning after waking up the MBP so things are working again as of this writing.. ..

I understand what you're saying but that in itself is an issue not caused by the owner. I also understand that third party programs like Adobe, Microsoft, etc need to keep their updates coming to be compatible with the platforms they live on and that may take a bit of time when Apple releases a new OS.

For me, it's the Apple native stuff that is breaking.. .. screenshot, Finder, etc. I have a plan of action today to try and come to grips with this. I will certainly post what I do along with the results and will reply to PRP_53 next.

Status as of Nov 20, 2024. 3 Days after initial post for help

The three of you (jeffreythefrog, dialabrain and PRP_53) all suggested I run an Etretech report, so I did. From the report I posted, here is what I have done as of this writing.. .. 

App extensions:

- Deleted: NetworkProtectionSystemExtension - version 1.68.0 (Duck Duck Go, Inc. - installed 2023-12-12)

- Deleted: Application: /Applications/DuckDuckGo.app/Contents/Library/LoginItems/DuckDuckGo VPN.app - version 1.68.0 (Duck Duck Go, Inc. - installed 2023-12-12)

Safari extension:

- Deleted: [Loaded] Privacy Dashboard - /Applications/DuckDuckGo Privacy for Safari.app

Clean up:

- Deleted: ~/Library/LaunchAgents/com.adobe.AAM.Updater-1.0.plist /Library/Application

After removing these items, I deleted the trash and did a Shut Down. Then…

* Through observation I am thinking that the issue is with Finder and its triggered by taking a screenshot after waking it from a sleep of unknown sleep time

- Powered up, did my work, made several screenshots, played around with Finder, everything worked as it should. 

- Once done working, I put it to sleep. I normally use keyboard commands for this.. . .Option-Command-Eject key combo (I use an extended kybd)

- Pressed space bar to wake it a few hours later: Everything worked as it should. Was it asleep long enough to have caused the issue or not???

- Once done working, I put it to sleep for the remainder of the day. 

Next Day - let’s call this Day 1 (after the deletions)

- Pressed space bar to wake it, Everything worked as it should. This was an overnight sleep which was long enough to historically have the issue show up, but it didn’t. I’m now a bit optimistic but keeping in mind that the issue started after the upgrade from Sonoma to Sequoia which was only six days ago so there isn’t a lot of experience with this yet.

- Once done working, I put it to sleep. 

- Pressed space bar to wake it a few hours later: Everything worked as it should. 

- Once done working, I put it to sleep. 

- Pressed space bar to wake it a few hours later: Everything worked as it should. 

- Once done working, I put it to sleep for the night

Day 2

- Pressed space bar to wake it, Everything worked as it should.

- Basically day 2 was a repeat of day 1. Some number of sleeps, wakes, working, etc and all worked as it should

Day 3 - Today

 - Today proved to be a repeat of Day 2. Certainly by now, the issue would have happened several times with subsequent reboots between each one. I am happy to report that as of this writing, after several sleep/wake periods, all is well.

Unfortunately, I did all the deletes before retesting so it's hard to know if any one of them was the root. I will now let this go for about a week or so before coming back with another update so stay tuned.. .. 

I always expect a few issues when upgrading, I always wait till a .1 or .2 before upgrading due to that. It's a complex code and all the testing in the world will not cover 100% of what we do with our puters and what we have connected to them. I get that. However, its still frustrating and of course the screenshot is a function I use several times/day and no one likes having to clear the screen of all running apps in order to reboot to get screenshot working again, but I do remember my days, long ago now, when living in the Microsoft world - it was much worse!

How did you open Screenshot and change the save location?

Thanks! didn't know that as my default method to make a screenshot is the Shift-Command-4 key combo but after dragging the Screenshot app to the dock and selecting it, that menu that you showed automatically appears at the bottom of the screen for me. However, my menu doesn't have some of the items like yours, for instance: Microphone doesn't show up.

The good news is the screenshot is still working for me!

Just found that out, I started playing around with it and found that you can do screen "recording" ...of course with voice, that's when the microphone section showed up. I've used Quicktime for this in the past, next time I'll try the Screenshot app. Always learning.. .. ..

To be brutally honest, I came here instead of contacting Apple Support. I believed I would get higher quality help. It's rare that a level one tech support person can help me anymore, even when I've done the leg work and give them that info. Escalating to level 2 takes time and even then, you get "one" level 2 person whereas posting here can have a multitude of people chiming in.

I seriously doubt Apple Support would have found the issue, they probably would have told me to reinstall the OS, truth be told that was already in the back of my mind :-) but there were still some troubleshooting steps I had not yet taken, like isolating my MBP from all peripherals, etc (which I didn't have to do :-)

Day 7 post Etretech suggested actions (refer to my Nov 20 at 5:40pm post)

I had a Finder issue yesterday where it hung up and refused to work. When this happens, screenshots stop working as well and so did Preview. In looking at the logs, I'm of the opinion that Photoshop hung and the rest were a result of that. While I can't be sure, the Photoshop issue happened before the Finder issue. A reboot brought everything back to normal.

I then ran Etretech again but nothing new or different was found as compared to after I had taken its recommendations back on Nov 20. I decided to do the Apple Hardware Test and it ended with code ADP000 No Issues Found. A point estimate. I then booted in Safe Mode and then back to normal mode. I still wonder why all this started upon the upgrade to Sequoia???