Essential problem: certificate trust configuration file is damaged
discovery operation: /usr/bin/security dump trust settings - d
operation result:

SecTrustSettingsCopyCertificates: The Trust Settings Record was corrupted.

Delete /library/security/trust settings/Admin. Plist , which is the configuration file. Go back to the keychain and click trust configuration again

Cause

Clashx can’t even get on it

After

looking at clashx log: found
error: x509: failed to load system roots and no roots provided; Sectrustsettingscopycertificates error: - 25262 error checking: sectrustsettingscopycertificates seems to be a function, which has been mentioned in many issues of GitHub, most of which are go and sublime text, such as
and
functions https://github.com/golang/go/issues/42414 , to trust digicert global root CA
Baidu first, said to repair the operating system, So I looked at some of them. Fortunately, there was an upgrade package, but why couldn’t it be changed??Can’t save after clicking??Strange, it’s impossible to find this kind of magic question. Do you really want to ask MAC questions
delete the import, no, import a new one, no, update it. Sure enough, I didn’t accidentally see an article: https://stackoverflow.com/questions/33224830/error-executing-security-dump-trust-settings-in-sublime-text-3
/usr/bin/security dump-trust-settings -d??
the trust settings record was corrupted????Of course you have to pay attention to that?But Baidu came out and found that there was only one. It didn’t know what it was doing. It put it aside first, and it was a mess. When it came back, it used Bing search, and didn’t know how to do it. X2, Google search, the first, classic deletion configuration???https://apple.stackexchange.com/questions/374890/how-to-remove-a-corrupted-trust-settings-record
/ library/security/trust settings/Admin. Plist
looking back, sure enough, none of the trust configurations have specified values
as soon as I opened it, I couldn’t see anything, but one of the following UUID’s files was obviously deleted decisively. Trust digicert global root CA again, and you’re done

However, when updating the clear space, I found that the impression notes took up another 12g, and the handsoff log wrote another 2 g, which solved the problem of “locking up the water in the world” after deleting Xcode, and made the computer live again