Windows-GPU-UNLOCK README

项目的 README,来自 github.com/windows-GPU-UNLOCK/Windows-GPU-UNLOCK。合并为一个 markdown 文件:README.md。

Windows GPU UNLOCK

English | 한국어

Contributor tooling: entry-point inventory and cleanup proposal.

Experimental UEFI GPU unlock and direct Windows handoff, expanded through community contributions.

Join our Discord community View compatibility and supported configurations Contribute research and improvements

Start here

Want to find out about your PC or help report compatibility? Start with a Windows-only check. You do not need to attempt an unlock.

Your goal What to do
I'm new. What information should I report? Beginner guide: check your PC and share results
I already have capture files from my PC Check those files offline
I want to know which setups have worked Reported setups and their limits
I'm ready to investigate an unlock Check the exact configuration and boot route first

Quick check · No reboot

Download Code → Download ZIP, extract it, and open PowerShell in the extracted project folder. With Python 3.10+ installed, run:

python -I .\tools\collect_compatibility.py

This prints hardware/driver information; it does not unlock, change settings or upload anything. not-assessed and can_unlock: false are normal. Remove personal details from the output, then paste the reviewed text into a compatibility report. Do not attach firmware or raw dumps.

[!TIP] No Python or terminal experience? The step-by-step guide explains how to start, what the result means and what to share. You can also enter hardware details manually; no EFI test is required to report findings.

Community

Join our Discord community for conversations, work-in-progress findings, and collaborative development and research. Keep substantial research results, reproducible test reports, code reviews, and project decisions in GitHub issues and pull requests so everyone can find and review them. Please read the community rules.

GPU support

Success reports apply to specific cards and systems, not every card of the same GPU model. Check the linked motherboard, BIOS and card requirements before building.

GPU Current status Details
RTX 3060 12GB (GA104 / GA106) Hardware success reported; headless USB only GA104 · GA106
RTX 3060 Ti 8GB (24c9 / GA104) Contributor LOCAL USB success reported; experimental automatic profile Exact conditions
RTX 3070 8GB (2484 / GA104) Contributor LOCAL USB success reported; experimental automatic profile Exact conditions
RTX 3070 Ti 8GB Hardware success reported; internal headless Supported configuration
RTX 3080 12GB (220a / GA102) Contributor USB success; narrow experimental LOCAL admission, with reported DP recovery limitation Exact setup and evidence
Other RTX 3080 / RTX 3080 Ti Private/research success reports; not general upstream profile support Setup audit
RTX 3090 FE 24GB Hardware success recorded; internal headless; original B650M AMD-retained multi-display experiment Supported configuration
RTX 3090 Ti 24GB Hardware success reported; route depends on exact system X870 USB · B660M internal

The compatibility guide lists exact build profiles and distinguishes maintainer tests from contributor reports. Results concern their recorded builds; later main-branch hardening has host/build checks, not a new physical boot or recovery test.

The latest tagged release, v0.3.1, is a source-only pre-release. This source tree has changes beyond that tag, including the USB route and X870 profile; those are not a newly published release. Build locally with your own partition GUIDs. Firmware assets and private, partition-specific EFI binaries are not bundled.

All reported working setups and profile coverage · Complete issue audit.

Choose the correct boot path

Path Display and input Instructions
Internal headless B650M/3090 FE or B660M/3070 Ti / 3090 Ti profile; monitors on RTX; display temporarily removed; no T/U/Enter Internal headless guide
Headless USB Reported RTX 3060 / 3090 Ti configurations; profile-specific wrapper and child on a FAT32 USB stick Headless USB guide
Internal AMD-display manual / Auto Original B650M profile, motherboard/iGPU display preserved; manual variant requires U Existing internal guide
Legacy USB manual Original AMD/iGPU display profile; U once, then Boot Override to Windows without reset Legacy USB guide

For the original B650M machine with one motherboard display and two RTX displays, see the opt-in AMD-retained experiment. One manual boot succeeded on its recorded private build; automatic boot and the integrated revision still require their own physical verification.

X870, B660-PLUS and H610M are not wired into Configure.ps1 or Headless.ps1; use the USB guide. USB packages can also be built for the first two profiles, but their recorded internal boots do not validate those USB routes. The legacy USB EFI retains its AMD display requirement. BIOS priority USB → Windows alone does not implement direct handoff.

Internal headless quick start

Advanced · Exact-profile internal headless setup

This example is for the default B650M / RTX 3090 FE profile. For B660M, select -HardwareProfile b660m-3070ti in both configuration and build as described in compatibility. X870 uses the separate USB route.

Read the full guide and recovery procedure before changing boot settings. Use the exact supported hardware, Secure Boot disabled, a fully decrypted Windows C: with BitLocker protection off, and a connected keyboard. The tools do not disable encryption.

Preserve the existing Windows ESP and recovery partition. Prepare a separate GPT FAT32 EFI System Partition of at least 1 GiB, with a letter such as U:. Tools do not create, shrink, delete or format partitions. An ordinary FAT32 data partition alone is not the required ESP.

