Skip to content
BootCampARM
Ko-fi (opens in a new tab)

Installation

There is no supported way to install Windows with BootCampARM today. This page is the boundary, not a setup guide.

Read this before anything else

BootCampARM has not installed Windows 11. The tools in the engineering tree are able to plan, and in some paths apply, changes to the internal SSD, a stub boot policy, and firmware files. That can make a Mac fail to boot macOS. Unpublished builds are not a recovery product.

If you do not already have the source tree and a reason to be developing it, stop here. Do not download a disk image, EFI binary, or "BootCampARM installer" from anywhere else and assume this project published it.

Current status

Verified, on one MacBook Pro 14-inch with M3 (2023): an alternative boot environment, m1n1, U-Boot/UEFI, the AArch64 shim, loading of a Microsoft EFI image, and UEFI firmware-service tracing.

Not verified: Windows Boot Manager initialization.

Not achieved: Windows PE, Windows Setup, a Windows desktop, drivers, or a second tested machine.

The progress page is the checklist. The compatibility page is the hardware rule.

What the orchestrator is designed to do

InstallOrchestrator in BootCampKit is shaped as seven stages. This is the intended shape of a future installer, not a procedure you should run:

  1. Probe the Mac and refuse the run when the compatibility check reports an error.
  2. Find the internal disk and read the partition map.
  3. Plan a stub volume, an EFI system partition, a media volume, and a Windows volume, leaving headroom on macOS.
  4. Apply that plan to the disk.
  5. Mount the new volumes and prepare the stub APFS container.
  6. Install the firmware payload and a recovery-side step that registers the m1n1 boot object.
  7. Stage Windows installation media.

A --dry-run flag exists on the command-line tool so a developer can print the plan without modifying the disk. Dry-run is still not a general-purpose installer, and a plan can be wrong.

The Windows partition size in the planner has a floor of 64 GB, which is the Windows 11 minimum the code records. The stub, EFI system partition, and media volume consume space on top of that. Those numbers are constants in the source. They are not a sizing recommendation for your Mac.

What this page will not tell you to run

This page deliberately omits diskutil invocations, kmutil invocations, security-policy changes, and firmware copy commands.

Those operations are how the experiment is built. Publishing them here as a tutorial would present risky partitioning and firmware changes as if they were a supported setup. They are not. People working in the engineering tree can read the source. Everyone else should wait until a result exists and a real release note says otherwise.

Do not disable security features on a Mac because a forum post says BootCampARM requires it. This project has not published that instruction.

If a Mac will not boot

This project does not provide a supported uninstaller for the public, even though the engineering tree contains an uninstall command. If a development machine no longer boots macOS, use Apple's own recovery paths: hold the power button for startup options, and if that is not enough, restore with Apple Configurator from another Mac. Keep a backup before any experiment that touches the internal drive. A Time Machine backup, or a full external clone, is the practical safety net. This website cannot restore a disk for you.