Here is what is confirmed, what is still only claimed, and what Windows admins can do while Microsoft says nothing.
What ThreatLocker reproduced
On November 19, ThreatLocker's threat intelligence team published a proof of concept. It says FastUnlock allows someone with physical access to execute code and files without signing in to a user account. The attack uses Microsoft Narrator, Windows' built-in screen reader. It works by opening Microsoft Narrator accessibility feature Narrator, during the Microsoft account recovery flow and navigating Windows settings from the lock screen.
The most important detail is which account the attacker ends up in. According to ThreatLocker, the bypass provides access to "WSIAccount" user, which is not an administrator account. So the attacker gets past the lock screen, but only into a limited lock-screen account, not full control of the PC.
ThreatLocker also described some awkward parts of the attack. During our testing, ThreatLocker Intelligence could not type using the physical keyboard while navigating through Narrator, but if needed, it is possible to launch the on-screen keyboard when typing was needed. The team brought code onto the machine with an external drive and noted that other methods exist, though it did not describe them.
ThreatLocker lists three requirements:
- Physical access to the machine
- A Microsoft account available through the account recovery flow
- Narrator navigation using Caps Lock and the arrow keys
Summary: A security company has independently confirmed a physical-access route past the lock screen. It ends in a limited, non-administrator account.
What the researcher claims
The researcher's own claims are broader. Security Affairs reported that, according to the researcher, exploiting it can bypass BitLocker encryption and allow code execution under the lock screen's WsiAccount. He claims he breached a fully encrypted Windows 11 26H2 system in just five minutes, even with the November security updates installed.
The researcher blames a Narrator redesign. He explains that Microsoft introduced the issue while redesigning Narrator, failing to prevent its new interface from running in the lock screen account context. Cyber Kendra's reading of the published files adds that when Microsoft gave Narrator a new look, the new interface was not blocked from running on the lock screen, even though the older code still includes that check.
According to the disclosure, the attack works like this:
- The attack can be triggered through the "I forgot my PIN" or password option.
- From the Microsoft account recovery screen, enabling Narrator causes it to focus on a hidden background window. By navigating its options with the keyboard, an attacker can open Narrator's settings.
- From Settings, the researcher says several paths lead to File Explorer, including Bluetooth & devices and AutoPlay. Plugging in a USB drive then lets a binary run as WsiAccount.
There are caveats. Mallory's summary points out that the published demonstration omits the final code-execution step. The researcher has said he did not have a USB stick on hand for the video. ThreatLocker's test did use an external drive, which partly fills that gap. Testing so far is also narrow: SecurityOnline notes that the researcher has not tested Windows 10 or other Windows 11 builds. Exposure on any other version is unknown, not established.
Summary: The Windows 11 26H2 version, the November patch level, the five-minute timing and the BitLocker framing all come from the researcher. ThreatLocker has corroborated the lock-screen route and the WsiAccount context, not every part of those claims.
Is it really a BitLocker bypass?
Calling FastUnlock a "BitLocker bypass" makes a good headline but misleads. Cyber Security News explains the difference: BitLocker protects data at rest, but once Windows has started and the system drive is unlocked, the lock screen and Windows account permissions control what people can access. FastUnlock targets that later stage.
That is why the default setup matters. On a typical consumer or business PC using TPM-only BitLocker, the machine unlocks the drive itself during startup and goes straight to the lock screen. Microsoft's BitLocker countermeasures documentation describes this mode: TPM-only needs no user interaction, and if the TPM checks pass, the sign-in experience looks like a normal one. In that state, the drive is already decrypted behind the lock screen, so a lock-screen flaw can reach data that encryption protects only while the machine is off.
A preboot PIN changes this. Microsoft's documentation says BitLocker loads encryption keys into memory only after preboot authentication is complete. ThreatLocker says a preboot PIN can help protect a machine that is powered off or hibernated, because it must be supplied before the drive unlocks and Windows starts. Privacy Affairs makes the same point: FastUnlock needs the Windows lock screen with the drive already unlocked, and a PIN-protected laptop that was shut down or hibernated doesn't get that far.
Sleep is the weak spot. Microsoft's documentation warns that when a device resumes from sleep, users don't have to re-enter a PIN or USB startup key to reach encrypted data. A laptop that is merely asleep has its drive unlocked, preboot PIN or not.
Summary: FastUnlock gets around the lock screen on a running PC. It does not break encryption. Whether your data is exposed depends on whether the drive was already unlocked.
Has Microsoft responded?
So far, there is nothing official on record. Techtroduce reported that as of the November 19 disclosure, no Microsoft security advisory, assigned CVE identifier or confirmed patch specifically addressing FastUnlock had been identified.
Don't mix this up with November's Patch Tuesday. Cyber Security News notes that it previously covered two separate Windows BitLocker security feature bypass flaws, CVE-2026-97015 and CVE-2026-119832, in its November Patch Tuesday coverage. Those fixes should not be confused with a FastUnlock patch. If you are already up to date on November updates, that does not protect you here. The researcher says his test machine had them installed.
There is no sign of attacks yet. The same outlet reported that no attacks using FastUnlock had been publicly reported in the coverage reviewed.
Context: the researcher's track record
This disclosure has a history. Security Affairs describes the researcher as one who has publicly released zero-day proofs of concept, mostly against Microsoft products, often after criticizing how vendors handled his reports. He recently identified himself as Abdelhamid Naceri, a former Microsoft employee. RuntimeWire reports that International Cyber Digest called FastUnlock the latest of more than a dozen Windows zero-days Naceri has released since April without warning Microsoft first.
He has also attacked Narrator before. Naceri published a Narrator-driven BitLocker bypass for Windows touch devices in January 2021, and the FastUnlock ties the new bug to an earlier lock-screen bypass tracked as ZDI-21-1053.
That history cuts two ways. His past releases have been real enough that some were later exploited in the wild, so this one deserves attention. But his combative stance toward Microsoft is a reason to keep his biggest claims, like "extremely consistent in every machine," separate from what third parties have confirmed.
What Windows admins and users should do
There is no patch, so this comes down to hardening. The following steps come from ThreatLocker's guidance, Microsoft's BitLocker documentation and the researcher's own suggestions. They are not a Microsoft-issued FastUnlock fix.
1. Require a BitLocker preboot PIN on mobile devices. ThreatLocker recommends it, and Microsoft's documentation covers it under the policy setting "Require additional authentication at startup." Microsoft's trade-offs still apply: users who forget the PIN need a recovery key, and remote or unattended reboots get harder. Microsoft points to BitLocker Network Unlock for wired, WDS-backed environments.
2. Prefer hibernate over sleep. A PIN only helps if the drive is locked. Microsoft's documentation says hibernation locks the drive and sleep does not, and it lists the relevant Group Policy paths:
- Computer Configuration > Policies > Administrative Templates > Windows Components > File Explorer > Show hibernate in the power options menu
- Computer Configuration > Policies > Administrative Templates > Power Management > Sleep Settings > Allow standby states (S1-S3) when sleeping (plugged in) / (on battery)
Microsoft notes these settings are not configured by default.
3. Consider restricting Narrator. SecurityOnline reports the researcher suggests you block Narrator with AppLocker or a restrictive DACL. That is a real accessibility trade-off. Blind and low-vision users rely on Narrator, so check who depends on it before blocking it fleet-wide.
4. Control physical access and USB use. The demonstrated attack needs someone at the keyboard and, in ThreatLocker's test, a removable drive. Existing removable-storage and execution controls narrow the follow-on options. Don't leave unlocked-drive laptops unattended in public.
5. Know your accounts. The attack needs a Microsoft account available through the recovery flow. Machines with only local accounts may not meet that condition according to the published requirements, though that has not been tested broadly.
The bottom line
FastUnlock is now more than one researcher's claim: ThreatLocker has published its own reproduction. The confirmed risk is a physical-access route past the Windows 11 lock screen that ends in a limited, non-administrator account. Its main danger is to laptops whose BitLocker drive is already unlocked. A preboot PIN combined with a hibernate-not-sleep policy closes the most worrying scenario for powered-off devices. Until Microsoft acknowledges the flaw, treat it as unpatched and act accordingly.
References
- Windows 11 FastUnlock flaw bypasses lock screen in ThreatLocker test - Business Upturn Business Upturn · 2026-11-20T04:29:43.720000+00:00
- Windows 11 BitLocker Bypass via Narrator (FastUnlock): PoC Published securityonline.info
- Windows 11 Lock Screen Zero-Day Reportedly Bypasses Security - Techtroduce techtroduce.com