You need Python 3.9+, clang/lld-link 20.1.8, the pinned repository dependencies and five locally obtained firmware assets. Host integration tests additionally need MSVC/Windows SDK and private fixtures.

From an administrator PowerShell in the repository root:

# Replace the GUID and tool paths with your own values.
.\internal-boot\Configure.ps1 -UnlockDriveLetter U `
  -WindowsEspGuid 'YOUR-WINDOWS-ESP-GUID'
.\research\headless\build-unlock.ps1 `
  -Clang 'C:\TOOLS\LLVM20\bin\clang.exe' `
  -LldLink 'C:\TOOLS\LLVM20\bin\lld-link.exe'

# Stage and append a separate F8 test entry; retain existing boot priority.
.\internal-boot\Headless.ps1 -Assets '.\assets' -Register

Without an action switch, Headless.ps1 -Assets '.\assets' only stages files. Configuration and build do not register a boot entry.

  1. Save work and fully power off. On the tested ASUS firmware, select F8 → GPU Headless UNLOCK - EXPERIMENTAL.

  2. Wait without T, U or Enter. Initial Esc within five seconds skips release and unlock and boots Windows directly.

  3. The screen becomes black while the RTX GOP is removed. The child attempts once and the wrapper starts Windows directly. Do not reset between unlock and Windows. Confirm display recovery and measure.

  4. Only after that F8 test succeeds, enable default automatic boot:

    .\internal-boot\Headless.ps1 -EnableAutomatic -ConfirmedSuccess
    

That explicit action places headless first and Windows Boot Manager second and disables Windows Fast Startup. Test registration alone does not. Publishing this release does not change the research PC's current default boot selection.

The two Esc windows differ: initial wrapper Esc boots Windows without release; the later three-second child Esc window is after release and cancels into a stop. It does not restore the display or continue to Windows. On failure or if Windows does not return, fully power off and choose F8 → Windows Boot Manager.

.\internal-boot\Headless.ps1 -RestoreWindowsFirst

Windows-first recovery is independent of experimental EFI/build artifacts and still works without saved state. Restoring the prior Fast Startup setting needs that state; retain it and backups. Recovery details.

Original B650M results and limits

The original B650M hardware run's successful child reported SS0 0x88888888, SS1 0x8, BME disabled, zero remaining mappings, completed cleanup and one FLR. The wrapper verified the released topology before Windows entry. Windows display recovery was observed by the operator.

CUDA 12.6 / cuBLAS 12.6, 4096 × 4096 Three-run median
FP32 pedantic 22.85 TFLOPS
FP16 Tensor / FP32 accumulation 124.97 TFLOPS
BF16 Tensor / FP32 accumulation 128.93 TFLOPS

Future runs of the benchmark tool also measure TF32 separately. The historical measurements above predate that addition and have no TF32 result.

There is no contemporary controlled locked baseline for this headless boot, so these values do not establish an unlock percentage. They do not establish game or ComfyUI gains, long-term stability, sleep/hibernate resume or repeated automatic cold-boot reliability. Sanitized measurements and earlier results describe separate experiments.

For the other machines' measurements, see B660M Profile 2, X870 USB evidence and B660-PLUS / 3060 USB evidence (controlled locked baseline: FP16 1.88–1.92×, BF16 1.92–1.95×, TF32 1.93–1.94× over two boots). Those results are tied to their reported builds; a later successful build or host test does not extend the physical test record.

Check existing captures

An offline compatibility checker explains whether existing probe captures fit the automatic local-profile route and what is missing. It needs only Python 3.10+ and runs no probe or unlock:

python -I research/profile/check-compatibility.py "D:\RTX3090-UNLOCK"

A candidate still needs profile generation, host tests and hardware validation. An out-of-scope result does not rule out an exact existing fixed profile. Use --json for a reviewed-shareable report with limited model/topology observations; paste it into the optional offline report field in a compatibility issue. The guide also covers comparing two reports to investigate common differences.

Implementation and boundaries

The GPU family layer shares reviewed GA102/GA104/GA106 traits and identical firmware templates, while exact card/platform pins remain separate. Existing profile names and support scope are unchanged.

Headless is a separate compile-time profile. Exact GPU/PROM/PCI state, firmware driver code, ownership, cold state, immutable selectors and cleanup checks remain. The child logs to files only and rejects physical GOP reappearance or changed console/input interfaces. Ordinary builds retain their AMD display guards. Do not remove checks or substitute a PROM hash to force another machine through.

Path Purpose
internal-boot/, research/headless/ Internal/headless source, local build, installation and host tests
unlock/, release/ Preserved legacy USB manual implementation and historical artifacts
benchmark/, evidence/ Measurement tools and selected public evidence
docs/ Compatibility, assets, boot guides and limitations

No VBIOS flashing or Windows driver replacement is part of the procedure. Driver 617.14 was unchanged in the documented run. Host mock tests do not add hardware support. New systems require compatibility reporting and portability validation. A machine inside the hardware-proven envelope can build and test its own local profile with the new-machine pipeline. This experimental workflow inventories NVIDIA display devices, but deep capture is limited to one reviewed RTX 3090 / 3090 Ti, RTX 3060 12GB, RTX 3060 Ti 24c9 or RTX 3070 2484 identity in the reviewed PCI/BAR state. The generic probe also records optional parent PCI information when its observation conditions match, helping investigate motherboard differences. This does not enable an unlock or correct PCI state. A generated local profile does not add another verified machine profile. USB write builds require all 22 host jobs, including fresh PCI identity checks, input policy and the topology-specific complete driver-release replay, and unchanged profile, fixtures and build inputs; hardware validation is still required. Within this envelope the generic probe discovers the bus automatically and the generated profile pins it per machine. An optional -TargetBus constrains discovery and resumed captures. LOCAL discovery also accepts captured PNP0A03/PNP0A08 root identities and up to 16 PCI path nodes, pinning the complete ancestry and checking the exact PCI parent. This experimental bridge-chain support still requires per-machine validation. LOCAL discovery and generation can pin a unique target on any 16-bit PCI segment. Prepare, release and PCI access must match that segment as well as the captured bus; nonzero-segment operation is experimental and still needs physical validation. Single-RTX systems may have no iGPU or separate EDID driver on the non-aggregate path. Without a separate EDID driver, non-aggregate LOCAL generation/replay accepts one to four unique NVIDIA display children. Three/four-child paths remain experimental; four-child coverage is host-only. EDID-driver and aggregate generation retain a two-child limit. Recognized AMI aggregate consoles with one or two display children can generate an experimental local profile and require their own prepare/release replay; this does not establish another hardware success. Multiple NVIDIA GPUs are not generated. Staging the unlock package needs -StageUnlock.

License and attribution

The port and reused core are GPL-2.0-only; EDK2 and separately attributed components retain their licenses. Based on rough2515-hub/rtx3080-unlock-public and Zagitta/gpu-unlock. Preserve LICENSE, third-party notices and change history. NVIDIA firmware, PROM/BIOS images, drivers and CUDA DLLs are not redistributed in this source release.

Windows-GPU-UNLOCK (windows-GPU-UNLOCK/Windows-GPU-UNLOCK)

正在搜索数据库…

这是什么?Windows GPU UNLOCK 是一个实验性的 UEFI 阶段工具,它能让 NVIDIA RTX 显卡摆脱最初的锁定 PCI/BAR 状态,无需重置循环,直接把控制权交给 Windows,而不是走常规的启动和重置流程。它是对早期 RTX3080 解锁项目的移植,并通过社区测试扩展到了其他 RTX 显卡。
这是我显卡的驱动或固件改装吗?都不是。它是一个自定义的 UEFI 启动阶段(基于 EDK2 构建),在 Windows 加载之前运行,执行解锁流程,然后衔接到现有的 Windows 启动管理器;它从不刷写 VBIOS,也不替换任何 Windows 驱动。
我该怎么构建和运行它?在仓库根目录下,以管理员身份打开 PowerShell,使用对应的 -HardwareProfile(例如 b660m-3070ti)运行 Configure.ps1 和 Headless.ps1,然后通过专用的 F8 启动菜单项先测试一次;只有测试成功之后,才把它注册为默认启动路径。
构建之前我需要准备什么?Python 3.9+、clang/lld-link 20.1.8、固定版本的仓库依赖项,以及五个需要你自行获取的固件资源(不随附提供);主机集成测试还需要 MSVC 和 Windows SDK。
这能用在任何 RTX 显卡和主板上吗?不能。硬件成功只在特定的显卡和主板组合上得到验证(RTX 3060、3070 Ti、3090 FE、3090 Ti 搭配特定配置),而且在一块显卡上成功,并不保证同型号的另一块也能成功。X870、B660-PLUS 和 H610M 等主板尚未接入自动化脚本。
这只能在 Windows 上运行吗?是的。它专门用于在 Windows 启动时解锁显卡,要求禁用安全启动、完全关闭 BitLocker,并且需要在 Windows 所在的机器上设置一个专用的 FAT32 EFI 系统分区。
如果解锁启动失败或屏幕一直黑屏,会怎样?关机后选择 F8,再选择 Windows 启动管理器。这条恢复路径独立于实验版本,即使没有任何已保存的状态也能使用。不过,要还原原来的快速启动设置,你需要先备好备份。
使用它会分发 NVIDIA 的固件或驱动吗?不会。源码发布版本中不包含 NVIDIA 的固件、PROM/BIOS 镜像、驱动程序和 CUDA DLL,你必须自行获取这五个所需的固件资源。
解锁后实际能看到多大的性能提升?在一次受控的双启动对比中,于一台测试机器上,相比锁定的基线,FP16 约提升 1.88-1.95x,BF16 约提升 1.92-1.95x。但这些数字只适用于该特定构建,不保证能在其他系统或游戏、ComfyUI 等工作负载上复现。
有没有我可以直接下载的稳定版本?最新的带标签版本 v0.3.1 仅提供源码,并且是预发布版本。USB 路线和 X870 配置等更新的工作只存在于该标签之后的源码树中,因此你需要自行构建。
大小
3 MB
星标
2.3K
更新
提交Nov 15
时长
29天
提交 · 90 天