What has actually run.
Recorded 25 October 2026. The next honest milestone is a verified Windows Boot Manager initialization. There is no date on it.
Alternative Apple Silicon boot environmentVerified
Verified
The primary test machine has left the macOS kernel and entered an alternative boot environment built around m1n1.
Recorded on the MacBook Pro 14-inch, M3 (2023) used for this project. This is a boot-environment result. It is not a Windows installation, and it does not extend to other machines.
m1n1 / U-Boot execution on M3Verified
Verified
m1n1 and U-Boot have executed on that M3 test machine. U-Boot is the UEFI provider used for later EFI experiments.
Stage 2 on the EFI system partition is an m1n1 image that carries device trees and U-Boot. The diagnostic shim is started from U-Boot with bootefi. Verified for this machine only.
AArch64 EFI shim executionVerified
Verified
BootCampARM's AArch64 EFI shim reaches its entry point and prints to the UEFI console.
The current diagnostic image logs SHIM ENTRY 7 from efi_main. That line means the shim started. It does not mean Windows started.
Microsoft EFI image loadingVerified
Verified
The shim has loaded a Microsoft EFI image with the UEFI LoadImage service and identified it as an ARM64 PE binary.
The sanitized trace records LOAD IMAGE with status 0 (EFI_SUCCESS) and MACHINE AA64, the PE machine type for AArch64. Loading an image is not the same as the image completing its own initialization.
Instrumented Microsoft image executionObserved, under validation
Observed, under validation
A hook on the loaded image's entry point has observed that entry begin and return into the shim.
The trace includes ENTRY HOOKED, WIN ENTRY, STP OK, and RESUMED. Those lines are shim instrumentation. They are under validation and are not a verified Windows Boot Manager initialization.
UEFI firmware-service tracingVerified in current test environment
Verified in current test environment
Hooks on boot and runtime services have logged firmware calls made after the shim starts the loaded image.
In the current test environment the trace includes RT GetVariable, BS HandleProtocol, and AllocatePages fields (AP TYPE, AP IN, AP STATUS). AP STATUS 800000000000000E is an EFI error code, EFI_NOT_FOUND. This is firmware-service tracing, not Windows kernel output.
Windows Boot Manager initializationNot yet verified
Not yet verified
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.
Windows PE executionNot achieved
Not achieved
Windows Preinstallation Environment has not been shown running on the test machine.
No Windows PE desktop, command prompt, or setup shell has been demonstrated. Do not read the EFI trace as a PE log.
Windows SetupNot achieved
Not achieved
Windows Setup has not installed Windows 11 ARM64.
There is no completed installation, no booted Windows desktop, and no public installer. Partition roles exist in BootCampKit as a design. They have not produced an installed system.
General Apple Silicon compatibilityFuture objective
Future objective
Support across Apple Silicon generations is a long-term goal. It is not a current result.
The device database can name many models. Naming a model is hardware identification, not a boot test. M1, M2, M3, M4, and later families are not generally supported. Only one M3 MacBook Pro has a verified boot-environment result.
The console excerpt is on the homepage. Hardware limits are on the machine list.