Skip to content

← All issues

Update: Additional Context and Verbose Logs from v.7 Crashes

· by @Skjen-911 · edited October 18, 2026

needs-version-infoneeds-mac-model

Hi devs,

This is an addendum to my previous test report.

I've carefully reviewed the 19.9.9 changelog. The fact that the old boot.efi (OpenCore 1.0.4) and the old Spoof-VMM were causing unstable installations perfectly explains my failure yesterday. I was indeed using the older .7 version.

To help you further debug the T2TahoeFixup and the PMU/SEP deadlocks, I have transcribed the most critical lines from my previous crash logs (version .7). I believe the specific services hanging right before the panic will be very helpful.

Here are the two failure scenarios:

Scenario 1: Clean Install (Failed early with PMU deadlock)
Context: Pure APFS volume, Reset NVRAM. It stalled early without loading the UI. The screen froze at:
using hsynchronous pmu monotonic clock read

Scenario 2: Cover Install (Reached Login Window, but panicked at Login)
Context: Overwritten on a volume with mixed Preboot caches. It successfully loaded WindowServer, but upon entering the password, AppleKeyStore timed out. Here are the tail logs before it locked up:

Log Block 1 (fskitd & AMFI issue):
com.apple.xpc.launchd[2026-10-18 02:21:37.146744] (system) : fail...
methodConfigureUserClient: client pid: 139 pidversion: 346 supportBl...
AppleActuatorDeviceUserClient::start Entered
ALUC:clientDied(pid: 139 pidversion: 346), fskitd_entitled 0 fsmodule_enti...
lifs_destroy_louc_container: container removed (pid 139 pidversion 3...
AMFI: [non-fatal] unable to accelerate context: com.apple.hfs | 65285
up: name = com.apple.networkd_privileged, flags = 0x8, requestor = configd...
com.apple.xpc.launchd[2026-10-18 02:21:37.146854 (pid/139 [com.apple.fskit...
com.apple.xpc.launchd[2026-10-18 02:21:37.147109 (system) : denie...
com.apple.xpc.launchd[2026-10-18 02:21:37.151032 (system/com.apple.BlueTool...

Log Block 2 (Infinite loop skipping boot tasks):
com.apple.xpc.launchd[2026-10-18 02:43:49.331081] [INFO] (System) : Skipping boot-task: (system/com.apple.osanalyticsd)
com.apple.xpc.launchd[2026-10-18 02:43:49.346469] [INFO] (System) : pending spawn, domain in on...
com.apple.xpc.launchd[2026-10-18 02:43:49.350118] [INFO] (System) : pending spawn, domain in on...
com.apple.xpc.launchd[2026-10-18 02:43:49.355091] [INFO] (System) : (com.apple.opendirectoryd) : This service is...
com.apple.xpc.launchd[2026-10-18 02:43:49.357293] [INFO] (System) : (com.apple.audio.coreaudiod) : The...
com.apple.xpc.launchd[2026-10-18 02:43:49.356608] [INFO] (System) : pending spawn, domain in on...
com.apple.xpc.launchd[2026-10-18 02:43:49.356903] [INFO] (System) : pending spawn, domain in on...

Key observation: In Scenario 2, AppleActuatorDeviceUserClient (related to the T2's built-in keyboard/trackpad controller and SEP) and com.apple.fskit seem to be failing or dying right before the loop starts.

I am currently downloading the new 19.9.9 release. I will run a clean install test on a fresh partition and provide the new verbose logs shortly.

Thank you all!
2018 MacBook Air
macOS 14/macOS 26

Comments

@github-actions ·

Hi @Skjen-911, thanks for the report! We need to know which Mac this is about — the patches OpenCore Legacy Patcher applies depend on the exact model. Please edit your issue or reply below with your model identifier. You can get it by running this in Terminal:

sysctl -n hw.model

It prints something like Macmini8,1 or MacBookPro16,2. If you can't boot into macOS, the model name with its year works too (e.g. "Mac mini 2018", shown under → About This Mac).

This comment will go away once the model is added.

@github-actions ·

Hi @Skjen-911, thanks for the report! To look into this we need to know exactly which versions you're running. Please edit your issue or reply below with:

  • macOS version, ideally with the build number (e.g. 26.6.1 (25G76)). You can find it under → About This Mac, or by running sw_vers in Terminal. Image

"Latest" or "new" isn't enough, since new builds come out often. This comment will go away once the versions are added.

@albert-mueller ·

Hi devs,

This is an addendum to my previous test report.

I've carefully reviewed the 19.9.9 changelog. The fact that the old boot.efi (OpenCore 1.0.4) and the old Spoof-VMM were causing unstable installations perfectly explains my failure yesterday. I was indeed using the older .7 version.

To help you further debug the T2TahoeFixup and the PMU/SEP deadlocks, I have transcribed the most critical lines from my previous crash logs (version .7). I believe the specific services hanging right before the panic will be very helpful.

Here are the two failure scenarios:

Scenario 1: Clean Install (Failed early with PMU deadlock) Context: Pure APFS volume, Reset NVRAM. It stalled early without loading the UI. The screen froze at: using hsynchronous pmu monotonic clock read

Scenario 2: Cover Install (Reached Login Window, but panicked at Login) Context: Overwritten on a volume with mixed Preboot caches. It successfully loaded WindowServer, but upon entering the password, AppleKeyStore timed out. Here are the tail logs before it locked up:

Log Block 1 (fskitd & AMFI issue): com.apple.xpc.launchd[2026-10-18 02:21:37.146744] (system) : fail... methodConfigureUserClient: client pid: 139 pidversion: 346 supportBl... AppleActuatorDeviceUserClient::start Entered ALUC:clientDied(pid: 139 pidversion: 346), fskitd_entitled 0 fsmodule_enti... lifs_destroy_louc_container: container removed (pid 139 pidversion 3... AMFI: [non-fatal] unable to accelerate context: com.apple.hfs | 65285 up: name = com.apple.networkd_privileged, flags = 0x8, requestor = configd... com.apple.xpc.launchd[2026-10-18 02:21:37.146854 (pid/139 [com.apple.fskit... com.apple.xpc.launchd[2026-10-18 02:21:37.147109 (system) : denie... com.apple.xpc.launchd[2026-10-18 02:21:37.151032 (system/com.apple.BlueTool...

Log Block 2 (Infinite loop skipping boot tasks): com.apple.xpc.launchd[2026-10-18 02:43:49.331081] [INFO] (System) : Skipping boot-task: (system/com.apple.osanalyticsd) com.apple.xpc.launchd[2026-10-18 02:43:49.346469] [INFO] (System) : pending spawn, domain in on... com.apple.xpc.launchd[2026-10-18 02:43:49.350118] [INFO] (System) : pending spawn, domain in on... com.apple.xpc.launchd[2026-10-18 02:43:49.355091] [INFO] (System) : (com.apple.opendirectoryd) : This service is... com.apple.xpc.launchd[2026-10-18 02:43:49.357293] [INFO] (System) : (com.apple.audio.coreaudiod) : The... com.apple.xpc.launchd[2026-10-18 02:43:49.356608] [INFO] (System) : pending spawn, domain in on... com.apple.xpc.launchd[2026-10-18 02:43:49.356903] [INFO] (System) : pending spawn, domain in on...

Key observation: In Scenario 2, AppleActuatorDeviceUserClient (related to the T2's built-in keyboard/trackpad controller and SEP) and com.apple.fskit seem to be failing or dying right before the loop starts.

I am currently downloading the new 19.9.9 release. I will run a clean install test on a fresh partition and provide the new verbose logs shortly.

Thank you all! 2018 MacBook Air macOS 14/macOS 26

Yeah, to me it seems more likely to be a kext issue in the T2Fixup, and less likely to be the package itself causing issues.