Dynamic Lock in Windows 11 and 10: How to Enable It

Dynamic Lock in Windows 11 and Windows 10 automatically locks your PC when your Bluetooth-paired phone moves out of range — but here is the part almost nobody tells you: it only locks if your PC is idle at the moment the signal drops. If someone sits down and starts typing before your phone crosses the Bluetooth threshold, Dynamic Lock does nothing. It is an extra barrier layered on top of Win+L, not a replacement for it — and the lock never fires instantly. Expect a wait of up to a minute after you walk away.

That caveat about the idle requirement is not a footnote. The lock fires only when two things are true at the same moment: your phone's Bluetooth signal has fallen below its threshold, and the PC is idle. If someone gains access before the signal drops — if they are already typing when you cross out of range — the device will not lock. The feature reduces the probability of someone getting in when you forget to lock your PC. It does not eliminate the possibility.

The second thing worth knowing before you invest time in this: Dynamic Lock is genuinely useful in shared spaces — an office where anyone can walk past your desk, a coffee shop, a repair counter — and genuinely unnecessary if you already hit Win+L religiously. Jake runs a phone repair shop where customers lean over the counter while he is in the back room digging for a replacement battery. That is the exact scenario this feature was built for.

What Dynamic Lock Actually Does (and What It Doesn't)

Dynamic Lock is a security feature that automatically locks your Windows device when your Bluetooth-paired phone moves far enough away that the signal strength drops below a fixed threshold. When that happens — and the system is idle — Windows locks the screen. You come back, you sign in again with your password, PIN, or Windows Hello.

What it does not do:

• It does not unlock your PC when you return. Dynamic Lock is one-directional. Walking back into Bluetooth range does not sign you back in. You always re-authenticate manually.
• It does not log you out or close your apps. It locks the screen the same way Win+L does. Everything you had open stays open, just behind the lock screen.
• It does not work without Bluetooth. If your PC has no Bluetooth adapter, or your phone's Bluetooth is off, the feature cannot function. There is no Wi-Fi or cellular fallback.
• It does not replace a strong password or PIN. The lock screen is only as strong as the credential behind it. If your sign-in method is weak, Dynamic Lock just puts a weak door in front of your data.

Even Microsoft's own description calls it an additional barrier — and that phrasing is worth taking at face value. It narrows the window of opportunity for someone to access an unattended machine. It does not close that window entirely.

The delay window (and why it matters)

When the Bluetooth signal drops, Windows does not lock instantly. The lock fires within a minute — and in practice the wait is usually closer to 30 seconds. That is short enough to feel responsive, and long enough that someone already sitting at your keyboard can defeat it.

Thirty seconds is enough time for someone who is already standing next to your PC to sit down and start interacting with it. Once they are actively using the machine, the "system idle" condition is no longer met, and Dynamic Lock will not fire at all. This is the exact failure mode to plan around.

The practical takeaway: if you work in a high-traffic environment where someone could reach your keyboard in under a minute, do not rely on Dynamic Lock alone. Use it as a backup for the times you forget to hit Win+L, not as your primary locking method.

What You Need Before You Start

Dynamic Lock has exactly one hardware dependency: Bluetooth. Both your PC and your phone need it, and both need it turned on.

A note on that last row: outdated Intel Bluetooth drivers are the most repeatedly reported root cause of Dynamic Lock failures that persist even after re-pairing. The fix that has worked for many on Intel-equipped laptops is downloading drivers directly from Intel's support page rather than relying on Windows Update or the manufacturer's system update tool.

Desktop PC users: your Bluetooth situation is different

If you are on a desktop tower rather than a laptop, a few things change. Most desktop motherboards do not include Bluetooth unless they are high-end models or specifically marketed for wireless connectivity. If your desktop has no built-in Bluetooth, you need a USB Bluetooth adapter (often called a dongle). These are inexpensive — typically under $20 — and plug into any free USB port.

However, not all USB Bluetooth adapters are equal for Dynamic Lock purposes. Cheap adapters with older Bluetooth versions may not maintain the kind of steady, always-on connection that Dynamic Lock needs. If you buy a dongle specifically for this feature, look for one that supports at least Bluetooth 5.0 and comes from a reputable chipmaker (Intel, ASUS, TP-Link are common choices). The adapter should stay plugged in — if it is on a USB hub that powers down with the system, Dynamic Lock may lose the connection during sleep.

Another desktop-specific quirk: if your PC is under a metal desk or inside a cabinet, the Bluetooth signal from your phone may be weaker than it would be in open air. Metal attenuates Bluetooth significantly. If Dynamic Lock triggers when you are still sitting at your desk, check whether the signal path between your phone's usual resting place and the PC's antenna passes through metal.

Turn On Dynamic Lock in Windows 11 (Settings)

Windows 11 keeps Dynamic Lock in the same location it has occupied since Windows 10 — the Sign-in options page — but the path to get there changed with the redesigned Settings app. Here is the full sequence.

Step 1: Pair your phone over Bluetooth

If you have not already paired your phone to this PC, do that first.

1. Press Win + I to open Settings.
2. Click Bluetooth & devices in the left sidebar.
3. Make sure the Bluetooth toggle at the top is set to On.
4. Click the Add device button (represented by a plus sign next to the devices list).
5. In the "Add a device" popup, select Bluetooth.
6. Put your phone into Bluetooth pairing or discovery mode (on most phones: Settings → Bluetooth → make sure it is on and visible).
7. When your phone appears in the scan list on the PC, click it.
8. Confirm the pairing code matches on both your phone and the PC, then accept on both.

Your phone should now appear in the list of paired devices under Settings → Bluetooth & devices, with a status showing "Connected" or "Paired."

Step 2: Enable Dynamic Lock in Sign-in options

1. Press Win + I to open Settings (if you closed it).
2. Click Accounts in the left sidebar.
3. Click Sign-in options on the right side.
4. Scroll down past the Windows Hello section (PIN, facial recognition, fingerprint) and the password section until you reach Dynamic lock.
5. Click the Dynamic lock row to expand it.
6. Check the box labeled Allow Windows to automatically lock your device when you're away.
7. Close Settings.

That is the entire setup. Windows does not show a confirmation dialog — the checkbox simply stays checked. To see whether it is functioning, walk away from your PC with your phone in your pocket and give it a minute; the screen should lock. If it does not, jump to the troubleshooting section below.

To turn Dynamic Lock off later, follow the same path and uncheck the box. The default state is off — Windows ships with Dynamic Lock disabled.

Turn On Dynamic Lock in Windows 10

Windows 10 reached end of support on October 14, 2025. It still runs, and Dynamic Lock still functions on it, but the operating system no longer receives free security updates. If you are relying on Windows 10 in a business setting, the lack of ongoing security patches is a bigger risk than any locking feature can compensate for.

The steps for enabling Dynamic Lock on Windows 10 are almost identical to Windows 11 — the only difference is the path through the Settings app, which was organized differently before the Windows 11 redesign.

Step 1: Pair your phone on Windows 10

1. Press Win + I to open Settings.
2. Click Devices.
3. Click Bluetooth & other devices in the left sidebar.
4. Make sure the Bluetooth toggle at the top is set to On.
5. Click Add Bluetooth or other device at the top of the page.
6. In the "Add a device" popup, select Bluetooth.
7. Put your phone into pairing mode, wait for it to appear in the scan list, and click it.
8. Confirm the pairing code on both devices.

Step 2: Enable Dynamic Lock on Windows 10

1. Press Win + I to open Settings.
2. Click Accounts.
3. Click Sign-in options in the left sidebar.
4. Scroll down to the Dynamic lock section.
5. Check the box labeled Allow Windows to automatically lock your device when you're away.
6. Close Settings.

Dynamic Lock on Windows 10 behaves the same as on Windows 11 — same delay, same idle requirement, same RSSI-based signal detection. The feature was introduced in the Windows 10 Creators Update (version 1703, April 2017) and has not changed substantially since.

How Dynamic Lock Actually Works Under the Hood

Dynamic Lock does not use GPS, Wi-Fi triangulation, or any location service. It relies entirely on a metric called RSSI — Received Signal Strength Indicator. RSSI is a number that represents how strong a radio signal is when it arrives at a receiver. Every Bluetooth chip reports it, and Windows reads it from the Bluetooth adapter to estimate how far away your paired phone is.

Think of RSSI like the volume of someone calling your name from another room. When they are standing right next to you, the voice is loud. When they walk down the hall, the voice gets quieter. When they go outside and close the door, you can barely hear them. Dynamic Lock is listening for the moment that "voice" — the Bluetooth signal from your phone — gets quiet enough that Windows concludes you have left the building.

Windows polls the Bluetooth connection at a regular interval and reads the RSSI value. When the value falls below a threshold — meaning the phone is physically far enough away that the signal has weakened — Windows initiates the lock sequence. The threshold is not user-configurable through the Settings UI.

The signal rule (for administrators)

When Dynamic Lock is enabled through Group Policy, a default signal rule is created in an XML format:

<rule schemaVersion="1.0">
  <signal type="bluetooth" scenario="Dynamic Lock" classOfDevice="512" rssiMin="-10" rssiMaxDelta="-10"/>
</rule>

What those values mean:

• type="bluetooth" — the signal source is a Bluetooth radio
• scenario="Dynamic Lock" — this rule applies specifically to Dynamic Lock, not to other Bluetooth uses
• classOfDevice="512" — the Bluetooth device class that qualifies (512 corresponds to certain phone/device classes)
• rssiMin="-10" — the minimum RSSI threshold below which the lock triggers
• rssiMaxDelta="-10" — the maximum change in RSSI that still counts as "in range"

You do not need to modify these values for normal use. They exist so that enterprises can fine-tune the sensitivity through Group Policy if the default range is too aggressive or too lax for their environment.

Why the delay exists

The delay between signal loss and the lock firing serves a purpose: it prevents false positives. If your phone briefly drops out of Bluetooth range — you walked to the kitchen for coffee, or you put the phone in a metal drawer — you do not want your PC locking every time. The delay gives the signal a chance to recover before Windows commits to locking.

The tradeoff is that the delay creates a vulnerability window. Someone who is already near your PC when you walk away can start using it before the lock fires, and once they are actively using it, the "system idle" condition is broken and the lock will not engage at all.

The Registry Method: EnableGoodbye

Behind the friendly Settings toggle sits a registry value with an unusual internal name: EnableGoodbye. Despite what the name might suggest, it has nothing to do with saying farewell — it is Microsoft's internal codename for the Dynamic Lock feature. Setting this value to 1 enables Dynamic Lock; setting it to 0 disables it.

The full registry path is:

HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
Value name: EnableGoodbye
Type: DWORD (32-bit)
Data: 1 (enabled) or 0 (disabled, the default)

When you would use the registry instead of Settings

Most people never need to touch this registry value — the Settings UI writes to it automatically when you check or uncheck the Dynamic Lock box. But there are three scenarios where editing the registry directly is useful:

1. The Dynamic Lock option is missing or grayed out in Settings — setting the registry value directly can restore the option. For users where the checkbox has disappeared entirely, this is the route back.
2. You are scripting the change — a .reg file or a PowerShell command can enable Dynamic Lock across multiple machines without clicking through Settings on each one.
3. You are troubleshooting — if the Settings toggle does not seem to be working, checking whether the registry value actually changed can tell you whether the problem is in the UI layer or deeper in the system.

Editing the registry manually

1. Press Win + R to open the Run dialog.
2. Type regedit and press Enter.
3. If prompted by User Account Control, click Yes.
4. In Registry Editor, navigate to: HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
5. In the right pane, look for a value named EnableGoodbye. If it does not exist, right-click in the empty space, select New → DWORD (32-bit) Value, and name it EnableGoodbye.
6. Double-click EnableGoodbye to modify it.
7. Change the Value data to 1 to enable Dynamic Lock, or 0 to disable it. Make sure Hexadecimal is selected as the Base.
8. Click OK.
9. Close Registry Editor and restart your PC for the change to take full effect.

After the restart, check Settings → Accounts → Sign-in options → Dynamic lock. The checkbox should now reflect the registry state — checked if you set the value to 1, unchecked if you set it to 0.

Using a .reg file instead

If you prefer not to navigate the registry manually, you can create a .reg file that does the same thing. Open Notepad, paste the following for enabling Dynamic Lock:

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon]
"EnableGoodbye"=dword:00000001

