Skip to content
TroubleGrid

PowerToys Mouse Without Borders: "Pairing could not be loaded or updated" after the 0.102 update

Last verified November 2026Tested against PowerToys 0.101.2652.0 - first reports of the untrusted-signature failure (26 September 2026), PowerToys 0.102.2933.0 (21 October 2026), PowerToys 0.102.3001.0 (27 October 2026) - most reports, PowerToys 0.102.3101.0 (6 November 2026) - hotfix for pairing; service mode still broken, PowerToys 0.101.2362.0 (25 August 2026) - last build reported working, including service mode, Windows 10 22H2 and Windows 11Well documented

If this started after PowerToys updated itself, it is a PowerToys bug, not your network. Builds released from late September to late October 2026 (reports cover 0.101.2652.0 to 0.102.3001.0) can reject their own Microsoft-signed files, so Mouse Without Borders cannot load, accept or generate a key. Update every PC to 0.102.3101.0 or later, then pair again. If Use Service is on, turn it off: service mode is still broken in 0.102.3101.0.

PowerToys 0.102 shipped to auto-update in late October 2026, and the PowerToys issue tracker filled with reports of Mouse Without Borders refusing to pair. Microsoft fixed the main cause in the 0.102.3101.0 hotfix on 6 November. A second, separate failure in service mode is still open. The steps below tell you which one you have.

Symptoms

  • "Pairing could not be loaded or updated. Try again." in Mouse Without Borders settings
  • New Key does nothing, or the existing security key is no longer accepted
  • The other PC's tile cycles Negotiation (blue) → Connecting (orange) → Error (red)
  • The log shows "Rejected Settings IPC client: untrusted-signature" or "Rejected SettingsSync server: untrusted-signature"
  • Turning on Use Service fails with "Mouse Without Borders could not switch service mode. Restart PowerToys and try again."
  • It started right after PowerToys updated itself, and reinstalling, firewall changes and running as administrator do not help

Why this happens

A signature check rejected validly signed PowerToys files

PowerToys added a check that the Settings app and Mouse Without Borders are signed by the same certificate. Microsoft signs different PowerToys components with different valid certificates, so the check rejected them and pairing failed with an untrusted-signature error. Reports start with 0.101.2652.0 and run through 0.102.3001.0. PR #51789 changed the check to verify each signature independently, and it shipped in 0.102.3101.0.

Put every PC on PowerToys 0.102.3101.0 or later, then pair again · Need service mode? Roll every PC back to 0.101.2362.0 until it is fixed

Service mode never starts listening for connections

With Use Service on, the service-started copies of Mouse Without Borders never open TCP ports 15100/15101, so the PC drops every connection. This still happens on 0.102.3101.0 and has no fix yet. Turning Use Service off restores the connection. Rolling back to 0.101.2362.0 also restores service mode.

If Use Service is on, turn it off and restart PowerToys · Need service mode? Roll every PC back to 0.101.2362.0 until it is fixed

The PCs are on different PowerToys versions

Updating only one PC is not enough. A user whose PCs showed as connected but would not share input fixed it by updating the PC that was behind, and a PowerToys collaborator closed the report on that basis.

Put every PC on PowerToys 0.102.3101.0 or later, then pair again

Fixes

Put every PC on PowerToys 0.102.3101.0 or later, then pair again

about 10 min

0.102.3101.0 is Microsoft's hotfix for the untrusted-signature pairing failure; a PC left on an older build keeps failing even if the other one is fixed.

Applies to: PowerToys 0.101.2652.0 through 0.102.3001.0, Normal mode (Use Service off)

  1. On each PC, open PowerToys Settings and check for updates manually. If PowerToys came from the Microsoft Store, update it in the Store instead. You can also download the current installer from the PowerToys GitHub releases page.
  2. Confirm every PC now reports 0.102.3101.0 or newer. A mismatch matters: a user whose PCs showed as connected but would not share input fixed it simply by updating the one PC that was behind.
  3. Quit PowerToys from the system tray on every PC and start it again.
  4. If the old key is still rejected, select New Key in Mouse Without Borders on the first PC. On the second PC enter that key and the first PC's computer name, then select Connect.
  5. If the device tile still turns red, select Refresh connections on both PCs.

Confirmed by the vendor, though some users report it does not help.

Source: Microsoft PowerToys (GitHub), Microsoft PowerToys (GitHub), Microsoft PowerToys (GitHub), GitHub — microsoft/PowerToys, GitHub — microsoft/PowerToys, Microsoft Learn, Microsoft Learn

If Use Service is on, turn it off and restart PowerToys

about 5 min

Service mode is still broken on 0.102.x, including the 0.102.3101.0 hotfix: the service-started instances never open their network ports, so pairing fails however correct the key is.

Applies to: PowerToys 0.102.2933.0, 0.102.3001.0 and 0.102.3101.0 with Use Service enabled

  1. Run PowerToys as administrator (the Use Service toggle needs it), open Mouse Without Borders, and turn Use Service off.
  2. Quit PowerToys from the system tray and start it again. In the report that documents this, connections came back within seconds.
  3. If the PCs still do not reconnect, pair them again with New Key and Connect as in the first fix.

