Microsoft has quietly added a small but meaningful piece of cross-device security: the Link to Windows app on Android can now
remotely lock a paired Windows 11 PC, while other workflow and sharing features have been refreshed — but the app still does not offer a remote
unlock ability.
Background
Link to Windows (formerly branded Phone Link on Windows and Your Phone companion on Android) has been Microsoft's marquee effort to blur the line between Android phones and Windows 11 PCs. The experience has evolved from basic notification mirroring into a multi-feature cross-device suite that includes calls, messaging, screen mirroring, drag-and-drop file transfers and cross-device clipboard syncing. In mid‑2025 Microsoft previewed a refreshed Link to Windows experience that explicitly included a remote
Lock PC action, a consolidated
Recent Activity hub, and bidirectional file sharing between phone and PC. The preview and staged rollout began in the Windows Insider channel in July, and production builds and APKs reflecting the refreshed feature set circulated through November and early December 2025.
This change is pragmatic: it fills a narrow but real gap in day‑to‑day security for people who get up from a desk and forget to lock their machine, especially in public or shared spaces. At the same time, Microsoft and partners are clearly cautious — the experience emphasizes locking only, not unlocking, and the rollout is being staged by build, account channel and device support.
What arrived: features in the refreshed Link to Windows
The refreshed Link to Windows experience brings several incremental but practical improvements that work together to improve usability and security.
Core additions
- Lock PC remotely — a one‑tap button in the Android Link to Windows app that locks the paired Windows 11 machine when it is connected.
- Recent Activity — a consolidated view showing recent file transfers, shared photos and clipboard items synchronized from the PC.
- Phone → PC file sharing — file transfer that previously worked primarily from PC to phone now supports sending files from the phone to the PC as well.
- Clipboard and copy history surfaced — copied text from the Windows clipboard shows up in the Recent Activity area, making cross-device copy/paste more discoverable.
- Updated onboarding and UI — simplified setup flows and a modernized home experience to make pairing and discovering features easier.
Versioning and rollout notes
The refreshed UI and features were previewed in July 2025 and began appearing in production APKs and store updates through late November and early December 2025. Build artifacts suggest incremental releases (for example, builds in the 1.25071.x and 1.25102.x series during the rollout window, with a later build appearing in early December). Microsoft is staging the rollout, so availability depends on a mix of factors: the Android app version, a compatible Phone Link/Link to Windows build on Windows, account/channel eligibility, and OEM support for deeper features.
How the remote Lock works (practical mechanics)
The remote Lock action is intentionally simple: when the phone and PC are paired and the PC is connected to the Link to Windows/Phone Link service, the Android app surfaces a
Lock PC control. Tapping it sends a remote lock command to the paired Windows 11 machine, causing the session to end and the lock screen to engage.
Key operational points:
- The PC must be paired to the phone via Link to Windows / Phone Link and visible in Windows Settings under Bluetooth & devices > Mobile devices.
- The action requires the devices to be connected (the experience relies on the existing Link to Windows connectivity model rather than a separate “find my device” or cloud lock service).
- After the PC is locked remotely, Link to Windows disconnects until the machine is unlocked by the user, preventing the phone from acting as an automatic unlock token in that session.
These mechanics prioritize a conservative security posture: remote locking is helpful for terminating an active session, but the system deliberately avoids offering a remote unlock path that would risk weakening the PC’s local authentication.
Step‑by‑step: enabling and using Lock PC
- Update Windows 11 to the build recommended for Link to Windows functionality and ensure Phone Link on the PC is the latest available.
- On Android, update Link to Windows (opt into beta if necessary when features are in preview).
- Open Link to Windows on the phone and follow the onboarding prompts to pair the phone with the PC.
- Verify the phone appears in Windows 11 Settings > Bluetooth & devices > Mobile devices and that the same Microsoft account is used on both devices.
- In the app’s home or remote actions area, tap Lock PC when the PC shows as connected.
This sequence reflects the user‑facing setup steps Microsoft rolled out during the preview; individual users may see slightly different steps depending on their OEM and app channel.
Why remote unlock is absent — and why that matters
The refreshed Link to Windows intentionally provides only a
lock action, not unlock. That absence is meaningful and rooted in security tradeoffs:
- Remote unlocking effectively bypasses the local login barrier. If a phone could unlock a PC remotely, a lost or stolen phone (or a maliciously‑controlled device) would offer a direct path to a previously locked PC unless safeguards were extremely strict.
- Local unlock flows often require device‑proximate authentication (PIN, Windows Hello facial/ fingerprint recognition, or secure tokens) precisely because they guard against remote compromise.
- Offering a remote unlock would force Microsoft to define robust constraints: binding to a device and account, requiring recent biometric verification on the phone, or requiring an online two‑factor confirmation for every unlock — all of which complicate usability.
For now, Microsoft favors a conservative approach: let the phone act as a remote
terminator of a session (lock), but keep the resumption of a session under the direct control of whoever can authenticate locally to the PC.
Security analysis: benefits and risks
Benefits
- Fast mitigation of exposure: Forgetting to lock a laptop in a public place is common. A remote lock is an immediate, practical way to cut potential exposure.
- Low friction: A simple tap in the phone app accomplishes what might otherwise require sprinting back to an unattended device.
- Complementary to Dynamic Lock: Dynamic Lock (which automatically locks a PC when the paired phone moves out of Bluetooth range) remains useful; the manual Lock provides a deterministic fallback when Dynamic Lock may not trigger quickly enough.
- Audit and clarity: The Recent Activity center and the UI emphasis make cross‑device actions clearer, which can reduce accidental oversharing of sensitive content.
Risks and caveats
- False sense of safety: Locking the screen remotely protects the active session but does not retroactively secure data already exfiltrated or stop malware that already has persistent access.
- Dependency on pairing and account security: The phone command works only for paired devices under the same account, which means account takeover is still the core risk. If an attacker compromises the Microsoft account or the pairing relationship, they may control cross‑device features. Users must keep account credentials and MFA secure.
- Potential for social engineering: An attacker could trick a user into executing actions that appear benign in Link to Windows but have unintended effects; however, the lock action itself has limited destructive capacity compared with remote control tools.
- No remote unlock: While intentional, the lack of remote unlock can be inconvenient in legitimate scenarios (for instance, when the only way back to the machine is to be physically present, and the user needs someone else to unlock it). For enterprise-managed environments there may be other administrative tools, but consumer users will have to rely on local unlock flows.
- Rollout fragmentation: Feature availability depends on app and OS build versions plus OEM integrations (Samsung devices see deeper integration). That staggered availability can create inconsistent user expectations.
Practical recommendations and hardening steps
To get the benefit of remote locking without exposing additional risk, users should treat cross‑device linking as an extension of their account security posture.
- Enable multi‑factor authentication (MFA) on the Microsoft account tied to Link to Windows.
- Use Windows Hello (biometric or PIN tied to the device) instead of an easy password so local unlock remains strong.
- Register recovery and remote management options if using the device for work; enterprise admins should use management policies to log and control device linking.
- Unpair immediately if the phone is lost or stolen — using the Microsoft account device management portal or the Windows PC’s Mobile devices pane to remove the paired phone.
- Keep Phone Link and Link to Windows updated to the latest stable releases to receive security patches and bug fixes promptly.
- Audit paired devices occasionally and remove any devices no longer used.
Compatibility and the vendor landscape
The Link to Windows experience is broader on Android than iOS because Android allows deeper integration for features like app mirroring and drag‑and‑drop. OEMs also play a role: Samsung has repeatedly received enhanced capabilities through closer collaboration with Microsoft, like tethering your phone’s cellular connection automatically to a supported Samsung laptop via the Windows 11 network flyout.
Compatibility checklist:
- Android phone: modern Android versions with Link to Windows updated; deeper features often require OEM-specific integration on select hardware.
- Windows 11 PC: latest Phone Link / Link to Windows companion build and current Windows 11 updates (some features launched in Insider Preview before broader rollout).
- Same Microsoft account on both devices and pairing configured in Settings.
Because Microsoft stages features by region and channel, users may see the refreshed UI sooner on Insider builds, with general rollouts following after validation.
The user experience: what changes in daily use
For a frequent commuter, the remote Lock PC control is a small but meaningful tool. The new Recent Activity view reduces friction for the common scenario of quickly grabbing a file or clipboard snippet from a PC to continue work on the phone. Crucially, the switch to allow phone→PC file sharing closes a previous workflow gap that forced extra steps (email, cloud upload) to move files the other direction.
The new onboarding reduces the initial friction; users can now start pairing from the phone without needing to begin on the PC first. That improves discoverability and widens adoption among casual users who may not have previously tried the cross‑device feature set.
Enterprise considerations
Enterprises should evaluate Link to Windows features within an endpoint management and data protection context:
- Link to Windows is convenient, but administrators should decide if pairing is permitted on corporate devices and whether logs or policies need to capture these cross‑device actions.
- Corporate devices should combine these features with endpoint detection and response (EDR), conditional access, and device enrollment in Microsoft Endpoint Manager to ensure compliance with organizational security policies.
- The inability to remotely unlock a machine reduces the risk of delegation misuse but also means helpdesk workflows for account recovery remain unchanged.
Where Link to Windows could go next
Observing Microsoft’s iterative approach suggests several likely paths:
- Controlled remote unlock: If Microsoft adds unlock, expect it to be gated by strong constraints — e.g., phone biometric confirmation plus a secondary factor, or a time-limited temporary unlock token.
- Better enterprise controls: Admin APIs or policy settings to control which users or devices can pair and what cross‑device actions they can perform.
- Encrypted cross‑device sessions and audit trails: More explicit guarantees and logs for enterprises and privacy‑conscious users.
- Richer file and clipboard management: Searchable Recent Activity, persistent cross‑device clipboards with expiration policies, and granular sharing permissions.
Why this matters for Windows and Android integration
Microsoft’s strategy with Link to Windows is to make the PC a richer hub for mobile content and to reduce friction for workflows that cross devices. Small, trusted security features — like remote lock — are important because they demonstrate attention to real user pain points without introducing large new attack surfaces.
Lock being available without unlock is a sign of caution and maturity: the company is adding convenience while prioritizing security. For many users, that’s the right balance.
Limitations and remaining questions
- Exact availability remains fragmented: the feature arrives by version/channel and may not be visible to every user at the same time.
- The absence of a changelog in some store listings means users must rely on platform announcements or third‑party build repositories to track feature rollouts.
- It remains unclear how future unlock ideas will be handled and whether Microsoft will expand remote management capabilities for consumers.
Those uncertainties argue for patience and for users to rely on standard account and device security best practices rather than assuming the app covers all threat vectors.
Verdict: practical, cautious, and useful
The addition of a remote
Lock PC action to Link to Windows is a pragmatic, low‑risk enhancement that solves a common problem: quickly securing an unattended Windows 11 session. Coupled with Recent Activity and phone→PC file transfers, the refresh improves everyday cross‑device workflows without compromising core local authentication guarantees.
The decision to exclude remote unlocking preserves the security model that prevents a remote device from becoming a weak point in the authentication chain. Power users and IT administrators will appreciate the staged rollout and the conservative approach; everyday users will get immediate, tangible value from the lock button and the improved sharing features.
For now, Link to Windows is better at stopping exposure than it is at enabling remote access — and in this case that tradeoff is the right call.
Source: Windows Central
https://www.windowscentral.com/micr...11-pc-but-it-still-cant-unlock-your-computer/