Process appstoreagent using 100% CPU in MacOS 27.0.1

Question

Level 1

31 points

Process appstoreagent using 100% CPU in MacOS 27.0.1

After upgrading to 27.0.1 every morning I wake up to an overheated MacBook Pro due to the process appstoreagent running at 99%. I have seen a discussion of this on MacRumors at https://forums.macrumors.com/threads/high-cpu-usage-due-to-processes-appstoreagent-and-dasd-exactly-between-midnight-and-9-am.2490572/. The opinion there is that this bug started with 27.0 (which I had not run on my laptop) and there had been hopes that 27.0.1 would have fixed it, but as far as I can tell it hasn't. That thread on MacRumors provides a workaround, which I've tried but found it didn't work for me. I have registered a bug report at Apple's feedback site, but of course you never hear anything back from Apple when you do that. Has anyone else seen this? Does anyone have a workaround other than the one on MacRumors? It is quite annoying!

MacBook Pro (M5, 2025)

Posted on Oct 28, 2026 2:47 PM

Reply

Answer 1

Oct 28, 2026 3:11 PM in response to lp1756

The very first thing you should probably do is update to 27.2 which released this week.

Reply

Answer 2

den.thed

Level 10

98,738 points

Oct 28, 2026 3:13 PM in response to lp1756

macOS 27.2 Golden Gate is the current version. Update to it and test for a day of two.

What's new in the updates for macOS 27 Golden Gate - Apple Support

Reply

Answer 3

lp1756 Author

Level 1

31 points

Oct 30, 2026 5:30 AM in response to lp1756

Update: 27.2 appears to have solved the problem. I've had two mornings without the problem and it had been consistently there before the upgrade. Thank you to those who provided help!

Reply

Answer 4

etresoft

Level 9

60,652 points

Oct 28, 2026 5:32 PM in response to lp1756

lp1756 wrote:

Has anyone else seen this? Does anyone have a workaround other than the one on MacRumors? It is quite annoying!

Yes. I saw it just the other day. In my case, it wasn't appstoreagent, just dasd. It also consumed about 460 GB of storage. I fixed it with this:

kill -9 <PID for dasd>; rm -Rf /private/var/db/DuetActivityScheduler; rm -Rf /private/var/db/powerlog/Library/PerfPowerTelemetry/BackgroundProcessing; rm -Rf /private/var/db/DuetActivityScheduler;

Reply

Answer 5

lp1756 Author

Level 1

31 points

Oct 28, 2026 5:41 PM in response to Randall_2023

Thanks for the info. Just two days ago I installed 27.0.1 by clicking on the update-tonight button which showed 27.0.1 as the next release. Didn't know there was already a 27.2. Odd that the Software Update dialog recommended 27.0.1, but there it is. I'll update to 27.2 tonight and post my findings on this bug after a day or so. Thanks again.

Reply