Reported to work by 3 users; not confirmed by the vendor. 1 report it did not help.

Source: GitHub — microsoft/PowerToys, GitHub — microsoft/PowerToys, GitHub — microsoft/PowerToys, Microsoft Learn

Need service mode? Roll every PC back to 0.101.2362.0 until it is fixed

Check before applyingabout 20 min

0.101.2362.0 predates the signature check that broke pairing, and several users report service mode works on it.

Applies to: Users who need Use Service (lock screen and UAC control) on PowerToys 0.102.x

Before you do this

This runs a PowerToys build from August 2026 and misses every fix since, including the 0.102 hotfixes. Only do this if you need service mode; otherwise the first two fixes are enough. Note your Mouse Without Borders layout and other module settings first in case they do not carry over.

First:

  • Note your current PowerToys settings (Mouse Without Borders layout, keyboard remaps) before uninstalling
  1. On each PC, uninstall PowerToys from Settings > Apps > Installed apps. If you have both a Store copy and a GitHub copy, remove both.
  2. Open the PowerToys GitHub releases page, find Release v0.101.2362.0, expand Assets and download the installer that matches the PC (x64 or ARM64, per-user or machine-wide).
  3. Install it on every PC. All machines must run the same version.
  4. Turn off automatic updates in PowerToys Settings, otherwise it will offer 0.102 again. Turn them back on once a release notes a service-mode fix.
  5. Pair the PCs with New Key and Connect, then turn Use Service back on if you need to control the lock screen or elevated apps.

Reported to work by 5 users; not confirmed by the vendor.

Source: Microsoft PowerToys (GitHub), GitHub — microsoft/PowerToys, GitHub — microsoft/PowerToys, GitHub — microsoft/PowerToys, GitHub — microsoft/PowerToys, Microsoft Learn

Known issues

  • Pairing fails with an untrusted-signature error ("Pairing could not be loaded or updated"). Reported on these builds, though not on every PC running them

    Affects 0.101.2652.0, 0.102.2933.0, 0.102.3001.0 · Status: fixed

  • Use Service (service mode) drops all connections; the service-started instances never listen on TCP 15100/15101

    Affects 0.102.2933.0, 0.102.3001.0, 0.102.3101.0 · Status: workaround only

  • settings.json sharing violations can make the two PCs' security keys diverge, so input works in only one direction or settings are lost after a reboot

    Affects 0.101.2362.0, 0.102.3101 · Status: open

If none of this worked

If every PC is on 0.102.3101.0 or later, Use Service is off, and pairing still fails, the version bug is probably not your problem. Go through Microsoft's basic checks: both PCs on the same network, the key and computer name typed exactly, and Add a firewall rule for Mouse Without Borders selected on both. If input works in only one direction, or the key or layout resets after a reboot, that matches a separate open bug where the two PCs end up with different keys. It has no confirmed fix yet. Generating a new key and connecting again is the obvious thing to try, but nobody has confirmed it as a lasting fix.

Common questions

Will reinstalling PowerToys or resetting Mouse Without Borders fix it?
Not on the affected builds. On the GitHub issues, users who wiped the configuration, reinstalled, rebooted, ran PowerToys as administrator or changed firewall settings kept getting the same error. The bug is in the build itself, so you need 0.102.3101.0 or later.
Should I use the script that swaps in Mouse Without Borders files from a dev preview?
No. It was an unofficial stopgap posted before the hotfix. Two users said it worked and two said it did not. It is no longer needed now that 0.102.3101.0 contains the official fix.
Is it safe to attach a PowerToys bug report to a GitHub issue?
Generate a new security key afterwards. An open pull request exists to strip the Mouse Without Borders security key from the bug report zip, because the key is reported to appear in clear text in some of the included files.
Does the 0.103 dev preview fix it?
The dev preview carries the same pairing fix (0.103.3099.0 and later list it), but a tester reported service mode is still broken on 0.103.3052.0. The stable 0.102.3101.0 is the better choice for most people.

Did this fix work?

If a step is wrong, outdated, or did not help, telling us is the fastest way to get it corrected. Reports are reviewed before new articles.

Report a problem with this page

Related problems

