Is it normal to have so many access denied errors due to sandbox for apple system processes?

I did a DFU restore yesterday, which offered me Ventura 13.1, so I installed it. I may try again with a different ipsw file to get it back to Monterey, Ventura 13.1 still has problems with System Settings not sticking the first time. From the point of view of the GUI, it appears that most things are operating as expected, though I'm having some problems editing this message (copy and pasted text disappears, beachballs occasionally and keystrokes arriving out of order).

It hasn't made a difference, in fact, I seem to be getting more errors.

Still have lots of Sandbox errors, though when I put some of those programs in "allow full disk access", I started getting errors that they are duplicates of other sandbox accesses granted, and, at times, messages to the effect of "why does this program have access to this" messages. It's hard to tell if it's by design or if it's an actual problem. Perhaps I'm just seeing the initial error message, and the system attempts to give it sandbox permissions after that, but I don't think most are successful, but it's hard to tell without some deep log analysis by me.

I've noticed that a lot of these errors are actually "To Do" messages to remind Apple developers of what still needs to be done, or simply checkpoints for following a process' process. More like "Info" messages than "Error" messages. But I still get more than a few "Fault" messages, and a lot of these errors cause actual problems in the desktop environment, i.e. the problem reaches the GUI and the errors are affecting Apple default programs like Safari.

Particularly concerning to me are the

 45001 wakeups over the last 153 seconds (293 wakeups per second average), exceeding limit of 150 wakeups per second over 300 seconds 

that a few processes are causing.

I get a lot of these types of messages, as well.

fault	15:13:20.299185-0600	com.apple.Safari.History	Couldn't read values in CFPrefsPlistSource<0x600003dc0980> (Domain: kCFPreferencesAnyApplication, User: kCFPreferencesAnyUser, ByHost: Yes, Container: (null), Contents Need Refresh: Yes): accessing these preferences requires user-preference-read or file-read-data sandbox access

followed by

error    15:13:20.310324-0600	cfprefsd	rejecting read of { kCFPreferencesAnyApplication, bob, kCFPreferencesCurrentHost, /Users/bob/Library/Preferences/ByHost/.GlobalPreferences.1C8F38D1-F980-525A-B115-5E18C3B3A296.plist, managed: 0 } from process 503 (com.apple.Safari.History) because accessing these preferences requires user-preference-read or file-read-data sandbox access.   

so I believe cfprefsd is having difficulty reading preferences, and that's where the majority of my problems are coming from. I get a lot of these

error	16:20:20.026809-0600	cfprefsd	Couldn't open parent path due to [2: No such file or directory]

but, that may just a message that cfprefsd has exited a read prefs loop by reaching the end of it, I can't tell, but when I add cfprefsd to "allow full disk access", I get these errors:

error	16:29:59.235518-0600	kernel	Sandbox: analyticsd(166) deny(1) file-issue-extension target:/private/var/db/analyticsd/Library/Preferences/analyticsd.plist class:com.apple.cfprefsd.read-write

so maybe it shouldn't be there, in any event other systems are telling cfprefsd that it can't do something, regardless of what I granted it.

It gets worse once iCloud is involved, Family can't get what it asks for:

error	16:18:08.326345-0600	Family	Unable to open XPC store: Error Domain=NSCocoaErrorDomain Code=134060 "A Core Data error occurred." UserInfo={Problem=Unable to send to server; failed after 8 attempts.} {
    Problem = "Unable to send to server; failed after 8 attempts.";
}

The logs are also rolling over very quickly, due to all the messages.

Personally, I think it's Ventura 13.1 - there's no excuse to release this update in this condition. My system passes diagnostics, it's a clean install: "erased contents and settings", put it into DFU mode and restored (not revived) the DFU successfully, installed 13.1 when the system started the "Hello" screens, and yet I still have all these errors and faults.

But, considering all System Settings that don't stick occasionally, I'm going to punt and install Monterey on here. I'll wait until Ventura is ready for primetime before I'll install it.

It would be interesting to know whether other users of 13.1 get the same types of errors.

Thank you for your response

No, my DFU is fine, it boots into Normal mode and passes all the steps of a normal boot.

I'm sorry I wasn't very clear in my initial post, I created the USB install like this: Create a bootable installer for macOS - Apple Support did Erase your Mac and reset it to factory settings - Apple Support and then Use Disk Utility to erase a Mac with Apple silicon - Apple Support rebooted into Recovery mode and chose the Ventura install on the USB stick. The other choice was to continue and install Monterey.

I'm wondering, if by logging into iCloud, I brought back garbage or something?

I'll try another clean install and let it load the Monterey package instead, just to see if the system is sane, and then try the Ventura 3.1 install after that.

Oh! Perhaps you’re right. I did a standard Erase Contents and Settings and let it reinstall today and still had a problem getting the computer name to propagate, as well as network settings for connections not saving some preferences on the first try. Also, still getting a lot of sandbox related access denied errors in the log. I’ll reinstall the DFU tomorrow and see if it helps.

Thanks!

While I agree that I could ignore the logs, it doesn’t rectify my problem with System Settings not behaving well. A quick look at other posts indicates that the System Settings not sticking problem is prevalent. I would guess less than one in a thousand users post here about any particular problem, and this issue is getting mentioned often. I would consider it widespread at this point.

I am a fan of eclecticlight.co, as well. Very good site and it was a very good tip, thanks.