- 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.