Or this for disabling it:

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon]
"EnableGoodbye"=dword:00000000

Save the file with a .reg extension (for example, enable_dynamic_lock.reg), then double-click it and approve the merge prompts. Restart afterward.

PowerShell equivalent

For those comfortable with the command line, the same change can be made in PowerShell:

To enable:

Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows NT\CurrentVersion\Winlogon" -Name "EnableGoodbye" -Value 1 -Type DWord

To disable:

Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows NT\CurrentVersion\Winlogon" -Name "EnableGoodbye" -Value 0 -Type DWord

These commands modify the current user's registry (HKCU), so they do not require an administrator PowerShell window — though running one does not hurt.

IT Admin: Deploy Dynamic Lock with Group Policy

For enterprises managing fleets of Windows machines through Active Directory, Dynamic Lock can be configured centrally through Group Policy. The policy lives under the Windows Hello for Business section of the Group Policy editor.

The GPO path is:

Computer Configuration
  → Administrative Templates
    → Windows Components
      → Windows Hello for Business
        → Configure dynamic lock factors

Step-by-step GPO configuration

1. Open the Group Policy Management Console (GPMC) on a domain controller or a machine with the RSAT tools installed.
2. Scope a domain-based Group Policy to the computer accounts in Active Directory that you want to target. You can link it to an OU containing the relevant machines.
3. Right-click the Group Policy Object and select Edit to open the Group Policy Management Editor.
4. Navigate to Computer Configuration → Administrative Templates → Windows Components → Windows Hello for Business.
5. Find and double-click the policy setting named Configure dynamic lock factors.
6. Set the policy to Enabled.
7. Click OK and close the Group Policy Management Editor to save the Group Policy object.

