Windows 11 Remote Lock (build 26340.10013): Intune can lock a lost PC without wiping it
Microsoft's new Insider preview lets IT lock a lost or stolen Windows PC from Intune, keep BitLocker and data intact, and unlock it only through Intune.
· 7 min read
Written by AI from the sources linked below. How we use AI
On this page
Microsoft is testing Remote Lock, a Windows 11 feature that lets IT administrators lock a lost, stolen or compromised PC from Microsoft Intune without wiping it. It appeared in the Windows Insider Experimental build 26340.10013 on 16 November 2026, and it matters because until now the usual remote options for a missing laptop were blunt: leave it alone, or erase it. Remote Lock sits between the two. The device keeps its enrolment, its BitLocker protection and the user's files, but nobody can sign in until an admin lifts the lock through Intune.
Key points
- Remote Lock is in preview in Windows 11 Insider Experimental build 26340.10013, released 16 November 2026, according to Microsoft's release notes.
- Locking signs out every active session, hides all sign-in options and shows a "Device locked" screen. Nothing is erased and the device stays enrolled and managed.
- The lock holds across restarts and while offline, and there is no local or offline unlock: only Intune can lift it.
- In the preview it is set up with a custom OMA-URI profile whose
LockStatevalue is 1 to lock and 0 to unlock, on Entra-joined, hybrid-joined or MDM-enrolled Windows Enterprise, Education or Pro devices. - It does not block Safe Mode, the Windows Recovery Environment or booting from USB, so Microsoft says to keep BitLocker on.
What to do
This is a preview, not a production feature, so most organisations cannot use it yet. If you run a test group of Windows Insider devices and manage them with Intune, you can try it now.
- Who is affected: devices that are Microsoft Entra joined, hybrid joined or MDM-enrolled and run Windows Enterprise, Education or Pro, on an Insider build that includes the feature. Microsoft's documentation lists these conditions.
- How to try it: in the Intune admin center go to Devices > Windows > Configuration > Create > New policy, choose Windows 10 and later, then Templates > Custom. Name the profile (Microsoft's example is "Remote lock - ON") and add the
LockStatesetting with value 1. - How to lock a device: assign that profile to a group reserved for locked devices. Adding a device to the group applies the lock at its next check-in.
- How to unlock it: create a second profile with
LockStateset to 0, assign it to an unlock group, and move the device from the lock group to the unlock group. - How to check status: a read-only
Statusnode reports 0 for unlocked, 1 for locked, 2 for lock pending and 3 for error. - Keep BitLocker on. Remote Lock does not protect a drive that is removed or a device that is reimaged.
What happened
On 16 November 2026 Microsoft published release notes for Windows 11 Insider Experimental Preview Build 26340.10013. Among the changes "gradually being rolled out" is a feature it calls Remote Lock. Microsoft describes it as a way for IT to "lock a lost, stolen or compromised Windows device from Microsoft Intune without wiping it." When the lock is applied, Windows signs out every active session, hides all sign-in options and shows a Device Locked screen.
Microsoft's separate documentation page, dated 12 November 2026 in its metadata, adds the operating detail. The lock applies at the device's next check-in. It persists through restarts and while the device is offline. The user's account is not touched: credentials stay valid and the person can still sign in on other devices. The default lock screen shows a laptop-and-padlock icon and tells the user the organisation has locked the device and to contact IT support.
BleepingComputer, which covered the feature on 17 November, reports that it is being tested in both the Beta channel (build 26320.10003) and the Experimental channel (build 26340.10013). We opened Microsoft's notes for the Experimental build; we did not open the Beta notes, so the Beta build number rests on BleepingComputer's report. The Register's coverage points to the Experimental notes and stresses that the lock can only be lifted by an administrator.
Background
Remote device management is not new. Mobile device management products have long offered "lock" and "wipe" actions for phones, and Intune can already wipe a Windows PC or isolate it from the network through Microsoft Defender. What was missing for Windows laptops was a lock that does not destroy data. A wipe is irreversible, which makes admins hesitant to use it when a laptop is merely misplaced on a train, and a device that is later found has to be rebuilt from scratch.
Remote Lock is designed for that gap. Microsoft's documentation says the device "stays enrolled and managed, BitLocker stays on and user data stays in place," so once the device is back in the right hands the user "picks up where they left off." The same Insider build also lets standard users set a BitLocker preboot PIN, which is part of the broader hardening push in the build, though that is a separate feature.
How it works
In the preview, Remote Lock is not a button in the Intune interface. It is configured through a custom configuration profile that writes to three settings under ./Device/Vendor/MSFT/RemoteDeviceLock/:
| Setting | Type | Purpose |
|---|---|---|
LockState (required) |
Integer | 1 locks the device, 0 unlocks it |
LockReason (optional) |
String, up to 1,024 characters | A reason shown on the lock screen |
RecoveryHint (optional) |
String, up to 256 characters | Help desk contact shown to the finder |
The design uses device groups as the trigger. One group holds locked devices and a second holds devices to be unlocked. Moving a device between groups changes which profile applies, and the change takes effect at the next check-in. A device that is offline when the lock is assigned will therefore lock only after it next connects to the management service. Microsoft's pages say the lock then holds even without a network, but they do not describe what happens to a machine that never reconnects after being stolen, and we have not tested it.
The LockReason and RecoveryHint fields are worth using. A finder who sees a message with a help desk number has a way to return the device, which a bare locked screen does not offer.
What it means
For IT teams. The practical gain is a reversible, low-regret action. A manager can lock a laptop within minutes of a loss report and decide about a wipe later. That matters for compliance too: the data is not exposed during the gap, and it is not destroyed if the device turns up in the office the next morning.
For users. Nothing is lost, but there is no way to unlock the device alone. Microsoft states there is "no offline or local unlock": no PIN, password, local admin account or web sign-in works on a locked machine. Anyone who relies on a laptop while travelling should know that the help desk, not a recovery option, is the way back in.
For security teams. Remote Lock is not a substitute for other controls. Microsoft lists what it does not do. It does not touch the user's account, so an admin worried about a compromised credential must still disable the account or revoke sessions in Microsoft Entra ID. It does not isolate the device from the network or erase data; the existing Intune and Defender controls cover those.
The boot-path caveat is the most important one. Safe Mode, the Windows Recovery Environment and booting from USB or other media are not blocked. If BitLocker is off, someone with physical access could in principle reach the disk by those routes, so the lock screen is a deterrent to casual use, and encryption is what actually protects the data.
What we don't know yet
- When it ships. Microsoft's notes say features in Insider builds "might never get released," and may change or be removed. No general availability date has been given.
- Whether a native Intune action will replace the custom profile. The documentation describes the OMA-URI approach as the preview method, but does not say what the final interface will look like.
- Editions and licensing at release. The preview lists Enterprise, Education and Pro; we have not seen anything about Home or any extra Intune licence.
- Behaviour on devices that never reconnect. As noted above, the documentation does not cover this.
- How broadly the Experimental channel rollout reaches. Microsoft uses a controlled feature rollout, so not every Insider will see the feature at once.
What to watch next
Watch for the feature appearing in the Beta and Release Preview channels, which would suggest a nearer ship date, and for an Intune admin center action that replaces the custom profile. Also watch Microsoft's documentation for changes to the list of boot paths that are not blocked, since that is the main weakness security teams will ask about.
Sources
- Microsoft Learn: Remote lock for Windows Devices (Preview)
- Microsoft Learn: Windows 11 Insider Experimental Preview Build 26340.10013
- BleepingComputer: Microsoft testing Remote Lock for lost or stolen Windows devices
- The Register: Windows 11 previews remote padlock only IT can open
Written by
The official account of the people who run audiotale.net: announcements, conversation starters and the newsroom's drafts. Posts written with AI say so. Every other account here is a real person.
Read next
SignDrop: unpatched Windows CLFS zero-day gives SYSTEM, no CVE or fix yet
A researcher published a Windows privilege-escalation exploit that abuses Microsoft's own CLFS hardening; here is who is in scope and what to do while there is no patch.
audiotale.net team6 min read
KB5131096 for Windows 10 (builds 19045.7846, 19044.7846): PowerShell signing and NTLM changes, USB audio fix
Microsoft's 10 November 2026 update for ESU and LTSC Windows 10 devices tightens PowerShell signature checks, turns on NTLM signing offers by default and fixes the September USB audio failures.
audiotale.net team7 min read
KB5132061 and CVE-2026-124194: November 2026 Patch Tuesday, Outlook zero-day leaks NTLM hashes
Microsoft's November 10 updates fix over a thousand flaws (1,235 or 1,093 depending on who counts), one exploited Outlook bug, and change NTLM signing and PowerShell signature checks.
audiotale.net team9 min read