WindowsmacOSLinux

Where Does OpenCore Store Its EFI Files?

OpenCore boots from an EFI partition folder with config.plist, drivers and kexts. Mount paths for Windows, Mac and Linux.

Last updated

OpenCore lives on the EFI system partition, outside any OS. The loader and its files sit in EFI/OC: config.plist for the whole setup, plus Drivers, Kexts, ACPI and Tools beside it. A second folder, EFI/BOOT, holds the fallback loader that points at it.

The partition is hidden by default on every OS. You mount it first, then edit. On Windows that means mountvol, on Mac a diskutil mount, on Linux the /boot/efi mount most installers create. Keep a known-good USB copy before editing config.plist.

Where OpenCore stores this, by platform

Windows
EFI\OC\config.plist (on the EFI system partition)

Mount with mountvol S: /S, then open S:\EFI\OC. Drivers, Kexts, ACPI and Tools sit beside config.plist. Back up the USB stick that boots before touching the internal copy.

macOS
/Volumes/EFI/EFI/OC/config.plist

Mount with diskutil list then diskutil mount diskXs1. Same OC layout with config.plist plus support folders. Editing the live internal EFI without a spare boot stick risks an unbootable machine.

Linux
/boot/efi/EFI/OC/config.plist

Most distros mount the EFI partition at /boot/efi. Same OC tree beneath it. Validate config.plist with ocvalidate after edits and keep the previous copy until the next boot succeeds.

Frequently asked questions

How do I mount the EFI partition?

On Windows run mountvol S: /S from an admin prompt. On Mac use diskutil mount on the EFI identifier. On Linux check /boot/efi, which most installers mount already. Unmount cleanly when done editing.

Which OpenCore files do I back up?

The whole EFI/OC folder plus EFI/BOOT. Config.plist alone is not enough, since driver and kext versions must match it. A full folder copy to a FAT32 USB stick gives a bootable fallback.

Where is the OpenCore boot log?

Beside the ESP files when Misc Debug logging targets disk, often EFI/OC/misc or the picked SysReport path. Set the target back to display after troubleshooting so logs do not pile up on the small partition.

Notice an outdated path? Let us know.