Most lost-laptop policies rest on one assumption. If the device was locked and the disk was encrypted, the data is safe. On 19 November a researcher known as Nightmare Eclipse published a technique called FastUnlock that weakens that assumption. It lets someone holding a locked Windows PC run programs on it without signing in.
FastUnlock isn't a disaster. It runs code as a limited, non-administrator account and needs physical access. But it's a good moment to check what your device policy actually protects, because many estates are set up in the way that leaves them most exposed to it.
What FastUnlock does
From The Hacker News and an independent reproduction by ThreatLocker:
- The attacker needs physical access to a locked PC.
- They start the Microsoft account recovery flow from the lock screen, then use Narrator, Windows' built-in screen reader, to navigate into settings that shouldn't be reachable from there.
- The result is code running as an account called
WSIAccount, which ThreatLocker describes as "not an administrator account". ThreatLocker used an external drive to bring its test code in and says there are other ways. - It needs a Microsoft account to be available through the recovery flow, and it doesn't work on every machine.
- Microsoft has released no fix and no CVE so far, and there's no evidence it has been used in real attacks.
FastUnlock doesn't break BitLocker. It doesn't need to. On most corporate laptops the disk is already unlocked by the time anyone sees a lock screen.
Why the lock screen isn't the boundary you think
The most common BitLocker configuration is TPM-only. When the machine starts, the TPM checks that the boot chain hasn't been tampered with and releases the key automatically. The user never types anything before Windows loads. That's convenient, and it protects a machine that's switched off against someone who pulls out the drive.
What it doesn't protect is a machine that's already running. A laptop closed into sleep, or left at the lock screen, has an unlocked disk with Windows in front of it. At that point the lock screen is the only thing between a stranger and the data, and FastUnlock is a reminder that lock screens have bugs.
Encryption protects a machine that's switched off. Most lost laptops are just asleep.
Four decisions to revisit
1. TPM-only or TPM plus PIN?
A BitLocker startup PIN means the disk isn't unlocked until someone types it, before Windows loads. Microsoft's BitLocker countermeasures guidance covers when to use it. ThreatLocker notes that a preboot PIN helps when the device has just been turned on, or was hibernated. A PIN costs users a few seconds at boot. For executives, finance, admins and anyone who travels, that cost is usually worth paying. You can set it through Intune's disk encryption policy, and you can target it at groups rather than the whole estate.
2. Sleep or hibernate?
A startup PIN only protects a machine that has to start. If laptops sleep for days when the lid closes, the PIN is never asked for. Set high-risk devices to hibernate after a short period asleep, so a laptop left in a taxi falls back to the protected state.
3. What's reachable from the lock screen?
FastUnlock depends on account recovery options and accessibility tools being available before sign-in. Accessibility matters and shouldn't be removed without thought. But it's reasonable to review which recovery options your managed devices show at the lock screen, and whether consumer Microsoft accounts have any place on corporate machines. Check Microsoft's current documentation for the settings that apply to your Windows build.
4. What does your lost-device runbook assume?
Many runbooks say: mark the device lost, issue a remote wipe and close the ticket, because the disk was encrypted. Ask instead whether the device was powered off, asleep or at the lock screen when it was lost. If it might have been running, treat it as potentially accessed. Revoke the user's sessions and tokens, check sign-ins from that device, and rotate anything stored locally.
Don't overreact
This is a physical-access attack with a non-administrator result. There's no need to rebuild anything. Microsoft will most likely fix it in a future update, so watch for an advisory and apply it when it arrives. The value here is the review it prompts. Most estates made the TPM-only decision years ago for convenience and haven't looked at it since. Whether the next lock-screen flaw is serious or minor, the same settings decide how exposed you are.
Where we help
Our Microsoft security consultancy team reviews BitLocker, Intune and Windows hardening baselines against how your people actually work. Our SOCs are staffed 24/7 and watch for what happens after a device goes missing: sign-ins from it, token use and access to data. If you'd like a second opinion on your device policy, talk to us or book a demo.