Step 1: Prepare Your Custom Logo
Step 2: Locate Your OpenCore EFI Partition
Step 3: Place the Hackbgrt Driver
Step 4: Place the Custom Logo
Step 5: Edit config.plist
Misc -> Boot:
UEFI -> Output:
Step 6: Save and Reboot
To understand the tool’s value, let’s break down the boot process:
Hackbgrt-1.5.1 injects itself as a driver (.efi) or kext (.kext) at step 2.5:
The result? The OS believes the vendor shipped a high-res logo, so it displays it cleanly without scaling artifacts. Hackbgrt-1.5.1
BGRT is a UEFI feature (introduced with ACPI 5.0) that stores a bitmap of the boot logo in memory. During early boot, the kernel or bootloader can display this logo, creating a seamless transition from firmware to OS.
The problem? Many UEFI implementations lock this table, and even when they don’t, changing the logo typically requires:
Hackbgrt avoids all of these by targeting the Linux kernel’s runtime memory after the BGRT has been loaded.
Users who dual-boot macOS and Windows can set a unified boot logo – for example, a neutral "Computer" symbol or a custom brand logo – so both OSes show the same clean boot screen.
The custom startup logo on your screen isn't just a picture—it’s the calling card for HackBGRT-1.5.1
, a specialized tool for UEFI systems that lets you swap out the standard Windows boot logo for anything you want.
Here is a short story about a user who took customizing their PC a bit too far. The Logo in the Machine
Leo lived for the "clean setup." His desk was cable-managed to within an inch of its life, and his desktop icons were strictly forbidden. But every morning, the same thing ruined his mood: the factory-default manufacturer logo staring at him during boot-up. It was a corporate blemish on his digital sanctuary. He found the solution in a folder named HackBGRT-1.5.1 . Following the official guide on Trio MDM , he dove into the BIOS to disable Secure Boot , the first step in reclaiming his screen. Step 1: Prepare Your Custom Logo
For the image, Leo didn’t want a logo. He wanted a warning. He spent hours in Paint, as the GitHub instructions
suggested, crafting a 24-bit BMP. It was a stylized, neon-blue eye that seemed to track movement. He ran the
, the command prompt flickered, and the files moved to the EFI partition. "Rebooting," Leo whispered.
The screen went black. Then, instead of the boring old logo, the neon eye snapped open. It was perfect. But as the system transitioned to the Windows lock screen, a bright flash lit up his room—a common glitch reported by other HackBGRT users
That night, Leo woke up to his PC turning on by itself. The neon eye wasn’t just a logo anymore; it was glowing with an intensity the software shouldn't have been capable of. He tried to mash the keys to enter the BIOS and undo the change, but his access keys didn't work —the eye just stared back, refusing to let him in.
He realized too late that when you hack the very first thing your computer sees, sometimes it decides what wants to see next. Learn more
Can no longer get into bios · Issue #52 · Metabolix/HackBGRT - GitHub
HackBGRT-1.5.1 is an open-source utility designed to customize the boot logo on UEFI-based Windows systems by modifying the Boot Graphics Resource Table (BGRT). Originally released in August 2018, version 1.5.1 remains a significant point in the tool's development history, specifically addressing configuration clarity and UEFI setup compatibility. Core Functionality Step 2: Locate Your OpenCore EFI Partition
Most computers store a manufacturer's logo in the UEFI firmware. Changing this permanently is difficult, so HackBGRT acts as a "shim". It runs a custom UEFI application during boot that overwrites the image in memory before Windows loads, allowing for a personalized startup experience. Key Updates in Version 1.5.1
This version focused on stability and ease of use following the introduction of major features in the 1.5.0 cycle.
UEFI Setup Fix: Addressed a specific exception that occurred on certain hardware when users attempted to boot directly into the UEFI (BIOS) setup from within the tool.
Config Clarity: Improved the default config.txt file to help users better understand how to customize their setup.
Legacy Support: While newer versions like 2.5.1 exist, 1.5.1 is noted for its "legacy" installation style, which some users still find more effective for specific hardware configurations. Essential Requirements
To use HackBGRT successfully, your system must meet these criteria:
UEFI Mode: The computer must be in UEFI mode, not Legacy BIOS.
Disabled Secure Boot: Secure Boot must be turned off, as it prevents unauthorized UEFI applications like HackBGRT from running.
Image Specifications: The custom logo must be a 24-bit BMP file named splash.bmp. Installation Workflow How to Change Windows 10's Boot Logo! (HackBGRT Tutorial)