A powered-on laptop with a locked screen and a disk encrypted with BitLocker is the last thing that should give way to someone who does not know the password. But Abdelhamid Naceri claims that five minutes, the screen reader that ships with Windows and a USB stick are enough for him to strip away all that security.
His public demonstration, published and dubbed FastUnlock, arrives with no prior notice to Microsoft, no CVE identifier and no patch available until December 8, when the next Patch Tuesday falls. The BitLocker analysis by Privacy Affairs reconstructs the full chain and makes clear where what has been demonstrated ends and the researcher's interpretation begins.
The key to the finding is not a memory flaw or broken encryption. It is a door left open in the redesign of Narrator, the screen reader Windows has included for years and that anyone can activate from the accessibility menu on the lock screen. Microsoft overhauled its interface and did not prevent the new version from opening in the context of the login screen, so the operating system offers menu navigation and settings before it knows who is at the keyboard.
That detail turns a well-protected machine into one vulnerable to anyone who has it in their hands for a few minutes. BitLocker protection is designed precisely for this, so that a stolen laptop does not hand over its files, and here the layer that fails is not the encryption but the screen that precedes it. There are two conditions that the headline usually leaves out and that change the map of those affected: the attacker needs physical access and at least one account on the machine must be an online Microsoft account.
The chain, step by step
The route the researcher published can be described with technical names and without the detail that would allow it to be repeated: what matters is where the separation between the lock screen and the already-booted system breaks down.
The entry point is the "I forgot my PIN" link that appears on the lock screen. From there Windows offers the Microsoft account recovery flow, and in that context the keyboard shortcut that opens Narrator still works. The reader's new screen starts with focus on a background window that is never drawn on the monitor, and the attacker navigates it without seeing it using Caps Lock together with the arrow keys and the Enter key.
The path leads to the Narrator settings and, from there, to the system settings app. At that point File Explorer can already be opened through the Bluetooth and devices options or through autoplay. If a USB drive is connected, the system displays its contents and runs whatever the attacker selects, in the context of the lock screen's service account, which is called WsiAccount and is not an administrator. The Security Affairs report reproduces Naceri's own description; he publishes as Chaotic Eclipse and Nightmare Eclipse.
The Narrator shortcut is the hardest part to explain, because it requires no malicious program: it uses features Windows installs to make the system accessible, and that is where its strength lies.
The second half of the chain is what turns a settings desktop into control of the system. Naceri bases it on SignDrop, another of his zero-days published on November 10, which he says elevates privileges from that limited account. Without that step, what remains is reading files from the already-unlocked disk, which on a powered-on laptop is almost everything that matters. On a machine that is off, the disk is not yet open, and that difference decides whether a theft ends in data loss.
Who is really exposed?
The detail that separates alarm from reality is how the encryption is configured and what state the machine is in when it changes hands. The table summarizes the combinations the researcher describes and those that technical coverage considers out of its scope.
| Laptop state |
Encryption |
Exposed |
| Asleep or on and locked |
BitLocker with TPM |
Yes, the disk is already unlocked |
| Off or hibernated |
BitLocker with TPM only |
Yes, Windows boots only as far as the lock screen |
| Off or hibernated |
BitLocker with boot PIN |
No, the PIN prompt comes before Windows |
| Any |
Local accounts only |
No, if the online account condition is met |
| Windows 10 |
Not tested |
Unknown, the author did not try it |
The boot PIN deserves an explanation because it is the recommendation Microsoft has given in similar cases. BitLocker allows the TPM chip to be combined with a PIN requested at power-on, and that PIN is requested before the boot manager hands control to the operating system. If the attacker cannot reach the lock screen, the entire chain loses its first link. The Home version of Windows 11 does not offer that option, so the home fleet depends on keeping the machine on one's person.
There is a nuance that none of the sources consulted has been able to test and that is worth stating plainly: no one has verified that the boot PIN stops FastUnlock in practice, because the researcher has not tried it. The conclusion comes from how BitLocker works, not from an experiment. In May 2026, with another evasion by the same author, Microsoft did state that the combination of TPM and PIN made the attack unexploitable, and that precedent is the closest thing to a confirmation.
The difference between a theoretical threat model and a real theft lies in the minutes the laptop spends out of its owner's hands, not in the quality of the encryption installed.
What was reproduced and what was not
ThreatLocker published an independent reproduction on November 19 that confirms the escape from the lock screen to the settings, with one practical difference: its analysts could not type with the physical keyboard during navigation and had to open the on-screen keyboard for the parts that required text. The ThreatLocker exercise also confirms that the account in which the code runs does not have administrator privileges.
The independent reproduction is worth more than the author's video, even if partial, because someone outside the finding walked the same route to the settings without the discoverer's help and without his script.
What no one has recorded is the end of the chain. Naceri himself admitted that he did not have a USB drive at hand and that he did not run the final step on camera, so the part demonstrated on video is the exit to the settings desktop, not a program running from the removable drive. The distinction does not invalidate the work, because access to menus and files already breaks the promise of encryption, but it does require the story to be written precisely: what is verified is the escape, what is claimed is the execution.
The researcher's track record supports part of the credit. Naceri has published Windows zero-days without notifying Microsoft since April 2026 and several of his earlier findings ended with an assigned CVE and a patch, including the YellowKey evasion in May, which the company acknowledged a week later. TechSpot carries his estimate of five minutes from the finding to getting into a machine with the November patches installed, which is the most uncomfortable data point for anyone maintaining laptops in circulation.
Blocking Narrator, a remedy with a cost
Until a patch exists, the most cited mitigation is to prevent Narrator from running. Naceri suggested on his X account blocking the executable with AppLocker or with a custom access list, and that same day a script appeared on GitHub that applies a deny rule through Windows Defender application controls. It works, and at the same time it takes the screen reader away from anyone who depends on it on that machine.
The practical detail is that the rule applies per machine and not per user, so a poorly documented restriction can stay there for years without anyone remembering its origin or when it should be removed.
For an organization with laptops that travel, the sensible order is different. First, shut down or hibernate machines when they leave the office, because a sleeping laptop keeps the disk open and the lock screen within reach. Then add a boot PIN on machines with full BitLocker, which is the only layer that acts before Windows. And finally, decide case by case whether blocking Narrator is worth the accessibility cost, bearing in mind that the rule must be removed when the patch arrives.
A blocking rule that is forgotten ends up being worse than never having set it, because the machine loses accessibility and still lacks the fix that justified it, and no one remembers why the reader no longer starts.
The home side has no good technical answer. Windows 11 Home has no boot PIN and the default device encryption configuration uses only the TPM, so the machine boots to the lock screen without asking for anything. Anyone who wants out of that scenario has two real options: leave the laptop at home or turn it into a machine with exclusively local accounts, which clashes with the direction Microsoft has taken in recent years.
December 8 and what remains untested
Microsoft's next update window is December 8, 2026, and nothing guarantees that FastUnlock will be in it. The company has not confirmed the flaw, has not assigned a CVE and has not published mitigation guidance, something it did do in earlier cases involving the same researcher. If the fix does not arrive, the discussion will move to January and machines will continue with the same combination of strong encryption and an open door.
What remains of this story is a lesson about where defenses are placed. BitLocker works and the encryption has not been broken: what fails is the interface the user sees before identifying themselves, that layer added for convenience that no one reviews with the same rigor as the cryptographic core. The history of Windows 11 26H2 flaws of recent weeks points in the same direction, with new features landing before anyone asks what happens if they are combined with the lock screen.