Skip to content
BootCampARM

Your Mac.Another operating system.

An open engineering effort to bring Windows 11 ARM64 to Apple Silicon. Direct booting, without macOS running as the host. Windows has not booted yet.

The projectWhat has run

Shim sequence, M3 test machine

Animated sequence. An ASCII drawing of an Apple Silicon processor is crossed by a signal, then becomes a four-pane mark. A short EFI shim trace follows: SHIM ENTRY 7, image load, machine AA64. Windows Boot Manager initialization is not verified. There is no public installer. Windows booting has not been achieved.

The lines are the EFI shim, not a Windows console.

One 14-inch M3 MacBook Pro, 2023, has reached the shim.

m1n1 and U-Boot have executed there. The AArch64 shim loaded a Microsoft EFI image, machine AA64, and traced firmware services. Windows Boot Manager has not been shown to finish. There is no setup, no desktop, and no public installer.

The chain stops at the shim.

Boot chain on the M3 test machine. Filled marks have executed. The record stops at the shim.
  1. Apple iBoot

    Verified

    Apple's bootloader on the test machine. Not a BootCampARM component.

  2. m1n1

    Verified

    Stage 1 and stage 2 have executed on the primary M3 test machine.

  3. U-Boot / UEFI

    Verified

    U-Boot supplies the UEFI environment used to launch EFI applications.

  4. BootCampARM shim

    Verified

    The AArch64 shim runs, loads a Microsoft EFI image, and traces firmware services.

    The record stops here.

  5. Windows Boot Manager

    Not yet verified

    StartImage is attempted. Initialization has not been verified.

  6. Windows Loader

    Not achieved

    The Windows loader has not been shown to run.

  7. Windows 11 ARM64

    Not achieved

    No setup, desktop, or completed installation.

M3 / UEFI execution trace

Shim console lines. Not a Windows kernel log.

Show the log
SHIM ENTRY 7
LOAD IMAGE 0000000000000000
MACHINE 000000000000AA64
ENTRY HOOKED
TRACE ON
STARTING WINDOWS
WIN ENTRY
STP OK
RESUMED
RT GetVariable
BS HandleProtocol
AP TYPE 0000000000000002
AP IN 0000000010200000
AP STATUS 800000000000000E
AFTER ALLOC
Line notes
SHIM ENTRY 7
efi_main of the current diagnostic shim started and printed to the UEFI console.
LOAD IMAGE 0000000000000000
LoadImage returned 0, which is EFI_SUCCESS. The Microsoft EFI image was loaded. It had not yet been started.
MACHINE 000000000000AA64
PE machine field AA64 means IMAGE_FILE_MACHINE_ARM64. The loaded image is an AArch64 EFI binary.
ENTRY HOOKED
The shim patched the loaded image's entry so later lines come from instrumentation.
TRACE ON
Boot Services and Runtime Services hooks are installed. Later service names are those hooks firing.
STARTING WINDOWS
The shim's own label immediately before StartImage. It does not mean Windows Boot Manager finished starting.
WIN ENTRY
The hooked entry point began. Observed, and still under validation.
STP OK
The shim's entry hook passed its stack setup check and continued.
RESUMED
Control returned through the hook path. This is not a completed boot-manager handoff.
RT GetVariable
Runtime GetVariable was called. The variable name is omitted from this sanitized excerpt.
BS HandleProtocol
Boot Services HandleProtocol was called.
AP TYPE 0000000000000002
AllocatePages type 2 is the UEFI value AllocateAddress.
AP IN 0000000010200000
Address argument passed into AllocatePages. No claim is made about what resides there.
AP STATUS 800000000000000E
EFI status with the error bit set. The low code 0xE is EFI_NOT_FOUND. The allocate call did not succeed.
AFTER ALLOC
The AllocatePages hook returned and the shim continued tracing.

Experimental diagnostic trace from the BootCampARM EFI shim on the primary M3 test machine. These are shim console lines. This is not Windows kernel output, and it does not show Windows Boot Manager completing initialization.

Claims, one at a time

Full record

Not yet verified

Windows Boot Manager initialization

The shim calls StartImage on the loaded Microsoft image. A completed Windows Boot Manager initialization has not been verified.

There is no verified boot menu, BCD-driven handoff, or confirmation that bootmgfw.efi finished its own startup. STARTING WINDOWS in the trace is the shim's label for the StartImage call.

Nothing on this site is a download.