crash launchservicesd (etrecheck pro report included)

CleanMyMac can not (or deliberately will not) un-install itself.

[in my opinion] CleanMyMac is indistinguishable from MALWARE.

the approved method for un-installing Apps (except CleanMyMac) has two parts:

anything installed by Drag-and-Drop to the /Applications folder can be Drag-and-Drop to the Trash Can. After a Restart, the software will be disengaged from MacOS, and the Trash may be emptied.

anything that was installed with a complex installer REQUIRES a complex un-installer. Search the original software maker's web site for the un-install script or procedure. Sometime un-install is an option of the Installer, and re-download of the Installer is required to obtain the un-installer.

ANY other methods, such as relying on CleanMyMac, is worse than just guessing, and leaves debris lying around to interfere with proper operation. Sometimes software like CleanMyMac has been found to remove parts of MacOS itself.

_______

you appear to have, at one time or another, installed every VPN known to humankind. Debris from improper removal of a dozen or more VPN packages it strewn all over your Mac, and it is a wonder your Mac operates ATA ALL.

You can not correctly operate a Mac with more Than ONE VPN active, and the appropriate number for most Users is ZERO.

your report also says:

 More than one antivirus app - This computer has multiple antivirus apps installed.

 Antivirus software: Apple, CleanMyMac, and AdGuard

the correct number of those for reliable operation is Apple antivirus and NO others.

That Mac has problems in addition to those Grant Bennet-Alder’s described.

In addition to his astute recommendations I strongly advise completely erasing that Mac and reconfiguring it from the ground up. Justifications for doing so go beyond the likely use of "CleanMyMac" despite its removal — merely removing it or similarly categorized "cleaning" products cannot undo the damage they are capable of inflicting upon a system. Justifications also include but are not limited to the possible presence of a configuration profile which can convey the ability for someone other than yourself to remotely control that Mac and to upload personal information from it to them. Configuration profiles are virtually limitless in that ability.

That Mac is a mess. I would not consider it secure at all. Erase it.

In addition to the wise counsel already offered, I see these:

1—Your SSD may be filling up:

Drives:

disk0 - APPLE SSD AP0512Q 500.28 GB (Solid State - TRIM: Yes)

Internal Apple Fabric NVM Express

disk0s1 [APFS Container] 524 MB

disk1 [APFS Virtual drive] 524 MB (Shared by 4 volumes)

disk1s1 - iSCPreboot (APFS) [APFS Preboot] (6 MB used)

disk1s2 - xART (APFS) (6 MB used)

disk1s3 - Hardware (APFS) (5 MB used)

disk1s4 - Recovery (APFS) [Recovery] (20 KB used)

disk0s2 [APFS Container] 494.38 GB

disk3 [APFS Virtual drive] 494.38 GB (Shared by 6 volumes)

disk3s1 - Macintosh HD - Data (APFS) [APFS Virtual drive] (420.53 GB used) ⚠️

2—Configuration Files:

/etc/hosts - Count: 8

See this for more information on those files:

Fixing a hacked /etc/hosts file - Apple Community

3—Are you using a off-site network for Time Machine backups, or do you have a networked drive attached?:

Backup:

Time Machine information is limited without Full Disk Access

Destinations:

M****M [Network] (Last used) 👈🏻

C***M [Local]

4 local snapshots

Oldest local snapshot: 2024-07-04 10:15:28

Last local snapshot: 2024-07-12 12:20:48

Hi,

I think it may be Sonoma's bug. You should send kernel crash report to Apple directly, though you may reported to Apple about it.