Windows 11 lock screen bypass via Narrator
FastUnlock uses Narrator to get past the lock screen on Windows 11 PCs with a Microsoft account. Who's exposed, how to check and what to do for now.

On this page 3 sections ▾
WHAT TO DO
- There's no patch, CVE or Microsoft advisory yet, so your best protection today is a BitLocker startup PIN and shutting laptops down or hibernating them instead of just locking them.
- You're only at risk if the laptop has a Microsoft account on it and gets locked instead of shut down, because by the time the lock screen shows up, BitLocker has already unlocked the drive.
- Affected
- Shown on Windows 11 26H2 with the November 2026 update; no official list of affected versions
- Fixed in
- No fix yet
- Disclosed
- Nov 19, 2026
- Exploited
- No known attacks; public proof of concept
- Workaround
- BitLocker startup PIN, shut down or hibernate instead of locking, or block Narrator with AppLocker
If there's a Microsoft account on your Windows 11 laptop, locking it and walking away isn't as safe as it sounds: anyone who picks it up can get past the lock screen in a few keystrokes using Narrator, the screen reader built into Windows. It works even with BitLocker on and the November update installed. That's FastUnlock, a Windows 11 lock screen bypass the researcher known as Nightmare Eclipse dropped on GitHub on November 19 without warning Microsoft, so there's no patch yet. The good news is that it gets an attacker a lot less than the "BitLocker bypassed" headlines make it sound.
Quick facts
The researcher says it took him "a total of 5 minutes from finding this to breaching a fully encrypted bitlocker machine" with the November patch installed.
It isn't his first Windows lock screen bypass: his write-up points back to an earlier one, ZDI-21-1053, and calls this one "extremely convenient to use" by comparison.
When ThreatLocker reproduced it, the physical keyboard stopped typing while Narrator was in control, so its testers opened the on-screen keyboard instead.
#How the Narrator lock screen bypass works
The way in is a link everyone has seen: "I forgot my PIN" on the sign-in screen. That opens the Microsoft account recovery window, and pressing Win+U there turns on Narrator, which jumps to one of its own windows hidden behind the lock screen. From there, Caps Lock and the arrow keys get you into Windows Settings, and Settings lets the attacker start a program, all while the PC is still locked.
According to the researcher, Microsoft gave Narrator a new look and forgot to stop the new version from running on the lock screen, even though the old code that blocks its window when it runs as SYSTEM is still there.
#What FastUnlock gets an attacker, and what it doesn't
The catch for an attacker is whose account they end up in. When ThreatLocker reproduced the bypass on November 19, it landed in WSIAccount, the limited account Windows uses to run the lock screen, which it confirms is "not an administrator account." So it's still code running on a locked machine, just with very little power.
It also doesn't break BitLocker's encryption. On most PCs, BitLocker lets the TPM chip unlock the drive automatically at boot, so by the time the lock screen appears the drive is already readable and the attack goes around it. With a startup PIN, BitLocker doesn't load the encryption keys into memory until someone types it, so a laptop that's shut down or hibernated never gets as far as the lock screen.
ELI5: explain it simply▾

THE WORDS
- TPM
- A security chip in the PC that can hold BitLocker's key and hand it over at startup.
- Startup PIN
- A code you type before Windows even loads, so the drive won't unlock without you.
THE IDEA
Think of a house where the front door unlocks itself every morning when the owner's car pulls in. FastUnlock is a window left open after that, while everything inside is already unlocked. A startup PIN means the door stays shut until a person types a code, so there's nothing open to climb through.
#Is your Windows PC exposed to FastUnlock?
Three things decide it: the Windows version, whether an account on the PC is linked to a Microsoft account (the recovery window is the way in), and whether BitLocker asks for a PIN at startup. These PowerShell commands check each one. We couldn't run them ourselves, so the note under each command says what to look for instead of showing output:
student@opnf:~$ (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion').DisplayVersion # 26H2 is the version the researcher tested student@opnf:~$ Get-LocalUser | Select-Object Name, Enabled, PrincipalSource # PrincipalSource of MicrosoftAccount means a linked account student@opnf:~$ (Get-BitLockerVolume -MountPoint C:).KeyProtector.KeyProtectorType # run as admin; TpmPin means a startup PIN is set
The middle check uses PowerShell's PrincipalSource property, which tells you where each local account comes from: local, Active Directory, Microsoft Entra or Microsoft Account. If you see Tpm but no TpmPin in the last check, the drive unlocks itself at boot, which is the setup FastUnlock needs.
Here's where things stood on November 21:
| System | Status |
|---|---|
| Windows 11 26H2, November 2026 update | Bypass shown by the researcher; no fix |
| Other Windows 11 versions and Windows 10 | Not tested; no official list of affected versions |
| PC with an account linked to a Microsoft account | Meets the researcher's requirement |
| PC with only local accounts | Doesn't meet that requirement |
| BitLocker with a startup PIN, shut down or hibernated | Stops at the PIN prompt before the lock screen |
For work laptops, there's one big unknown: whether PCs where people only sign in with Entra ID work accounts are exposed. The researcher describes the requirement as at least one account "linked to an online account," and coverage so far only talks about Microsoft accounts. Until someone tests an Entra-only PC, treat it as unknown rather than safe.
If your PCs are exposed
Microsoft hasn't published a fix or a workaround, so these close the gap in the meantime, roughly from most to least protective:
- Require a BitLocker startup PINTurn on the "Require additional authentication at startup" BitLocker policy with a TPM and PIN, through Group Policy or Intune, then add the PIN on each PC. Microsoft's own guidance against attackers with physical access is TPM plus PIN.
- Shut down or hibernate, don't just lockA startup PIN only helps when the PC actually boots. Microsoft recommends shutting down or hibernating a device before it leaves an authorized user's control, and turning off sleep (standby) for high-risk laptops.
- Consider blocking NarratorThis one comes from the researcher, not Microsoft, and it takes Narrator away from anyone who needs it. More on that below.
- Watch for Microsoft's fixThere's no CVE or advisory yet. Once the patch is out you can drop the Narrator block, but keep the startup PIN.
The researcher's suggestion is to block Narrator with AppLocker or a custom access control list until Microsoft ships a patch. Nobody has published a test showing that a Narrator block holds under the lock screen's account, so treat it as a stopgap rather than a confirmed fix. Before you roll it out, check who in your organization uses Narrator, since a block takes it away from them too.
If you go that route, edition isn't a barrier anymore: since update KB 5024351, Windows 10 version 2004 and newer and all versions of Windows 11 can enforce AppLocker policies without needing Enterprise or Education.
Signs someone already tried
There's nothing published to hunt for. No attacks have been reported, and the attack needs someone physically at the PC, so the question to ask is whether a laptop was lost, stolen or left unattended while locked rather than shut down. If one was, handle it through your usual lost-device process rather than assuming the lock screen protected it.
Does FastUnlock break BitLocker encryption?
Can FastUnlock be used remotely?
Is there a patch for the Windows 11 Narrator bypass?
What this means for you
Check which laptops unlock BitLocker without a PIN and have an account linked to a Microsoft account. Those are the ones FastUnlock can reach while they sit locked, so add a startup PIN and have users shut down or hibernate them until Microsoft ships a fix.
SourcesResearcher's GitHubThreatLockerThe Hacker NewsCyber KendraSecurity AffairsMicrosoft BitLocker docsMicrosoft PowerShell docsMicrosoft AppLocker docs
Get opnF in your inbox
Tech news for IT professionals that actually teaches you something.
Our promise to you: we'll be conscious about email quality/frequency, and your address will never be shared/sold.