When this policy is enabled, a default signal rule is created with the XML values shown in the "How Dynamic Lock Actually Works" section above — Bluetooth signal type, Dynamic Lock scenario, class of device 512, RSSI minimum of -10, and RSSI maximum delta of -10.

What GPO does and does not control

Enabling this GPO setting configures the signal rule that Dynamic Lock uses to determine when to lock. However, it does not automatically pair phones to PCs — each user still has to pair their own phone over Bluetooth manually through the Settings UI. The GPO controls the behavior parameters; the pairing is always user-driven.

Additionally, the GPO applies to the computer, not the user. This means it affects all users who sign in to machines within the policy's scope, and the signal rule applies system-wide once the machine processes the Group Policy update.

Deploying via Microsoft Intune

For organizations using Microsoft Intune instead of traditional Group Policy, the same configuration can be pushed through an Intune profile. The settings catalog in Intune includes Windows Hello for Business policies, and dynamic lock factors can be configured there. The specific configuration path in Intune may vary by version, but the underlying policy — "Configure dynamic lock factors" — is the same one exposed through Group Policy.

Intune deployment is particularly relevant for organizations managing devices that are not domain-joined or that use Azure Active Directory (now Microsoft Entra ID) rather than on-premises Active Directory. The Intune approach delivers the same XML signal rule to target devices without requiring a domain controller.

