Warning about disabled SIP and latest macOS releases

[Moka Akashiya]

My friend has updated from 12.2 to 12.3.1 and got startup blackscreens / crashes / no network access from many macos apps, like browsers and electron stuff, like discord/vscode. I asked him to run app binaries from terminal, and this is some log lines for people, that will search similar problem:
ERROR:network_service_instance_impl.cc(975)] Network service crashed, restarting service. ERROR:gpu_process_host.cc(983)] GPU process exited unexpectedly: exit_code=9 FATAL:gpu_data_manager_impl_private.cc(448)] GPU process isn't usable. Goodbye.
There is no much good info from google, so i post this problem/solution here. Reason is disabled SIP before macos update, so enable and disable SIP in recovery mode terminal to fix system internals. This is first time i see something like that from Apple updates, but i guess, if you use macos with disabled SIP, you should enable it again before any update, and disable after if you want, since there is no guarantee to get worked OS without SIP after updates anymore.

 

[Fishrrman]

I've disabled SIP on every Mac I use since Apple introduced it.
I've never had any problems upgrading...

 

[Moka Akashiya]

Well, same here, but this problem happens on M1 Air, and cannot be fixed with reboots or app reinstallations, only with actual SIP toggle in recovery (even safe mode had app crashes!). This can be a temporary bug in 12.3.1 release/patch or only specific to Apple Silicon macs, but i personally would not to try updates without SIP in future, anyway.
Another reference with broken update:

vscocde got killed after updating to OSX 12.3 · Issue #145417 · microsoft/vscode

VSCode Version: Version: 1.65.2 Arm64 Local OS Version: macOS 12.3 (21E230) Steps to Reproduce: Got killed after updating to the latest OSX /opt/homebrew/Library/Taps/riscv/homebrew-riscv on  mast...

github.com

 

[bogdanw]

i personally would not to try updates without SIP in future, anyway.
Another reference with broken update:
https://github.com/microsoft/vscode/issues/145417

From that link, I understand that the cause might be an “unknown (Custom Configuration)” for SIP.
A simple check with csrutil status, to see if it returns “System Integrity Protection status: disabled.”, should be enough before an update.