- Dec 10, 2010
- Gigabyte Z390 Aorus Elite
- Mobile Phone
"OC: Failed to load configuration!" always mean a config.plist file bad formed.Wondering if you could help me out. I am running OC
0.720.73 on my Hackintosh rig. My MoBo is an Esonic H81 one with Core i5 4750 processor and 12GB 1600 MHz RAM. I am running MacOS Big Sur on my WD SSD and Windows 10 & Kubuntu on my HDD. Everything is working perfectly except that every time I start up the machine OC's GUI Bootpicker doesn't show up. Rather "OC: Failed to load configuration!" - this message shows up each & every time. Only when I reboot the OC Bootpicker comes on the screen. Have no clue as to what the problem is. Googled it but no solution so far. I have attached my OC config & EFI folder.
Thanking you in advance.
It is advisable to have the habit of passing the config.plist file by the ocvalidate tool included in each OpenCore version. ocvalidate and config.plist must be from the same OpenCore version.
In your case (config.plist within the EFI folder) ocvalidate shows several errors:
OCS: Couldn't get array serialized at 0 index! OCS: Couldn't get array serialized at 1 index! OCS: Couldn't get array serialized at 2 index! OCS: Couldn't get array serialized at 3 index! OCS: Missing key ForceOcWriteFlash, context <Quirks>! Serialisation returns 5 errors! Booter->Quirks->ProvideCustomSlide is enabled, but OpenRuntime.efi is not loaded at UEFI->Drivers! Booter->Quirks->EnableWriteUnprotector is enabled, but OpenRuntime.efi is not loaded at UEFI->Drivers! CheckBooter returns 2 errors! UEFI->Quirks->RequestBootVarRouting is enabled, but OpenRuntime.efi is not loaded at UEFI->Drivers! CheckUEFI returns 1 error!
These errors mean:
- OCS: Could not get array serialized at x index: the UEFI >> Drivers section has changed, review the post 1 to see how you must correct it
- Booter >> Quirks and Uefi >> Quirks are related to drivers part, you aren't loading OpenRuntime.efi, fixing drivers must fix them.