Enterprise caveats worth knowing

If you are rolling this out to a fleet, three things will save you support tickets later:

• Bluetooth must be enabled in the BIOS/UEFI. Some corporate images ship with Bluetooth disabled at the firmware level for security hardening. Dynamic Lock will simply not appear in Settings on those machines, and users will not know why.
• Users need to pair their own phones. There is no way to pre-stage a phone pairing centrally. Each user pairs their own device after the GPO lands. Communicate this clearly or you will get "it's not working" tickets from people who never paired a phone.
• Test with a small pilot group first. Bluetooth behavior varies wildly across phone models, adapter manufacturers, and even office layouts (walls, metal desks, interference from Wi-Fi access points). What works perfectly on the IT floor may fail on the warehouse PCs surrounded by metal shelving.

Why Dynamic Lock Stops Working (and How to Fix It)

Dynamic Lock is one of those features that works well when it works and is maddeningly opaque when it does not. The error messages are vague ("Your paired device cannot be found. It may be off, out of range or its Bluetooth is off"), and the troubleshooting path is not obvious because the failure can originate from the phone, the Bluetooth stack, the pairing, or the Dynamic Lock service itself.

Here are the failure modes, in rough order of frequency, based on reported cases.

Problem 1: "Your paired device cannot be found"

Symptom: In Settings → Accounts → Sign-in options → Dynamic lock, the Find device button fails, or the message says the paired device cannot be found even though the phone is sitting right next to the PC.

Most likely cause: The Bluetooth pairing exists in the phone's memory but not in Windows' Dynamic Lock service's memory, or vice versa. The two sides disagree about the state of the connection.

Fix:

1. Go to Settings → Bluetooth & devices (Windows 11) or Settings → Devices → Bluetooth & other devices (Windows 10).
2. Find your phone in the device list.
3. Click the three dots (or right-click) next to the phone's name and select Remove device.
4. On your phone, go to its Bluetooth settings and remove or "forget" the PC from the phone's paired devices list.
5. Restart both the PC and the phone — this clears the Bluetooth stack's cached state on both sides.
6. After both devices are back up, re-pair them from the PC side: Settings → Bluetooth & devices → Add device → Bluetooth, and select your phone when it appears.
7. Return to Accounts → Sign-in options → Dynamic lock and click Find device again.

One widely shared workaround, for cases where re-pairing alone does not stick: click Find device (it fails), then go to the phone's Bluetooth page and toggle Bluetooth off and back on, confirm the PC shows as connected on the phone, then click Find device on the PC again. The feature worked for about a day before needing the sequence repeated — pointing to an underlying driver or firmware issue rather than a one-time pairing glitch.

Problem 2: Dynamic Lock locks the PC but never re-detects the phone on return

Symptom: The lock fires correctly when you walk away, but when you come back and sign in, Dynamic Lock reports it is not working because no device is connected. You have to go to Dynamic Lock settings and click "Scan for device" every time to re-establish the link.

Most likely cause: The Bluetooth connection is dropping when the phone goes out of range and not automatically reconnecting when it comes back. Some phones (particularly iPhones, based on user reports) do not aggressively re-establish Bluetooth connections to PCs after a drop.

