Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tamhow to create OpenCore Catalina USB installation drive
To create an OpenCore Catalina USB installer, do two separate things:
createinstallmedia.If you have access to a Mac, that is the easiest and preferred path because Dortania’s current guide still treats macOS as the route for a full offline installer. On Windows or Linux, the supported method is generally an online recovery installer, not a full offline Catalina installer. (dortania.github.io)
A practical short version is:
/Applications, ideally 10.15.7, the final Catalina release. (dortania.github.io)MyVolume. (dortania.github.io)createinstallmedia command. (support.apple.com)config.plist, required drivers, kexts, and ACPI files for your exact hardware. (dortania.github.io)An OpenCore Catalina USB is not a single file-writing operation. It is a combination of:
That distinction matters because many outdated guides blur the two steps. If the Apple installer is correct but the EFI is wrong, the USB will boot OpenCore but fail to start Catalina. If the EFI is correct but the Apple installer is missing, OpenCore will load but you will have nothing to install. (support.apple.com)
If you have a working Mac or existing macOS environment, use this route:
Step A — Download Catalina
Use either the App Store route or Terminal. Dortania’s current macOS installer guide explicitly supports modern macOS downloads by App Store or softwareupdate, and Apple’s own installer article expects the downloaded installer app to be in /Applications. (dortania.github.io)
You can list and fetch installers from Terminal:
softwareupdate --list-full-installers
softwareupdate --fetch-full-installer --full-installer-version 10.15.7This is the cleanest way to request the final Catalina build, 10.15.7. (dortania.github.io)
Step B — Erase the USB In Disk Utility, choose Show All Devices, select the physical USB device, then erase it as:
MyVolumeMac OS Extended (Journaled)GUID Partition Map (dortania.github.io)Apple notes that the USB will be erased and reformatted during this process, and Dortania notes that formatting this way creates the visible installer volume plus the hidden EFI partition used later for OpenCore. (support.apple.com)
Step C — Create the Catalina installer Run:
sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolumeThat is Apple’s current Catalina command, and Dortania reproduces the same command in its updated installer guide. (support.apple.com)
When Terminal finishes, the USB is now a valid Apple Catalina installer. At this stage it is still not yet a complete OpenCore USB for PC hardware. (support.apple.com)
Next, mount the USB’s EFI partition. On macOS you can do that with diskutil:
diskutil list
sudo diskutil mount diskXs1Replace diskXs1 with the EFI partition belonging to your USB. Dortania notes that the EFI partition exists after GUID formatting but is hidden until mounted. (dortania.github.io)
Then copy the base EFI folder from the appropriate OpenCorePkg build onto the USB’s EFI partition. For Catalina-era systems you will almost always use X64, because macOS 10.8 and newer require EFI64. Dortania’s current guide also recommends using the DEBUG build first because it is much easier to troubleshoot than RELEASE. (dortania.github.io)
Your USB’s EFI should end up conceptually like this:
EFI
├── BOOT
│ └── BOOTx64.efi
└── OC
├── ACPI
├── Drivers
├── Kexts
├── Tools
└── config.plistThis is the standard OpenCore layout expected by the guide. (dortania.github.io)
The most important contents are:
Drivers
OpenRuntime.efiHfsPlus.efi (dortania.github.io)Dortania’s current guidance says these are the two .efi drivers needed for the majority of systems. HfsPlus.efi allows OpenCore to see HFS-based installer and recovery volumes, and OpenRuntime.efi is required for proper OpenCore operation and memory/NVRAM handling. (dortania.github.io)
Kexts
Lilu.kextVirtualSMC.kextWhateverGreen.kextAppleALC.kext, Ethernet kexts, USB mapping-related items, laptop input kexts, etc. (dortania.github.io)Dortania currently treats Lilu and VirtualSMC as non-optional boot essentials, and WhateverGreen as a required graphics helper for essentially all GPUs. (dortania.github.io)
ACPI You also need the correct SSDTs for your platform, for example EC/plug/power-management related SSDTs depending on your CPU generation and motherboard. This is why OpenCore USB creation is never fully universal. (dortania.github.io)
config.plist correctlyDo not start from a random prebuilt plist if you can avoid it. The current guide says to take Sample.plist from OpenCorePkg/Docs, copy it to EFI/OC/, and rename it to config.plist. Then use ProperTree and perform a Clean Snapshot so the plist matches the exact files currently present in your EFI/OC folders. (dortania.github.io)
A typical workflow is:
OpenCorePkg/Docs/Sample.plist
→ copy to EFI/OC/
→ rename to config.plist
→ open in ProperTree
→ Cmd/Ctrl + Shift + R
→ point to EFI/OCDortania explicitly warns that config.plist must match the contents of your EFI exactly; if a file is listed in the plist but missing from disk, OpenCore can stop booting. Dortania also explicitly advises using ProperTree and warns that OpenCore Configurator is heavily outdated and known for corruption issues. (dortania.github.io)
The USB creation itself is generic; the OpenCore configuration is not. Your config.plist, SSDTs, SMBIOS choice, device properties, and some kext choices depend on:
In engineering terms, OpenCore is an abstraction layer between your firmware/hardware and Apple’s expected boot environment. If you mismatch that layer, the USB may appear valid but fail at ExitBootServices, stall on PCI/ACPI initialization, miss the installer volume, or panic mid-boot. That is why a “universal EFI” is usually unreliable. This is an inference from the guide’s per-platform configuration structure and hardware-specific setup flow. (dortania.github.io)
After building the USB, boot the target machine from the USB and select the OpenCore entry in your firmware boot menu. In the OpenCore picker, the installer may appear as macOS Base System (External), Install macOS ..., or the USB drive name. On newer OpenCore setups, you may need to press Space if the installer is hidden by HideAuxiliary. (dortania.github.io)
When you reach Disk Utility in the installer, the target drive should be prepared as GUID + APFS for Catalina. After the first reboot, do not boot the raw USB installer again; boot back into OpenCore and select the temporary macOS Installer entry on the destination drive so installation can continue. (dortania.github.io)
Dortania’s current supported guidance is different here:
macrecovery.py, put the downloaded BaseSystem/RecoveryImage files in com.apple.recovery.boot, then place the OpenCore EFI folder beside that. (dortania.github.io)So if your goal is a full offline Catalina installer, macOS remains the best host OS. If your goal is simply “boot a Catalina installer with OpenCore,” Windows and Linux can still do it using the recovery-based method. (dortania.github.io)
As of the current Dortania guide crawl, the OpenCore Install Guide reports support for OpenCore 1.0.6, and the USB-creation pages were updated in March 2026. That matters because a lot of Catalina/OpenCore tutorials circulating online are materially older than the current guide. (dortania.github.io)
Two current corrections to many older tutorials are worth emphasizing:
Catalina itself is legacy now, and the final public release remains 10.15.7. If you want “latest Catalina,” that is the version to fetch, not an earlier 10.15.x build. (support.apple.com)
A useful mental model is:
Without the Apple installer, there is nothing to install. Without the OpenCore EFI, standard PC firmware usually cannot present the environment macOS expects. (support.apple.com)
From a troubleshooting standpoint, the most common build errors are:
config.plist not matching EFI contents,HfsPlus.efi or OpenRuntime.efi,For older non-UEFI hardware, Dortania still documents a LegacyBoot path using BootInstall_IA32.tool or BootInstall_X64.tool from Utilities/LegacyBoot. That is only for systems without UEFI support; most Catalina-capable Hackintosh builds should be UEFI and use the normal path. (dortania.github.io)
If your goal is a Hackintosh rather than an unsupported real Mac, review Apple’s software license terms before proceeding. Apple’s legal pages state that installation and use are governed by Apple software license agreements that you must accept before installing or using the software. (apple.com)
From a practical engineering perspective, this is a community-supported path rather than an Apple-supported deployment path, so reliability, updates, and compatibility validation are your responsibility. That conclusion follows from the fact that Apple documents only the generic macOS bootable installer process, while OpenCore configuration is provided by the community guide. (support.apple.com)
Use these best practices:
A concise “known-good” macOS-host workflow is:
softwareupdate --list-full-installers
softwareupdate --fetch-full-installer --full-installer-version 10.15.7
sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolume
diskutil list
sudo diskutil mount diskXs1After that, copy your prepared EFI to the mounted EFI partition and finish the hardware-specific OpenCore configuration. (dortania.github.io)
One correction to some of the sample answers: OpenCore Legacy Patcher (OCLP) is not the primary answer to a generic OpenCore Catalina USB for PC hardware. For a standard OpenCore-based Hackintosh workflow, the authoritative path remains the Dortania OpenCore Install Guide and Apple’s createinstallmedia process. (dortania.github.io)
Also, if you do not yet know your CPU generation, motherboard/chipset, GPU, audio codec, and network controller, you are not ready to finish the EFI correctly. The current guide explicitly branches by platform because the settings are not universal. (dortania.github.io)
Before booting, identify these items for the target machine:
Then follow the matching Dortania config.plist section for your platform and validate your EFI against the current guide structure. That is the step that determines whether the Catalina USB merely exists, or actually boots on your machine. (dortania.github.io)
The correct way to create an OpenCore Catalina USB is:
MyVolume. (dortania.github.io)createinstallmedia command. (support.apple.com)EFI containing the correct config.plist, ACPI, drivers, and kexts for your exact hardware. (dortania.github.io)If you want, I can give you the exact Catalina OpenCore USB recipe for your machine if you send: