One line from the original author, "I don't run Windows", got a Korean's port 17 days and 1,878 stars
What it is An open source tool that, at boot, runs a UEFI app to lift the half-rate AI compute limit on RTX 30-series GPUs and then goes straight into Windows. It's a Windows port of the Linux gpu-unlock.
Why it took off The original gpu-unlock went viral, and its author said outright they don't do Windows and linked this port in the FAQ. Many 3090 users running ComfyUI and local LLMs on Windows wanted the free speedup, and HN, media, and Reddit all cited it as the "Windows version".
CHow you could follow it Don't build this one. Learn the playbook: watch for a freshly viral project that supports only one platform, port the missing platform within a week to lower the barrier as far as possible, then get the upstream author to link you in their FAQ.
- Data (updated daily) · Repo created 2026-10-20 · 1,978 stars · 7 days +570
GitHub · stars Data 2026-10-24 → 2026-11-08 (16 days, 16 observations). Points before 10-28 come from deeply / archive backfill, not every day has one
Windows-GPU-UNLOCK moved a viral GPU unlock tool from Linux to Windows: at boot, a UEFI app unlocks the AI compute on RTX 30-series cards, then boots straight into Windows. It did almost no promotion itself, and nearly all its stars came over from the original. The original author wrote in the README that they don't do Windows and linked this project, so it became the "Windows version" everyone talks about. The playbook is learnable, but the slot is already being contested. Below: what it is, where the stars came from, why it got caught so fast, and what you should take from it.
A 3090 that boots straight into the BitLocker recovery screen
In late October, someone posted on r/nvidia titled "RTX 3090 tensor unlock on Windows: got it to actually boot (BitLocker was the problem)". Following a guide, they unlocked a 3090, and then Windows kept asking for the BitLocker recovery key on every boot. After digging, they realized: disabling Secure Boot and booting from an unsigned USB stick changed the TPM measurements, so Windows thought someone had tampered with the boot chain. The post named the tool they used: "The project is Windows-GPU-UNLOCK".
The post shows two things. First, a real group of people will turn off Secure Boot and decrypt their system drive just to make an old GPU run a bit faster. Second, the barrier is high, with lots of pitfalls to step through. The project blew up because of the first point; it lost ground to followers because of the second.
What it is
On GeForce cards, the FP16/BF16 tensor path that accumulates at 32 bits for AI compute is artificially capped at half speed by NVIDIA, with full speed reserved for professional cards. In Oct 18, Zagitta released gpu-unlock, a Linux kernel module that unlocks that path to full speed on RTX 30-series cards. According to tests cited by Notebookcheck, the 3090's BF16 went from 77.5 TFLOPS to 129.6 TFLOPS.
But the 3090 is the second-hand card most used in the local AI community, and many people run ComfyUI and local LLMs on Windows. Windows-GPU-UNLOCK is a port built for them:
- Unlock at boot, then straight into Windows without a reset: a UEFI program unlocks the card first, then hands control to the Windows boot manager. It doesn't flash the VBIOS or swap the official driver.
- Every result says which machine it stops at: the compatibility table lists each "GPU + motherboard + BIOS" combination separately, distinguishing what the maintainer tested from what others reported. For the 3090 FE machine, which has no pre-unlock baseline, the docs only state the measured numbers (FP16 124.97, BF16 128.93 TFLOPS) and don't claim a percentage gain.
- The author is Korean: the README comes in English, Chinese, and Korean, and includes a Korean guide to "going into Windows without a reset".
How much faster it actually is depends on the workload. Per community tests, ComfyUI image generation gets 47%–59% faster, the prompt-reading (prefill) stage of LLMs gets 15%–62% faster, and token-by-token output barely changes.
The stars rose along with the original
| Date | This project's daily star gain that day | The original gpu-unlock's daily star gain that day | What happened |
|---|---|---|---|
| 10-20 | — | — | Repo created, first machine verified successfully |
| 10-24 | Cumulative 39 | — | Zagitta's HN post (353 points), with someone in the comments linking it; Notebookcheck mentioned "an experimental Windows port" |
| 10-26 | +132 | +3,745 | TechTimes' headline was literally "Free Tool Fixes Firmware Cap on Windows", naming the author impacifist |
| 10-27 | +466 | +3,283 | Single-day peak |
| 10-28 | +405 | — | Afterglow |
| 10-29 ~ 11-03 | +55 ~ +92 | — | Flat |
| 11-04 / 11-05 | +121 / +154 | +976 / +1,063 | The original's second wave, and it rose too |
| 11-06 | +77 | +595 | 1,878 stars total, 205 forks |
(GitHub daily stars, 10-24 ~ 11-06.)
The peaks on both repos fell on the same days; when the original rose, this one rose. Traffic flowed in from these places:
- The original README's FAQ: "I don't run windows and don't plan to maintain it but github.com/impacifist/Windows-GPU-UNLOCK has built a port, YMMV". The original author personally pointed people here. This is the most important one.
- HN: under Zagitta's post, a comment reads "There's also a Windows version" with a link.
- Media mentions in passing: Notebookcheck 10-24, TechTimes 10-26, WindowsForum. Not one piece was about it specifically.
- Reddit's local AI scene: r/LocalLLaMA's "Amazing free 3090 speedup hack" thread linked it with the line "Can't vouch for its safety"; r/StableDiffusion, r/comfyui, and r/nvidia also had discussions.
- Korean communities: On CLIEN, someone posted "요즘 유행한다는 3090, 4090 gpu unlock을 해봤습니다" (I tried the trendy 3090 with 4090 GPU unlock), and DCInside's AI board has posts too. 10-30 The Korean blog tau-home wrote a full piece, with figures from X user @lucian__03's real-world tests.
I couldn't find whether the author promoted it personally.
224 issues, mostly people reporting their own hardware
The README's first step isn't unlocking. It's "run a read-only detection script first": download and unzip, then run collect_compatibility.py in PowerShell. It only prints hardware and driver info, changes no settings, and uploads nothing. Then paste the result into a compatibility issue template. The docs specifically say "can_unlock: false is normal", so people aren't afraid to submit.
The open issue count rose from 10-28 to 11-06 (rising.dev), from 76 to 224, mostly hardware reports. Casual visitors became contributors in two minutes, and a repo full of issues looks busy and alive. This trick works on any project that depends on the community to test compatibility.
Still, only a minority actually got it working. Many reports say "installed but no speedup" or "it shut down on boot". Stars far outnumber people actually using it.
First to build it, didn't hold it
About a week before nv-uefi-unlocker appeared, it was the only Windows version with real hardware evidence. The cost was the barrier: you had to create a separate EFI system partition, disable BitLocker and Secure Boot, install clang 20 yourself to compile, and source the firmware yourself.
Oct 26, physicsdolphin/nv-uefi-unlocker was created. It's also Windows UEFI, but boots from a USB stick, auto-selects the path by chip family, covers the 20, 30, and 40 series, and supports laptops. Nov 1, Tom's Hardware wrote it up specifically, with "on Windows" in the headline; this project got a passing mention in that piece as an "earlier Windows EFI tool".
| Name | Repo created | Stars (11-06) | How it differs |
|---|---|---|---|
| Zagitta/gpu-unlock | 10-18 | 17,130 | Upstream original, Linux kernel module, no Windows |
| JustAResearcher/gpu-unlock-ada | 10-23 | 4,786 | 40 series, Linux |
| physicsdolphin/nv-uefi-unlocker | 10-26 | 1,832 | USB boot, 20/30/40 series plus laptops, covered by Tom's Hardware |
| nlzy/turing-unlock, KohakUnlock | 10-24 / 10-25 | 346 / 388 | 20 series, Linux |
nv-uefi-unlocker gained 411 stars in one day in Nov 2, then its daily gain dropped to 370, 236, 129, 106,11-06, and 1,832 stars, only 46 behind this project. At the last two days' pace, it will pass this one within days. SEO sites like gpu-unlock.net and gpuunlock.com have also popped up, with Chinese "Windows support" pages and compatibility tables that directly cite this project's data. There's also a batch of repos riding the "unlock" name that have nothing to do with this, and some may be phishing.
There's another risk: NVIDIA could close this path at any time through a driver or firmware update. If they do, this whole wave of projects stalls.
If it were you
One-line verdict: don't chase this project. The Windows-version slot is already split between two projects, and the window was only a week or two. What's worth taking is the playbook: when an upstream project blows up and is missing a platform, be the fastest to fill that platform.
Who it's for: developers with systems, driver, and cross-platform porting skills who can, within days of an upstream going viral, ship a version that works and has real hardware evidence.
Who it's not for: anyone who hasn't worked with UEFI, firmware, or kernels. In projects like this, a bad release is worse than none, because other people's machines won't boot.
How to do it:
- Watch the GitHub projects gaining stars fastest, looking for ones that are "Linux only", "macOS only", "Python only", or "English only", with issue threads full of people asking "what about Windows?".
- Within a week, ship a working port, even if it only supports one configuration, and state clearly which machine it was tested on and what the results were.
- Lower the barrier to the floor on day one. That's where this project lost: once a competitor with USB boot and wider coverage showed up, media moved on.
- Borrow its read-only detection script plus issue template, so onlookers become contributors without effort.
How to get users: reply in the upstream's issue threads to the "what about Windows?" questions, and politely ask the upstream author to link you in their FAQ. That's the biggest traffic source. Then post hands-on test reports with "on Windows" in the title in the upstream's HN thread comments and the matching subreddits; and email the media already covering the original, since they need a follow-up.
Before the peak: 3 to 7 days after the upstream blew up. This project was 2 days in, the rival was 8 days in. After two weeks, positions were basically set.
Signs you misread it: a week after your port ships, the upstream author isn't linking it, HN and Reddit aren't sharing it, and stars aren't climbing with the upstream spikes. That means nobody on this platform wants it, or someone already claimed the slot.
Research notes: competitor table, acquisition evidence, full research report
- Competitors
Name Where Launched Scale How it differs from this one Zagitta/gpu-unlock Open source 2026-10-18 17,130 stars Upstream original, Linux kernel module, official team doesn't do Windows physicsdolphin/nv-uefi-unlocker Open source 2026-10-26 1,832 stars, covered by Tom's Hardware/Wccftech Also Windows UEFI, but boots from a USB stick and routes by chip family, covering 20/30/40 and laptops, with a lower barrier to entry JustAResearcher/gpu-unlock-ada Open source 2026-10-23 4,786 stars Targets RTX 40 (Ada), Linux only rough2515-hub/rtx3080-unlock-public Open source 2026-10 Small One of the upstreams, only unlocks a single MSI 3080 via UEFI USB nlzy/turing-unlock / KohakUnlock Open source 2026-10-24/25 346 / 388 stars Targets 20 Turing, Linux TOTORONG/AD103_win_unlocker, CMP mining card Windows unlocker Other Earlier Small niche An earlier Windows EFI unlock precedent, aimed at mining cards or 4080 NVIDIA pro cards (RTX A series) Big-company features — — Official full speed is only unlocked on pro cards; GeForce is artificially throttled - Where users come from
- Verified Upstream README link-out: Zagitta README FAQ: "I don't run windows…impacifist/Windows-GPU-UNLOCK has built a port"
- Verified HN: In the comments on Zagitta's HN post (10-24,353 points), someone posted "There's also a Windows version" with this repo's link
- Verified Tech media mentions in passing: Notebookcheck 10-24, TechTimes 10-26 name impacifist, WindowsForum
- Verified Reddit local-AI circles: r/LocalLLaMA, r/nvidia, r/gpu, r/tech_x, r/StableDiffusion threads link it directly
- Verified Korean and Chinese communities: CLIEN, DCInside, Naver blogs, tau-home (10-30); HKEPC on Threads with 2.6K views; Chinese X posts
- Inferred YouTube Shorts and explainer videos: "Unlock your RTX 3090 without flashing VBIOS" Shorts link to the repo; whether the creator made them is unverified
- Verified Discord plus crowdsourced compatibility: The README homepage puts a read-only detection script and issue templates up front; most of the 224 issues are hardware reports
Windows-GPU-UNLOCK (windows-GPU-UNLOCK/Windows-GPU-UNLOCK) research report
Date: 2026-11-06 · Channel: GitHub · Original repo name impacifist/Windows-GPU-UNLOCK (later moved to a same-named org; rising.dev has records)
One line
It's the Windows UEFI port of Zagitta/gpu-unlock (which unlocks GeForce RTX 30 FP16/BF16 tensor FP32 accumulation from half speed to full, originally Linux-only): a UEFI program runs at boot to unlock the GPU, then hands off to Windows without a reset, no VBIOS flashing, no driver swap. The author is Korean, with READMEs and docs in English, Korean, and a third language.
Verdict
It didn't generate its own momentum; it rode the wave of Zagitta/gpu-unlock (created 2026-10-18, now 17,130 stars). The original only supported Linux, while many of the 3090 users run ComfyUI or local LLMs on Windows, and they wanted a Windows version most. impacifist had a Windows version that successfully booted a machine two days before the original blew up (10-20). Afterward, Zagitta's README FAQ, the HN comments, Notebookcheck, TechTimes, and Reddit threads all cited it as the "Windows version," and traffic flowed over on the original's heat. The differentiator is "Windows + boot straight into the OS without a reset," which is why it took off. But the window is short: physicsdolphin/nv-uefi-unlocker, created 10-26, boots from a USB stick and covers the 20/30/40 series. It already got Tom's Hardware coverage, and its stars (1,832) are close to catching up.
Data (github repo_day, 2026-10-24 ~ 11-06)
- 17 days, 1,878 stars, 205 forks; +7 in the last 631 days, +1 in the last 77 days.
- Peak single-day 10-27 +466 (10-26 217 → 10-27 683 → 10-28 1,088), then another wave of +60~90,11-04/05 per day (+121, +154).
- Timing matches the original exactly: Zagitta/gpu-unlock 10-25 +1,458, 10-26 +3,745, 10-27 +3,283; 11-04 +976, 11-05 +1,063. The peaks on both sides fall on the same days, so its traffic came from the original.
- rising.dev 11-06 snapshot: 1,907 stars, 224 open issues (10-28 is 76), 25 merged PRs, 30 commits in 118 days. Most issues are hardware compatibility reports users filed from the template.
Why it could take off
- The original blew up, and Windows was the gap it left. Zagitta said on HN, "the exploits aren't my ideas…inspired by the CMP90/50 windows unlocks," and the README FAQ says: "I don't run windows and don't plan to maintain it but github.com/impacifist/Windows-GPU-UNLOCK has built a port, YMMV" (from the Zagitta README excerpt Brave surfaced). The original author linked it himself. This is the single most important source.
- Media mentioned it in passing when covering the original. Notebookcheck 10-24: "a separate experimental Windows port has demonstrated an unlocked RTX 3090 successfully booting into Windows"; TechTimes 10-26 headline "Free Tool Fixes Firmware Cap on Windows" names the "Windows-GPU-UNLOCK project, developed by GitHub user impacifist"; WindowsForum 10-24 covered it too; Gadgets Now wrote "four GitHub projects, each covering one class of card."
- HN: Zagitta's post (10-24,353 points, 85 comments) has someone replying "There's also a Windows version: github.com/impacifist/Windows-GPU-UNLOCK" (HN Algolia).
- Reddit's local-AI scene: In r/LocalLLaMA's "Amazing free 3090 speedup hack" thread, someone linked it ("Can't vouch for its safety"); in r/nvidia and r/gpu, "RTX 3090 tensor unlock on Windows: got it to actually boot (BitLocker was the problem)" states outright "The project is Windows-GPU-UNLOCK"; r/tech_x "Unlock your Windows GPU (3050…3090)"; r/StableDiffusion, r/comfyui, and r/LocalLLM all have discussions.
- Korean and Chinese communities: CLIEN "요즘 유행한다는 3090, 4090 gpu unlock을 해봤습니다", the DCInside AI gallery, Naver blogs, tau-home.com (10-30, with images from X user @lucian__03); HKEPC reposts on Threads (2.6K views); a trendshift page captured a Chinese X post listing "3090 Windows."
- YouTube and short video: "Unlock your RTX 3090 without flashing VBIOS" (Shorts, linking the repo) and the explainer "Unlocking RTX 3090 Performance on Windows"; a Digital Spaceport-style 4×3090 test video covers this whole unlock wave.
- Why users show up: 3090 is the most mainstream used card in local-AI circles, and "the same card gets 1.5~2× faster for free" (BF16 77.5→129.6 TFLOPS, Notebookcheck citing the original issue; this repo's B660-PLUS/3060 baseline shows 1.88~1.95×). It needs no BIOS flash and no driver changes, so the risk looks acceptable. Real gains depend on workload: ComfyUI up 47~59%, LLM prefill up 15~62%, token generation nearly unchanged.
- Most issues come from crowdsourcing compatibility data: The README homepage's entry point is "run the read-only collect_compatibility.py first, then file a compatibility issue," with no real unlock required. So most of the 224 issues are hardware reports rather than bugs, and the bar for community participation is set very low.
Competitors
| Name | Where | Launched | Scale | How it differs |
|---|---|---|---|---|
| Zagitta/gpu-unlock | Open source | 2026-10-18 | 17,130 stars / 1,720 forks | Upstream original, Linux kernel module, now claims support for 20/30/40; official team doesn't do Windows |
| JustAResearcher/gpu-unlock-ada | Open source | 2026-10-23 | 4,786 stars | RTX 4090/4070 Ti S, Linux; targets Ada cards, which don't overlap with its hardware |
| physicsdolphin/nv-uefi-unlocker | Open source | 2026-10-26 | 1,832 stars (11-01 onward, +400 per day) | The most direct rival: also Windows UEFI, but boots from a USB stick and routes by chip family, covering 20/30/40 and laptops. Covered by Tom's Hardware 11-01, Wccftech, r/overclocking, and Show HN. Tom's only mentions this project's class in passing as an "earlier Windows EFI tool." |
| rough2515-hub/rtx3080-unlock-public | Open source | 2026-10 | Small | One of its upstreams, only unlocks a single MSI 3080 via UEFI USB |
| TOTORONG/AD103_win_unlocker, CMP90/50 Windows unlocker | HuggingFace / mining-card circles | Earlier | Small niche | An earlier Windows EFI unlock precedent, aimed at CMP mining cards or 4080 |
| nlzy/turing-unlock, KohakuBlueleaf/KohakUnlock | Open source | 10-24 / 10-25 | 346 / 388 stars | Targets 20 Turing, Linux |
| NVIDIA official | big tech | — | — | Full speed is only unlocked on pro cards (RTX A series); GeForce has always been artificially throttled, and NVIDIA offers no equivalent feature |
Growth tactics (evidence)
- Upstream README FAQ link-out (verified, original Zagitta README text)
- HN comment links it (verified, HN Algolia)
- Tech media mention in passing: Notebookcheck 10-24, TechTimes 10-26, WindowsForum (verified)
- Reddit r/LocalLLaMA, r/nvidia, r/gpu, r/tech_x, r/StableDiffusion (verified, search excerpts)
- Korean communities CLIEN / DCInside / Naver / tau-home, plus HKEPC on Threads (verified)
- YouTube Shorts and explainer videos (verified; whether the creator made them is unverified)
- Discord community plus crowdsourced compatibility via issue templates (verified, README)
Visibility and copycats
- The buzz is already out there, and the big wave has been covered to death. "GeForce half-speed unlocked" hit Tom's Hardware, Notebookcheck, Wccftech, MakeUseOf and others. The project itself only got mentioned in passing in the press, with no dedicated coverage.
- Plenty of copycats already: nv-uefi-unlocker (a more general Windows version that is taking its spot); third-party SEO sites gpu-unlock.net and gpuunlock.com already have "Windows support" pages and compatibility tables by GPU, quoting this repo's profiles directly; YouTube reposts as short videos; and DLSS5-Unlocker-style repos riding the "unlock" name (unrelated to this project, possibly phishing).
Differentiation
- Windows + no-reset handoff to Windows + rigorous evidence: every profile is pinned to GPU, motherboard and BIOS, separates maintainer self-tests from contributor reports, states clearly that no percentage gain is reported without a locked-state baseline, and gives a full recovery procedure. In a space that gets easily mistaken for a scam ("real or fake" videos, DLSS5 phishing repos), that restraint makes people trust it.
- It took off because of timing and being the only Windows version, not because of engineering rigor. Rigor explains why users were willing to submit reports and stick around; the cost is an extremely high bar (a separate ESP partition, BitLocker off, Secure Boot off, compiling clang 20 yourself, sourcing firmware yourself), which scares off ordinary users. So once nv-uefi-unlocker came out, booting from a USB drive with broader coverage, the press's attention moved on.
Takeaways
- When the upstream blows up but a platform is missing, port it to that platform as fast as possible, then get the upstream author to link to you in the FAQ. That captures most of the original's spillover traffic.
- Make the "compatibility report" a read-only, zero-risk first step (one script plus an issue template). That turns onlookers into contributors, and the issue count becomes a heat signal in itself.
- For high-risk tools, trade restrained evidence for trust.
- The lesson on the other side: a high bar hands the spot to an easier follower, and a platform gap only stays open for a week or two.
Uncertain
- Whether the author impacifist's identity is real, or whether they promoted it themselves on X or Korean communities, is unverified (there are no related tweets in the x-radar local corpus).
- The exact date the repo moved to the organization, and how many stars each channel brought in: no referrer data.
- How many people actually got it installed: the successful reports in issues are a minority, while many are "finished but no speedup" or "won't boot"; stars far outnumber real users.
- Long term: whether NVIDIA will block it through a driver or firmware update, and whether nv-uefi-unlocker will fully replace it.
Sources
- Repo README: github.com/windows-GPU-UNLOCK/Windows-GPU-UNLOCK
- Stars: our GitHub library repo_day (2026-10-24 ~ 11-06); rising.dev/gh/windows-GPU-UNLOCK/Windows-GPU-UNLOCK/
- Upstream: github.com/Zagitta/gpu-unlock; HN news.ycombinator.com/item?id=50219700
- Notebookcheck(10-24):www.notebookcheck.net/Nvidia-RTX-3090-performance-nearly-dou…
- TechTimes(10-26):www.techtimes.com/articles/329479/20261026/nvidia-rtx-gpus-w…
- Tom's Hardware (11-01, covering nv-uefi-unlocker): www.tomshardware.com/pc-components/gpus/open-source-usb-tool…
- Reddit: r/LocalLLaMA 1xbuzj5, r/nvidia 1xmj5yn, r/tech_x 1xftgmf, r/StableDiffusion 1xdoh8k (search snippets only, Reddit body text was blocked)
- Korea: www.clien.net/service/board/park/19285609, tau-home.com/post/windows-gpu-unlock-uefi-nvidia-rtx/
- Copycat sites: gpu-unlock.net/zh/windows, gpuunlock.com/zh/windows