Fix attempts:

• On the phone, keep the Bluetooth settings page open during the reconnection attempt — this keeps the phone actively scanning rather than passively waiting.
• Toggle the phone's Bluetooth off and on after returning to the PC's range.
• If the phone has a "keep Bluetooth always discoverable" or similar setting, enable it.
• Check for a phone OS update — Bluetooth stack behavior changes between versions.

Unfortunately, there is no permanent fix if the phone's Bluetooth implementation simply does not auto-reconnect to PCs. In that case, the daily "Scan for device" ritual becomes part of using the feature.

Problem 3: Dynamic Lock option is missing entirely from Sign-in options

Symptom: The Dynamic Lock section does not appear at all in Settings → Accounts → Sign-in options, or the checkbox is grayed out and cannot be changed.

Most likely cause: The EnableGoodbye registry value is set to 0 or does not exist, or the Bluetooth adapter is missing/disabled.

Fix:

1. Verify Bluetooth is working: Settings → Bluetooth & devices, and confirm the toggle is On and at least one device can pair.
2. If Bluetooth is fine, edit the registry: press Win + R, type regedit, press Enter.
3. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon.
4. Find or create the EnableGoodbye DWORD value and set it to 1.
5. Restart the PC.
6. Return to Sign-in options and the Dynamic Lock section should be present and functional.

Problem 4: Dynamic Lock works intermittently — locks sometimes, not others

Symptom: The feature functions correctly for a period (hours or days), then stops working without any changes to settings or hardware.

Most likely cause: Outdated or buggy Bluetooth drivers. This is the single most commonly reported fix for persistent Dynamic Lock unreliability.

Fix:

1. Identify your Bluetooth adapter manufacturer. On most laptops, this is Intel (for Intel Wi-Fi/Bluetooth combo chips), Realtek, or Qualcomm.
2. For Intel adapters specifically, go to Intel's driver download page (intel.com → support → drivers → wireless/Bluetooth) and download the latest Bluetooth driver for your specific chip model.
3. Install the driver directly from Intel rather than through Windows Update. Windows Update and OEM update tools (like Lenovo System Update or Dell Update) do not always carry the latest Intel Bluetooth drivers.
4. Restart the PC after installation.
5. Re-pair the phone if the connection was dropped during the driver update.

One user on a Lenovo ThinkPad Carbon X1 reported that this driver update from Intel's site was the definitive fix — the phone stayed connected consistently afterward, and Dynamic Lock worked reliably. The same user noted that neither Windows Update nor Lenovo's own System Update tool had delivered the correct driver version.

Problem 5: Dynamic Lock fires when you do not want it to

Symptom: The PC locks even though you are still nearby — you just put the phone down on a desk a few feet away, or you are in a room where Bluetooth signal is attenuated by walls.

Most likely cause: The RSSI threshold is being crossed even though you are physically close. Bluetooth signal strength is affected by physical obstacles (walls, metal objects, human bodies), interference from other 2.4 GHz devices (Wi-Fi routers, microwave ovens, wireless keyboards), and the phone's antenna orientation.

Workarounds:

• Keep the phone on the same side of any walls as the PC when working.
• Move the phone away from sources of 2.4 GHz interference.
• If the problem persists and the sensitivity is genuinely wrong for your environment, an administrator can adjust the RSSI thresholds through the GPO signal rule — though this is an advanced configuration and should be approached with caution.
• The simplest workaround: keep the phone in your pocket rather than setting it on a desk while you work.

Problem 6: Dynamic Lock works but the delay is too long

Symptom: The PC does eventually lock, but not for what feels like too long after you walk away.

Most likely cause: This is the designed behavior. The delay — up to a minute on paper, closer to 30 seconds in practice — is intentional, to avoid false locks.

The honest answer: There is no user-accessible setting to shorten this delay. It is not configurable through the Settings UI, and there is no documented registry value to change the timing. If the delay is unacceptable for your security needs, the alternatives are:

• Hit Win + L manually every time you step away — instant, reliable, no delay.
• Set a shorter screen timeout: Settings → System → Power & battery (Windows 11) or Settings → System → Power & sleep (Windows 10), and reduce the "turn off my screen after" interval. This does not lock the PC, but it turns the display off, which reduces casual snooping.
• Enable the screen saver with "On resume, display logon screen" checked, set to a short interval. This locks the PC on a timer independent of Bluetooth.
• Consider Presence Sensing (discussed below) if your hardware supports it — it uses a dedicated presence sensor rather than Bluetooth and responds faster.

Dynamic Lock vs. Presence Sensing vs. Other Locking Methods

Dynamic Lock is not the only way Windows can lock itself. Depending on your hardware and how much you want to trust automation, there are several approaches, each with different tradeoffs.

