EfiGuard is a portable x64 UEFI bootkit that patches the Windows boot manager, boot loader and kernel at boot time in order to disable PatchGuard and Driver Signature Enforcement (DSE).
If you're just looking to try EfiGuard, skip to Usage.
-
Currently supports all EFI-compatible versions of Windows x64 ever released, from Vista SP1 to Windows 11.
-
Easy to use: can be booted from a USB stick or the Windows EFI partition via a loader that automatically finds and boots Windows. The driver can also be loaded and configured manually using either the UEFI shell or the loader.
-
Makes extensive use of the Zydis disassembler library for fast runtime instruction decoding to support more robust analysis than what is possible with signature matching, which often requires changes with new OS updates.
-
Works passively: the driver does not load or start the Windows boot manager. Instead it acts on a load of
bootmgfw.efiby the firmware boot manager via the boot selection menu or an EFI application such as the loader. If a non-Windows OS is booted, the driver will automatically unload itself. -
Supports four-stage patching for when
bootmgfw.efistartsbootmgr.efirather thanwinload.efi. This is the case when a WIM file is loaded to boot WinPE, Windows Setup or Windows Recovery mode. -
Graceful recovery: in case of patch failure, the driver will display error information and prompt to continue booting or to reboot by pressing ESC. This is true even up to the final kernel patch stage, because the last patch stage happens before
ExitBootServicesis called. Many UEFI Windows bootkits hookOslArchTransferToKernelwhich, while easy to find by pattern matching, is a function that executes in protected mode afterExitBootServices. This means no boot services are available to tell the user that something went wrong.
Simulated patch failure with error information
-
Debuggable: can output messages to a kernel debugger and to the screen (albeit buffered) during the kernel patching stage, and to a serial port or unbuffered to the screen during the boot manager and boot loader patching stages. If the driver is compiled with PDB debug information, it is possible to load the debug symbols at any point after HAL initialization by specifying the virtual DXE driver base and debugging it as you would a regular NT driver.
-
DSE bypasses: available as either a straightforward UPGDSED-style DSE disable at boot time or as a hook on the
SetVariable()EFI runtime service. The latter serves as an arbitrary kernel mode read/write backdoor that can be called from Windows usingNtSetSystemEnvironmentValueExand allows settingg_CiEnabled/g_CiOptionsto the desired value. A small DSEFix-style application namedEfiDSEFix.exeis provided that can be used to do this. It is also possible to leave DSE enabled and to disable only PatchGuard. The loader will use theSetVariablehook method by default, due to the fact that some anti-cheat and anti-virus programs do not understand the difference between cheats or malware and self-signed drivers in general and target the UPGDSED fix. -
Supports on-disk modified kernels and boot loaders by patching
ImgpValidateImageHashat every stage as well asImgpFilterValidationFailure, which may silently rat out some classes of violations to a TPM or the SI log file. -
Allows Secure Boot to work with Windows 7 (not a joke!). Windows 7 itself is oblivious to Secure Boot as it does not support it, or (officially) even booting without CSM. This is useful for people who want to use Windows 7 on a locked down device that requires WHQL Secure Boot. Wiki entry on how to get this to work here.
WinObjEx64 on Windows 7 with Secure Boot enabled
- EfiGuard can not disable Hypervisor-enforced Code Integrity (HVCI or HyperGuard) due to HVCI running at a greater privilege level. EfiGuard can coexist with HVCI and even successfully disables PatchGuard in the normal kernel, but this is not useful in practice because HVCI will catch what PatchGuard did previously. Both types of DSE bypass are rendered useless by HVCI: the boot time patch has no effect because the kernel defers to the secure kernel for integrity checks, and the
SetVariablehook will cause aSECURE_KERNEL_ERRORbugcheck if it is used to write tog_CiOptions. - Checked kernels are not supported due to the differences in PatchGuard and DSE initialization code caused by disabled optimizations and added asserts, as well as additional changes to PatchGuard in checked kernels. This should not be an issue as checked kernels are not generally useful without a kernel debugger attached, which disables PatchGuard.
There are two ways to use EfiGuard: booting the loader application, which will load the driver and start Windows for you, or installing the driver as a UEFI driver entry so it will be loaded automatically by the firmware.
Installing the driver can be preferable in some advanced configurations such as when multi-booting, but the loader is easiest to use and should work well in all configurations. See the table below for the most important differences between the two methods. If unsure, choose the loader application.
| Location | Installation | Skippable? | Which OS is booted? | |
|---|---|---|---|---|
| UEFI Driver Entry | Must be on ESP | Via UEFI Shell | ❌ | Same as before |
| Loader | Anywhere | Not needed | ✔️ | Windows |
Loader vs UEFI driver entry comparison
- Download EfiGuard and rename
EFI/Boot/Loader.efitobootx64.efi. - Place the files on a boot drive such as a FAT32 formatted USB stick (for physical machines) or an ISO/virtual disk (for VMs).
Assuming drive
X:, the paths for the two files should now beX:/EFI/Boot/{bootx64|EfiGuardDxe}.efi - Boot the machine from the drive you used in step 2. Most firmwares provide a boot menu to do this via F8/F10/F11/F12. If not, you will need to configure the BIOS to boot from the new drive.
- Windows should now boot, and you should see EfiGuard messages during boot.
- If you booted with the
SetVariablehook (the default), runEfiDSEFix.exe -dfrom an Administrator command prompt after boot to disable DSE, or runEfiDSEFix.exeto see the full list of options.
Note that you don't need to use a separate drive for the loader. If preferable, you can install EfiGuard on the ESP that Windows is already installed on. However, this is somewhat more complicated as you will need to add a UEFI boot entry for the loader.
To do this, mount the ESP at X: using mountvol X: /S and follow the steps above, but do not rename the loader and simply copy both files to X:/EFI/Boot. After that, you will need to manually add a UEFI boot entry from the UEFI Shell using bcfg boot addp 0 Loader.efi "EfiGuard", or alternatively using efibootmgr (Linux), EasyUEFI (Windows), or similar.
- Mount the ESP at
X:usingmountvol X: /S. - Copy
EfiGuardDxe.efitoX:/EFI/Boot/EfiGuardDxe.efi. - Boot to the UEFI Shell and add a UEFI driver entry:
bcfg driver add 0 EfiGuardDxe.efi "EfiGuardDxe". - Windows should now boot, and you should see EfiGuard messages during boot.
- If you booted with the
SetVariablehook (the default), runEfiDSEFix.exe -dfrom an Administrator command prompt after boot to disable DSE, or runEfiDSEFix.exeto see the full list of options.
Note: depending on your firmware, you may need to use "addp" in step 3 instead of "add". VirtualBox is known to require this, and possibly some motherboard firmwares do too.
Note: some very old or noncompliant firmwares may not support this method of installation at all. On these systems you will have no option but to use the loader instead.
EfiGuard requires EDK2 to build. If you don't have EDK2 installed, follow the steps in Getting Started with EDK2 first as the EDK2 build system is fairly complex to set up. This section assumes you have a workspace directory that your WORKSPACE environment variable points to, with a copy of EDK2 checked out in workspace/edk2. Supported compilers are MSVC, Clang, GCC and ICC.
- Clone the EfiGuard repository into
workspace/edk2/EfiGuardPkg. - Open a prompt or shell that sets up the environment variables for EDK2.
- Run
build -a X64 -t VS2019 -p EfiGuardPkg/EfiGuardPkg.dsc -b RELEASE, substituting your toolchain for VS2019.
This will produce EfiGuardDxe.efi and Loader.efi in workspace/Build/EfiGuard/RELEASE_VS2019/X64.
EfiDSEFix requires Visual Studio to build.
- Open
EfiGuard.slnand build the solution.
The output binary EfiDSEFix.exe will be in Application/EfiDSEFix/bin.
The Visual Studio solution also includes projects for EfiGuardDxe.efi and Loader.efi which can be used with VisualUefi, but these projects are not built by default as they will not link without additional code, and the build output will be inferior (bigger) than what EDK2 produces. Loader.efi will not link at all due to VisualUefi missing UefiBootManagerLib. These project files are thus meant as a development aid only and the EFI files should still be compiled with EDK2. To set up VisualUefi for this purpose, clone the repository into workspace/VisualUefi and open EfiGuard.sln.
While EfiGuard is a UEFI bootkit, it did not start out as one. EfiGuard was originally an on-disk patcher running on NT (similar to UPGDSED), intended to test the viability of a disassembler-based aproach, as opposed to using PDB symbols and version-specific signatures. PatchNtoskrnl.c still looks very much like this original design. Only after this approach proved successful, with no modifications to code needed in over a year of Windows updates, did UEFI come into the picture as a way to further improve capabilities and ease of use.
Some of the benefits provided by a bootkit approach include:
- No on-disk modifications to kernels or bootloaders needed.
- No need to modify the boot configuration store using
bcdedit. - No need to patch
ImgpValidateImageHash(although this is still optionally done). - Ironically, the use of a bootkit allows enabling Secure Boot, provided you own the Platform Key and are able to add your personal certificate to the
dbstore.
The initial incarnation of EfiGuard as a bootkit was an attempt to get dude719's UEFI-Bootkit to work with recent versions of Windows 10, because it had become dated and no longer works on the latest versions (like UPGDSED, often caused by version-sensitive pattern scans). While I did eventually get this to work, I was unsatisfied with the result mostly due to the choice of hooking OslArchTransferToKernel, which as noted above executes in protected mode and after ExitBootServices has been called. Apart from this, I was not satisfied with only being able to patch some versions of Windows 10; I wanted the bootkit to work on every EFI-compatible version of Windows x64 released to date. Because of this, I rewrote the bootkit from scratch with the following aims:
- To provide patch information at every stage of boot including the kernel patch itself.
- To support all EFI-compatible versions of Windows versions (at the time of writing).
- To enable lazy instantiation of the bootkit and optionally a kernel backdoor, achieved by EFI System Table hooks.
A big picture overview of the final EfiGuard boot flow is shown in the diagram above. For the individual component-specific hooks and patches, see EfiGuardDxe/PatchXxx.c in the source files. For driver initialization/unloading and the EFI Boot and Runtime Services hooks, see EfiGuardDxe.c.
- UPGDSED by hfiref0x and Fyyre
- Zydis by zyantific
- Uninformed articles on PatchGuard v1, v2 and v3 by Skywing
- UEFI-Bootkit by dude719
- ReactOS
EfiGuard is licensed under the GPLv3. Files in the EfiGuardDxe/Zydis submodule are licensed under the MIT license.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent