If You Fail Boot Camp Can You Try Again
# Installing and using BootCamp utilities
So a neat feature of OpenCore is the ability to avoid the BIOS entirely and use Startup disk solely for multiboot. Problem comes in when we try to kick windows and have no way of setting the kick option back to macOS. That's where the BootCamp utilities come up in.
- Annotation: This guide will not comprehend the creation of the Windows installer, only the installation of BootCamp drivers.
- Example of Windows installer cosmos: Build a Bootable Windows ISO (opens new window)
- Reminder: Windows MUST be GPT/GUID based, OpenCore volition not boot legacy installs
- Note 2: Using BootCamp utilities from macOS will erase the EFI/Kicking/BOOTx64.efi file on your EFI, which is needed for booting OpenCore. And OpenCore itself does not support MBR based installs so the utility is useless to us
# Preparations
To start we'll need the post-obit:
- Windows already installed
- MUST be UEFI/GPT based
- Brigadier (opens new window)
- To download the BootCamp drivers
- SMBIOS injection enabled
- Equally the drivers have a SMBIOS check
- Setup LauncherOption
- Non required simply can aid alleviate headaches when Windows erases the BOOTx64.efi OpenCore uses
# Installation
To install, it's equally simple as grabbing Brigadier (opens new window) and running either Brigadier.bat
for Windows or Brigadier.control
for macOS. If the SMBIOS y'all're currently using either has BootCamp issues or desire to download for another SMBIOS, you can add -- model{SMBIOS}
to the end:
- Notation: Older versions of the BootCamp installer(6.0) do not support APFS, you'll demand to either choose a newer SMBIOS that would have it arranged(ie. iMac 19,1) or after installation update your bootcamp software. Meet below for more details on troubleshooting: Windows Startup Disk tin can't come across APFS drives
Adjacent y'all will find our bootcamp drivers under either:
- Windows:
- macOS:
macOS users volition side by side need to expand WindowsSupport.dmg and place it somewhere Windows tin get.
Next navigate to the bootcamp-{filename}\BootCamp
binder and run the Setup.exe:
Once all is finished, you lot now accept BootCamp switching! In that location should be a lilliputian BootCamp icon in you tray now that y'all can select which drive to kick to.
- Note: For those no needing the actress drivers BootCamp provides, you tin delete the following:
-
$WinPEDriver$
: DO NOT delete the folder itself, just the drivers within- Apple Wifi carte users will want to proceed the following:
-
$WinPEDriver$/BroadcomWireless
-
$WinPEDriver$/BroadcomBluetooth
-
$WinPEDriver$/AppleBluetoothBroadcom
-
- Apple Wifi carte users will want to proceed the following:
-
BootCamp/Drivers/...
- DO NOT delete
BootCamp/Drivers/Apple
- Apple Wifi menu users will desire to keep the following:
-
BootCamp/Drivers/Broadcom/BroadcomBluetooth
-
- DO NOT delete
-
# Troubleshooting
- Can't discover Windows/BootCamp bulldoze in picker
- "You can't change the startup disk to the selected disk" error
- Booting Windows results in BlueScreen or Linux crashes
- Booting Windows mistake:
OCB: StartImage failed - Already started
- Windows Startup Disk can't encounter APFS drives
# Tin can't find Windows/BootCamp drive in picker
So with OpenCore, we take to note that legacy Windows installs are not supported, only UEFI. Almost installs now are UEFI based simply those made past BootCamp Banana in macOS are legacy based, so you lot'll have to find other means to make an installer(Google's your friend). This besides means MasterBootRecord/Hybrid partitions are besides broken so you'll need to format the drive you lot want to install onto with DiskUtility.
Now to get onto troubleshooting:
- Make sure
Misc -> Security -> ScanPolicy
is prepare to0
to evidence all drives
If Windows and OpenCore'due south kick loaders are on the same drive, yous'll need to add a BlessOverride entry:
- Note: As of OpenCore 0.5.9, this no longer needs to exist specified. OpenCore should pick up on this entry automatically
# "You can't change the startup disk to the selected deejay" fault
This is commonly caused past either:
- 3rd Party NTFS Drivers(ie. Paragon)
- Irregular partition setup of the Windows bulldoze, specifically that the EFI is not the first sectionalization.
To fix the onetime, either disable or uninstall these tools.
To fix the latter, nosotros need to enable this quirk:
-
PlatformInfo -> Generic -> AdviseFeatures -> Truthful
# Booting Windows results in BlueScreen or Linux crashes
This is due to alignment problems, brand sure SyncRuntimePermissions
is enabled on firmwares supporting MATs. Check your logs whether your firmware supports Retention Attribute Tables(generally seen on 2022 firmwares and newer)
For Z390 and newer motherboards, you lot'll as well want to enable ProtectUefiServices
to ensure OpenCore'southward patches are applying correctly.
If your firmware is quite sometime(mostly 2013 and older), you'll want to enable ProtectMemoryRegions
.
Due to the variations of firmwares from vendor to vendor, you lot'll need to play around with the combination of these 3 quirks and see which works best.
Common Windows mistake code:
-
0xc000000d
# Booting Windows error: OCB: StartImage failed - Already started
This is due to OpenCore getting confused when trying to kick Windows and accidentally thinking it'due south booting OpenCore. This can be avoided past either motility Windows to it's ain drive or adding a custom drive path under BlessOverride. Come across Configuration.pdf (opens new window) and Can't find Windows/BootCamp drive in picker entry for more details.
# Windows Startup Disk can't meet APFS drives
- Outdated BootCamp drivers(generally ver 6.0 will come up with brigadier, BootCamp Utility in macOS provides newer version like ver 6.1). You can endeavour to alleviate these problems past either updating to the newest release with Apple's software updater or selecting a newer SMBIOS from brigadier(ie.
--model iMac19,1
) and when running brigadier.
For the latter, you'll need to run the following(supervene upon filename.msi
with the BootCamp installation msi):
Last Updated: 7/28/2021, iv:28:07 PM
Source: https://dortania.github.io/OpenCore-Post-Install/multiboot/bootcamp.html
0 Response to "If You Fail Boot Camp Can You Try Again"
Post a Comment