Presence Sensing: the newer, faster alternative

Windows 11 introduced Presence Sensing, a feature that uses a dedicated hardware presence sensor — typically built into the camera or as a separate infrared sensor — to physically detect whether a person is in front of the PC. Unlike Dynamic Lock, which relies on a Bluetooth proxy (your phone), Presence Sensing detects you directly.

Presence Sensing can do things Dynamic Lock cannot:

• Lock on leave — the PC locks when you physically walk away, detected by the sensor
• Wake on approach — the PC wakes from sleep when you walk toward it, before you touch the keyboard
• Adaptive dimming — the screen dims when you look away and brightens when you look back

The limitation is hardware: Presence Sensing requires a PC with a compatible presence sensor. Not all Windows 11 machines have one. The exact Settings location varies depending on your PC manufacturer — some place it under power and screen settings, others under privacy or security. If your PC supports it, you will find it by searching "presence" in the Settings search bar.

For PCs that have both Dynamic Lock and Presence Sensing available, Presence Sensing is generally the better choice — it responds faster, does not depend on a Bluetooth pairing, and can both lock and wake. Dynamic Lock remains valuable on machines without a presence sensor, or as a redundant layer alongside Presence Sensing.

Why manual locking (Win+L) is still the gold standard

Every automated method has a failure mode: the Bluetooth signal is flaky, the presence sensor misreads, the timer is too long. Manual locking has no failure mode except forgetting. Hitting Win + L takes less than a second, works on every Windows PC ever made, and locks instantly with no delay.

The honest recommendation: use automated locking as a backup for the times you forget, not as a replacement for the habit of locking manually. Dynamic Lock and Presence Sensing are safety nets, not substitutes for the rope.

When Nothing Works: The Honest End of the Road

Some Bluetooth pairings simply refuse to cooperate with Dynamic Lock. If you have re-paired, updated drivers, edited the registry, toggled everything that can be toggled, and the feature still does not recognize your phone, here is what you are looking at.

Possibility 1: Your phone's Bluetooth stack is the problem

Some phones — and this is a hardware/firmware limitation, not a Windows issue — do not maintain the kind of persistent, low-level Bluetooth connection that Dynamic Lock requires. The phone may disconnect from the PC after a period of inactivity to save battery, and Dynamic Lock cannot function on a connection that does not exist.

Test: Pair the phone to a different Windows PC and try Dynamic Lock there. If it fails on the second machine too, the phone is the weak link.

What you can do: Try a different phone. If that is not an option, accept that this phone/PC combination is not going to work with Dynamic Lock, and rely on manual locking or a different automated method.

Possibility 2: Your PC's Bluetooth adapter is too old or too cheap

Older or low-cost Bluetooth adapters (particularly some USB dongles) may not support the Bluetooth profiles or maintain the connection stability that Dynamic Lock needs. If the adapter drops connections intermittently, Dynamic Lock becomes unreliable.

Test: Try a different Bluetooth adapter (a known-good one from a modern laptop or a quality USB dongle).

What you can do: Replace the adapter. A quality Bluetooth 5.0+ USB dongle costs under $20 and resolves the majority of "flaky Bluetooth" issues on desktop PCs.

Possibility 3: Something in Windows itself is broken

In rare cases, the Dynamic Lock service or its dependent components may be corrupted. This is the hardest to diagnose and the least common failure mode.

What you can try:

1. Create a new local user account and try setting up Dynamic Lock there. If it works in the new account, something in your original user profile is preventing it.
2. Run the Bluetooth troubleshooter: Settings → System → Troubleshoot → Other troubleshooters → Bluetooth (Windows 11).
3. Run sfc /scannow in an elevated Command Prompt to check for and repair corrupted system files.
4. If the machine is a work PC, ask your IT department whether Group Policy or a security tool is blocking the feature.

If none of that works, the pragmatic answer is to stop fighting it. Dynamic Lock is a convenience feature, not a necessity. Every security benefit it provides can be replicated by pressing two keys before you stand up. If the feature costs you more time in troubleshooting than it saves in convenience, it has failed at its own job.

Security Limits You Should Know About

Dynamic Lock is a real security improvement over nothing, but it has specific limits that matter if you are relying on it to protect sensitive data.

Limit 1: The vulnerability window before the lock fires

Between the moment your phone goes out of Bluetooth range and the moment the lock fires, there is a gap — up to a minute on paper, and closer to 30 seconds in practice. During that gap, the PC is unlocked and usable. An attacker who is already positioned near the machine when you walk away can begin interacting with it, and once they are actively using it, the "system idle" condition is not met and the lock will not fire.