Sources

  • Microsoft PowerToys (GitHub) · Release notes · checked Nov 17, 2026

    • v0.102.3101.0 was released on 6 November 2026 as a hotfix release
    • The hotfix release notes say it fixes Mouse Without Borders pairing failures
    • The Mouse Without Borders entry reads: fixed pairing failures that could show an untrusted-signature error in signed builds (PR #51789)
  • Microsoft PowerToys (GitHub) · Release notes · checked Nov 17, 2026

    • v0.102.3101.0 (6 November) is marked Latest; v0.102.3001.0 was released 27 October and v0.102.2933.0 on 21 October
    • v0.101.2362.0 (25 August) is still listed with installers on the releases page
    • Dev preview v0.103.3099.0 also lists the fix for pairing failures that could show an untrusted-signature error
  • Microsoft PowerToys (GitHub) · GitHub issue · checked Nov 17, 2026

    • Pairing failed with an untrusted-signature error when PowerToys components were signed by different valid Microsoft certificates
    • Peer verification required identical signer certificate bytes, so validly signed components were rejected
    • The fix checks each executable's Microsoft signature independently; merged 4 November 2026 and closes #51567
  • Microsoft Learn · Documentation · checked Nov 17, 2026

    • To connect: select New Key on the first computer, enter that key and the first computer's name on the second, then select Connect
    • New Key generates a new key and resets current connections
    • Use Service runs Mouse Without Borders as a service under the System account so it can control elevated apps and the lock screen; it requires running PowerToys as administrator
    • Troubleshooting: same network, correct key and host name, and Add a firewall rule for Mouse Without Borders
    • Refresh connections reconnects a lost connection
    • Red is the Error connection status colour; brown is InvalidKey
  • Microsoft Learn · Documentation · checked Nov 17, 2026

    • PowerToys can be installed from the GitHub releases page, the Microsoft Store, or with winget install --id Microsoft.PowerToys --source winget
    • You can check for updates manually from PowerToys Settings; an automatic update checker shows a notification when enabled
    • Older installers are available on the PowerToys GitHub releases page
    • Per-user and machine-wide installers are offered
  • GitHub — microsoft/PowerToys · GitHub issue · checked Nov 17, 2026

    • Opened 25 October 2026 on 0.102.2933: pairing fails after about 24 seconds and the device tile cycles Negotiation → Connecting → Error
    • About 18 distinct users report the same failure, many on 0.102.3001
    • Firewall changes, running as administrator, reboots, reinstalling and resetting the configuration did not fix it for several users
    • Downgrading to 0.101.2362 worked for one user; another reported v101 working
    • An unofficial executable-swap workaround worked for two users and did not work for two others
    • Removing the Mouse Without Borders service and rebooting worked for one user and worked in only one direction for another
    • A user reported dev preview 0.103.3052 resolves the pairing failure, but not in service mode
    • Closed as completed by PR #51789 on 4 November 2026
  • GitHub — microsoft/PowerToys · GitHub issue · checked Nov 17, 2026

    • First reported 26 September 2026 on 0.101.2652.0, with the log line "Rejected SettingsSync server: untrusted-signature"
    • Mouse Without Borders logs show "Rejected Settings IPC client: untrusted-signature"
    • Reporters confirm the problem on 0.102.3001.0; two report downgrading both PCs to 0.101.2362.0 worked
    • Regenerating the key, resetting the configuration, switching service mode and running as admin did not help one reporter
    • The issue was pinned by the PowerToys team on 30 October 2026
  • GitHub — microsoft/PowerToys · GitHub issue · checked Nov 17, 2026

    • A user reported the connection failure was caused by the two PCs not running the same latest PowerToys version, and updating one PC fixed it
    • A PowerToys collaborator closed the issue as completed on 16 November 2026 after that confirmation
  • Microsoft PowerToys (GitHub) · GitHub issue · checked Nov 17, 2026

    • An open pull request (6 November 2026) sanitizes the Mouse Without Borders security key in the bug report tool's output
    • The linked issue reports the bug report zip leaks the SecurityKey in clear text via the runner log and MouseWithoutBorders.backup
  • GitHub — microsoft/PowerToys · GitHub issue · checked Nov 17, 2026

    • After auto-updating to v0.102.3001, the saved key is rejected and New Key cannot generate a new one
    • Running as administrator and a full config wipe and reinstall did not fix it for commenters
    • Restarting PowerToys temporarily restored an existing connection for one user
  • GitHub — microsoft/PowerToys · GitHub issue · checked Nov 17, 2026

    • On 0.102.3001.0, enabling Use Service fails with "Mouse Without Borders could not switch service mode. Restart PowerToys and try again."
    • Normal mouse sharing continues to work while service mode fails
    • Service mode works again after rolling back to 0.101.2362.0, reproduced on Windows 10 and Windows 11
  • GitHub — microsoft/PowerToys · GitHub issue · checked Nov 17, 2026

    • On 0.102.3101.0 (and 0.102.2933.0), enabling Use Service makes the PC lose every Mouse Without Borders connection and nothing listens on TCP 15100/15101
    • Turning Use Service off and restarting PowerToys restores the connection within seconds
    • A second user confirmed on 0.102.3101.0 that service mode breaks pairing, with "Pairing could not be loaded or updated. Try again." shown in Settings
    • That user reports rolling back to 0.101.2362.0 restored service mode
    • The issue is open with no fix as of 17 November 2026
  • GitHub — microsoft/PowerToys · GitHub issue · checked Nov 17, 2026

    • Mouse Without Borders logs are written under %LOCALAPPDATA%\Microsoft\PowerToys\MouseWithoutBorders\Logs\
    • settings.json writes can fail with a sharing violation, so the security key, layout and Easy Mouse settings can be lost across reboots
    • The two machines can end up with different security keys, with "Magic number invalid / Checksum invalid" in the log
    • The failure rate is reported to be much higher with service mode on
  • GitHub — microsoft/PowerToys · GitHub issue · checked Nov 17, 2026

    • On 0.102.3101, diverging security keys are reported to leave the keyboard working in only one direction