Mitigation: In environments where this is a real risk (public spaces, high-traffic offices), manually lock with Win+L every time you step away. Dynamic Lock is for the times you forget, not for the times an adversary is waiting.

Limit 2: It requires the system to be idle

The idle requirement is absolute: if the system is not idle at the moment the Bluetooth signal drops, the device will not lock. This means any process that keeps the system "active" — a running application, a download, a background task that counts as activity — can prevent Dynamic Lock from firing.

Mitigation: Be aware of what your PC is doing when you step away. If a task is keeping the system busy, Dynamic Lock may not engage.

Limit 3: Bluetooth can be jammed or spoofed

Bluetooth is a radio protocol, and like any radio protocol, it can be interfered with. In a targeted attack, someone could potentially jam the Bluetooth signal between your phone and your PC to prevent Dynamic Lock from detecting the signal drop — though this is an exotic scenario far beyond the casual "walk by and snoop" threat that Dynamic Lock is designed to address.

The honest assessment: Dynamic Lock is effective against opportunistic access by passersby. It is not effective against a determined attacker with specific knowledge of the feature. For most users — including Jake at his repair counter — the opportunistic threat is the realistic one, and Dynamic Lock addresses it adequately.

Limit 4: The lock is only as strong as your sign-in method

Dynamic Lock puts the Windows lock screen between an unauthorized user and your session. If your password is "password123" or your PIN is "1234", the lock screen is a speed bump, not a wall.

Mitigation: Use a strong, unique password or a high-entropy PIN. Better yet, use Windows Hello (facial recognition or fingerprint) if your hardware supports it — biometric authentication is significantly harder to bypass than a typed credential.

Quick Reference: Every Method at a Glance

Frequently Asked Questions

What is Dynamic Lock in Windows 11 and Windows 10?

Dynamic Lock is a security feature that automatically locks your Windows PC when your Bluetooth-paired phone moves out of range. It uses the Bluetooth signal strength (RSSI) between your PC and phone to estimate proximity — when the signal drops below a threshold, Windows locks the screen within about a minute. It works identically on Windows 11 and Windows 10.

How do I turn on Dynamic Lock in Windows 11?

Open Settings with Win+I, go to Accounts → Sign-in options, scroll down to the Dynamic lock section, and check the box labeled "Allow Windows to automatically lock your device when you're away." Your phone must already be paired over Bluetooth for the feature to function. The full step-by-step is in the Windows 11 section above.

How do I enable Dynamic Lock in Windows 10?

The path is nearly identical to Windows 11: Settings → Accounts → Sign-in options → scroll to Dynamic lock → check the box. The only difference from Windows 11 is that the Bluetooth pairing happens under Settings → Devices → Bluetooth & other devices rather than Settings → Bluetooth & devices. Dynamic Lock has been available since the Windows 10 Creators Update (version 1703).

Does Dynamic Lock work with iPhone?

Yes, Dynamic Lock works with iPhones that support Bluetooth pairing to Windows PCs. The pairing process is the same as with Android phones. However, user reports indicate that iPhones can be less reliable at automatically reconnecting to the PC after going out of range — some users find they must manually re-scan for the device each time they return. This is a limitation of the iPhone's Bluetooth behavior, not of Dynamic Lock itself.

Does Dynamic Lock work with Android phones?

Yes, Android phones work with Dynamic Lock. The pairing process is the same as any Bluetooth device. Android phones generally maintain the Bluetooth connection to the PC more persistently than iPhones, which tends to make Dynamic Lock more reliable with Android in practice — though individual results vary by phone model and Bluetooth implementation.

Can I unlock my PC automatically when I come back with my phone?

No. Dynamic Lock is one-directional — it locks the PC when you leave but does not unlock it when you return. You always sign back in manually with your password, PIN, or Windows Hello. If you want automatic wake-up when you approach, look at Presence Sensing (available on some Windows 11 PCs with compatible hardware), which can wake the screen when you physically approach the machine.

How far away do I need to be before Dynamic Lock triggers?

The exact distance varies based on the Bluetooth hardware in both your PC and your phone, as well as environmental factors (walls, interference, antenna orientation). Bluetooth typically has a range of about 30 feet in open air, and Dynamic Lock triggers when the signal falls below a specific RSSI threshold — which typically corresponds to moving roughly 10 to 30 feet away from the PC. You can see your specific trigger distance by walking away with your phone and noting when the lock fires.

Can I change the delay before the lock fires?

No, not through any user-accessible setting. The lock fires within a minute of the signal dropping — usually closer to 30 seconds — and the delay is built into the feature's design. If the delay is too long for your security needs, you should lock manually with Win+L or use a screen saver with a short timeout and the "On resume, display logon screen" option.

Why does Dynamic Lock say my paired device cannot be found?

This is the most common Dynamic Lock error and has several possible causes: the Bluetooth pairing between the phone and PC is in an inconsistent state, the phone's Bluetooth is off, the phone is out of range, or the Bluetooth drivers on the PC are outdated. The fix usually involves removing the pairing on both sides, restarting both devices, and re-pairing from the PC's Settings. If the problem persists, updating the Bluetooth drivers directly from the manufacturer's website (particularly Intel for Intel-equipped laptops) often resolves it.

Can I use Dynamic Lock without a phone?

No. Dynamic Lock requires a Bluetooth-paired device — which in practice means a phone. It cannot use a smartwatch, a Bluetooth headset, or any other Bluetooth peripheral as the proximity trigger. The feature is specifically designed around the assumption that you carry your phone with you when you walk away from your PC.

Does Dynamic Lock work on Windows 10 Home edition?

Yes. Dynamic Lock is available on all editions of Windows 10 and Windows 11, including Home, Pro, Enterprise, and Education. Unlike some features (such as Group Policy Editor), Dynamic Lock does not have an edition restriction — the Settings UI method works on every edition. The Group Policy deployment method, however, requires Pro/Enterprise/Education since those editions include the Group Policy Editor.

Does Dynamic Lock close my applications?

No. Dynamic Lock locks the screen the same way Win+L does — your applications, files, and browser tabs remain open and running behind the lock screen. When you sign back in, everything is exactly as you left it. Dynamic Lock does not sign you out, shut down the PC, or close any programs.

What is the EnableGoodbye registry key?

EnableGoodbye is the internal Windows registry value that controls Dynamic Lock. The name is a codename — it has nothing to do with saying goodbye or farewells. The full path is HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\EnableGoodbye. Setting it to 1 (as a DWORD) enables Dynamic Lock; setting it to 0 disables it. The Settings UI checkbox writes to this same value automatically, so you normally do not need to edit it directly.

Is Dynamic Lock safe to use for business data?

Dynamic Lock provides a meaningful layer of protection against opportunistic access — someone walking by an unattended PC. However, it has known limitations: a delay of up to a minute before locking, a requirement that the system be idle, and dependence on a sometimes-flaky Bluetooth connection. For high-security environments, it should be used as a backup to, not a replacement for, manual locking (Win+L) and strong authentication. It is best suited for shared workspaces, offices, and public environments where the primary threat is a casual snoop, not a targeted attacker.

What is the difference between Dynamic Lock and Presence Sensing?

Dynamic Lock uses Bluetooth signal strength from your paired phone to detect when you have walked away. Presence Sensing uses a dedicated hardware sensor (built into the camera or as a separate infrared sensor) to physically detect whether a person is in front of the PC. Presence Sensing is faster (near-instant vs. up to a minute), can also wake the PC when you approach, and does not require a phone — but it requires specific hardware that not all PCs have. Dynamic Lock works on any PC with Bluetooth and any paired phone.

Can I use Dynamic Lock and a screen saver lock at the same time?

Yes, they are complementary and do not conflict. Dynamic Lock locks the PC based on Bluetooth proximity; a screen saver with "On resume, display logon screen" locks it based on inactivity time. You can enable both, and whichever triggers first will lock the PC. This layered approach provides redundancy — if your phone's Bluetooth is acting up and Dynamic Lock fails to fire, the screen saver timeout still catches the unattended machine.

Wrapping Up: Should You Actually Use This?

The honest recommendation: enable Dynamic Lock if you work in a shared space and occasionally forget to lock your PC manually. It costs nothing (assuming you already have Bluetooth on both your PC and phone), it works well enough when the Bluetooth pairing is stable, and it provides a genuine safety net for the moments when the Win+L habit slips.

Do not enable it if you expect it to be your primary security control. The delay, the idle requirement, and the Bluetooth reliability issues make it unsuitable as a sole line of defense. Treat it as a backup — the seatbelt to your airbag of manual locking, not the other way around.

For Jake at his repair counter, the calculation was straightforward: customers lean over the counter every day, he walks to the back room multiple times per shift, and Dynamic Lock has locked the PC more than once when he would otherwise have left it exposed. Is it perfect? No — the Bluetooth connection to his phone drops occasionally, and he has had to re-pair a few times. But the feature has done its job often enough that he keeps it enabled.

Ethan's final word: "Use every layer you can get, and do not trust any single layer too much. Dynamic Lock is a good layer. Win+L is a better one. Strong passwords and Windows Hello are better still. Stack them, and you are harder to breach than 90 percent of the machines out there."

Revision note. Updated September 2026. If you have been fighting a flaky Bluetooth pairing to get this working, you are not alone, and the fact that you care enough to secure your PC this way already puts you ahead of most people. Keep at it.