Live issue · Updated

Mouse Without Borders: “Pairing could not be loaded or updated. Try again.” after the PowerToys 0.102 update

If Mouse Without Borders stopped pairing right after PowerToys updated itself to 0.102, update both PCs to PowerToys 0.102.3101.0. That Stable release came out on 6 November 2026 and contains the fix. Nothing was wrong with your network, firewall or key. Before 0.102.3101.0, PowerToys Settings and the Mouse Without Borders engine only talked to each other when both programs were signed with the same certificate. The 0.102.3001 release files are signed with two different Microsoft certificates, so each side rejected the other. Settings couldn't hand the engine a new key, your saved key or your machine layout, which is why "New key" did nothing and the old key wasn't accepted.

What to do:

  • Update both PCs to 0.102.3101.0. Its release notes say it fixes Mouse Without Borders pairing failures that show an untrusted-signature error, and we checked that the fix is in that release's source. One user reports it working, with "Use Service" on. Steps below.
  • If 0.102.3101.0 doesn't fix it for you, roll back to 0.101.2362.0 or 0.102.2933.0, which users reported working before the fix. Steps below.

Before the fix, reinstalling 0.102, running PowerToys as administrator, rebooting, resetting the key, switching "Use Service" and deleting the Mouse Without Borders settings folder didn't fix it in the public bug reports.

What you see

  • In PowerToys Settings → Mouse Without Borders: "Pairing could not be loaded or updated. Try again." Some installs word it "Could not load or update pairing."
  • One user with "Use Service" on also saw "The saved pairing key cannot be used in the current mode. Generate a new key or connect using a key from another computer." when connecting with an existing key.
  • "New key" does nothing. The key you used before the update isn't accepted.
  • On the other PC, connections cycle from Negotiation (blue) to Connecting (orange) to Error (red), or connect without any status colours.
  • In the Mouse Without Borders log, under %LOCALAPPDATA%\Microsoft\PowerToys\MouseWithoutBorders\Logs\, this line repeats about twice a second:

    IpcChannel.cs::StartVerifiedIpcServer::118
        Rejected Settings IPC client: untrusted-signature
  • In the PowerToys Settings log, the same rejection from the other side:

    System.UnauthorizedAccessException: Rejected SettingsSync server: untrusted-signature

If you see untrusted-signature in either log, this page is about your problem. Users report it on 0.102.2933.0 and 0.102.3001.0, on Windows 10 and 11, after PowerToys' own auto-update and from the Microsoft Store.

Why it happens

PowerToys Settings and the Mouse Without Borders engine are separate programs that talk over a local named pipe. Since 0.102, each side checks the program on the other end before it accepts a message. Up to 0.102.3001, part of that check was that both programs carry the same signing certificate, byte for byte. A valid Microsoft signature wasn't enough.

We unpacked the 0.102.3001 x64 per-user installer from the GitHub release and read the signature of every program file in it. Both certificates are genuine Microsoft code-signing certificates, but they are different ones:

FileSigning certificate (thumbprint)
PowerToys.Settings.exe1D77A9B9E8FE2075D9AD15123257FB90DB0DA4A1
PowerToys.MouseWithoutBorders.exeAB172913A2960A224809EE8A0C371CD47A079B72
PowerToys.MouseWithoutBordersHelper.exeAB172913A2960A224809EE8A0C371CD47A079B72
PowerToys.MouseWithoutBordersService.exeAB172913A2960A224809EE8A0C371CD47A079B72

So on a PC installed from this file, Settings rejects the engine and the engine rejects Settings. Some users report the same two certificates the other way round on their install. Which file gets which certificate doesn't matter; that the two differ does.

What 0.102.3101.0 changes: it ships the fix #51789. Each side now checks the other program's Microsoft signature on its own, and that the other program's product name is PowerToys and its file name is the one expected. The two programs no longer need the same certificate. They still don't have it: in the 0.102.3101.0 x64 per-user installer, Settings is signed with 1D77A9B9… and Mouse Without Borders with AB172913…, the same split as 0.102.3001. By the new check that's fine. All the files we read carry a Microsoft signature, the product name PowerToys and the expected file name.

Check your version first

Run this in PowerShell on each PC. It only reads the two files' version and signature and changes nothing.

Get-ChildItem "$env:LOCALAPPDATA\PowerToys", "$env:ProgramFiles\PowerToys" -Recurse -Include PowerToys.Settings.exe, PowerToys.MouseWithoutBorders.exe -ErrorAction SilentlyContinue |
  Get-AuthenticodeSignature |
  Format-Table @{n='File'; e={Split-Path $_.Path -Leaf}}, @{n='Version'; e={(Get-Item $_.Path).VersionInfo.FileVersion}}, Status, @{n='Thumbprint'; e={$_.SignerCertificate.Thumbprint}} -AutoSize
  • Version 0.102.3101.0: you have the fix. The two thumbprints are expected to differ, and that's fine on this version. If you still see untrusted-signature in the logs after updating both PCs, this page doesn't cover your case; we know of no public report of it on 0.102.3101.0.
  • Version 0.102.2933.0 or 0.102.3001: these have the old check. If the two thumbprints differ, Mouse Without Borders can't pair on this version, whatever you change in its settings. Update.
  • A 0.103 version (Dev preview): none of the previews up to 0.103.3062 has the fix; the source of the later 0.103.3099.0 and 0.103.3151.0 includes it (see the update). See the previews.

Users who ran the thumbprint check on 0.102.3001.0 posted exactly the two thumbprints in the table above.

The first folder is where the per-user installer puts PowerToys, the second is the usual machine-wide location. If the command prints nothing, your copy is somewhere else (Microsoft Store copies are). We didn't run this command on Windows ourselves; the versions and thumbprints above come from the installer files.

Fix it

Option 1: update both PCs to 0.102.3101.0

Do it on both PCs; they need to run the same version.

  1. If you rolled back on this page's earlier advice, do this first: turn Download and install updates automatically back on (PowerToys Settings → General → Version & updates). If you pinned PowerToys in winget, remove the pin, because a blocking pin stops winget upgrade too: winget pin remove --id Microsoft.PowerToys (Microsoft's documented syntax; we didn't run it).

  2. Update PowerToys in its own updater (PowerToys Settings → General → Version & updates, with Update channel set to Stable), or with winget:

    winget upgrade --id Microsoft.PowerToys

    winget's newest PowerToys entry is 0.102.3101; we didn't run winget. Or download the installer from the 0.102.3101.0 release page. The x64 per-user installer we checked, PowerToysUserSetup-0.102.3101.0-x64.exe, has SHA-256 4B4C49A31E8B7E6A36647CCD3033ACB0AD56C306595A9409E59865C3C27D1CF2, the same as the release notes list. If PowerToys is installed for all users, take the machine-wide PowerToysSetup-0.102.3101.0-x64.exe instead; the release notes list its hash and the Arm64 installers' hashes, but we didn't read those files.

  3. Run the check on both PCs: both files should show 0.102.3101.0.

  4. If the PCs don't reconnect on their own, pair them again: generate a new key on one PC and enter it on the other.

The user who reports 0.102.3101.0 working upgraded a machine-wide x64 install from 0.102.2933.0, with "Use Service" on. They report clipboard sharing working in both directions between their two PCs and no untrusted-signature rejections in the Settings log, the Mouse Without Borders logs or the Application event log. That's one report; we haven't run 0.102.3101.0 or paired PCs with it.

From the Microsoft Store: we don't know when the Store copy gets 0.102.3101.0 and we didn't check the Store package. If your Store copy still shows an older version in the check, uninstall it and install with winget or the GitHub installer.

Option 2: roll back, if 0.102.3101.0 doesn't fix it

Use this only if updating both PCs didn't bring pairing back. Before the fix, rolling back to 0.101.2362.0 was what users in the bug reports most often said worked, and it matches the files: the signature check doesn't exist in 0.101.2362.0, so the two programs can't reject each other. Do it on both PCs.

  1. Uninstall PowerToys (Windows Settings → Apps → Installed apps → PowerToys → Uninstall). The original reporter also deleted the leftover %LOCALAPPDATA%\PowerToys folder before reinstalling.

  2. Install 0.101.2362.0. With winget (per-user install):

    winget install --id Microsoft.PowerToys --version 0.101.2362.0 --scope user

    Or download PowerToysUserSetup-0.101.2362.0-x64.exe from the 0.101.2362.0 release page. The x64 per-user installer we checked has SHA-256 D56FA7130FA68AFE553068C15A59A6B24C8DBCC9A0989A43EF0FC5A373230DE3, and winget's manifest for this version points to that same file. We didn't run winget, and we didn't check the machine-wide or Arm64 installers' files. The check is missing from the 0.101.2362.0 source itself, so it is missing from every installer of that version.

  3. Stop PowerToys updating itself straight back: open PowerToys Settings → General → Version & updates, turn off Download and install updates automatically, and keep Update channel on Stable. PowerToys will still offer the update. You can also turn off Show notifications for new updates. If you run winget upgrade --all, pin PowerToys first with winget pin add --id Microsoft.PowerToys --blocking (Microsoft's documented syntax; we didn't run it). Undo both when you try a later release.

  4. Pair the PCs again: generate a new key on one PC and enter it on the other. A key saved by 0.102 may not carry over.

Use exactly 0.101.2362.0, not any 0.101 build. The check arrived in later 0.101 builds, from 0.101.2572.0 on, and the first public report of this problem came from 0.101.2652.0. If you installed from the Microsoft Store, uninstall that copy and use winget or the GitHub installer for the rollback; we didn't check anything about the Store package. One Store user in the reports says rolling back to 0.101 fixed it.

Or roll back only as far as 0.102.2933.0 (21 October 2026): in its GitHub installer, Settings and Mouse Without Borders are signed with the same certificate, so the old check passes, and you keep 0.102's changes. Before the fix, one user said everything was back to normal after rolling back to 2933, another found every file on one certificate and the untrusted-signature errors gone but hadn't paired the PCs again yet, a third rolled back without saying clearly whether pairing came back, and a fourth rolled back one of their two PCs, used the key already saved on the other PC (still on 0.102.3001, where they couldn't make a new key) and says Mouse Without Borders works again. The one report of this error on 2933 came from a Microsoft Store install, whose files we didn't check. winget has no 0.102.2933.0 entry, so use PowerToysUserSetup-0.102.2933.0-x64.exe from the 0.102.2933.0 release page (SHA-256 EC0FD364AE1689A5E8FBEFB46BAD5C274C7BF0FBE9E828E14C88B44432ADA816 for the file we checked). On both PCs, do step 1 first, because this installer refuses to install over a newer version; use it instead of step 2, then do steps 3 and 4.

What you give up by rolling back to 0.101.2362.0: everything 0.102 added, including the Mouse Without Borders reconnection improvements one user misses, and two security changes, the signature check itself and encrypted storage of the pairing key when "Use Service" is on.

Option 3: can't update yet? Set the key by hand

This is only for a PC stuck on 0.102.3001 that you can't update or roll back yet. A user reported it on 0.102.3001 from the Microsoft Store. We haven't run it. It works around Settings instead of fixing it: the engine reads its own settings file when it starts, so you give it the key and the other PC's address directly.

  1. On each PC, exit PowerToys from the tray icon.

  2. Open %LOCALAPPDATA%\Microsoft\PowerToys\MouseWithoutBorders\settings.json in Notepad. Under "properties", set the key so it is the same on both PCs: "SecurityKey": {"value": "your-key-here"}. Use at least 16 characters, the minimum PowerToys accepts, for example the key you used before the update.

    In the same file, check "MachineMatrixString". The engine only connects to computers on this list, and it ignores the list unless it has exactly four entries. It must name both PCs, in the same order on both, with empty entries for the unused slots: for example "MachineMatrixString": ["HOME-PC", "OFFICE-PC", "", ""], using the names hostname prints on each PC. If it is [] or only lists this PC, which is what you get after resetting or deleting the Mouse Without Borders settings, add the other PC. Settings can't do it for you while the check fails.

  3. Add the other PC to the hosts file, C:\Windows\System32\drivers\etc\hosts (Notepad opened as administrator), as a line with its IPv4 address and the same computer name as in the list, for example 192.168.1.20 OFFICE-PC. The in-app IP mapping can't reach the engine either, and without it the reporter's PCs tried an IPv6 address and failed.

  4. Start PowerToys again.

The reporter got the mouse, keyboard and clipboard working this way. The status colours stay missing, and anything you change on the Settings page still isn't applied.

This only works with "Use Service" off, which is how the reporter ran it. We read this and the machine-list rule from the 0.102 source, not from a test: when "Use Service" is on, the engine runs as the Windows system account and only accepts a key stored in encrypted form, starting mwb-dpapi:. A key you type into the file is then ignored. Users also report that the Settings switch for "Use Service" stops working in this state. If it is on and you can't switch it off, update or roll back.

The 0.103 previews

None of the 0.103 Dev previews up to 0.103.3062 (4 November 2026) has the fix. If you run a preview and have this problem, move both PCs to Stable 0.102.3101.0: uninstall PowerToys first (step 1 of Option 2), then install 0.102.3101.0 from its release page, and set Update channel to Stable. Then do steps 3 and 4 of Option 1. The 0.102.2933.0 installer refuses to install over a newer version, and we expect 0.102.3101.0's to do the same; we haven't tested moving from 0.103 back to 0.102.

The 0.103 previews also add the same check to a second connection, between Mouse Without Borders and its clipboard helper. By the source, 0.102.3101.0 doesn't have that check, so the clipboard helper's certificate doesn't matter there.

Four Dev previews of 0.103 had come out since 0.102.3001 by 4 November 2026, and we read those four; later ones are in the update. We read each from its x64 per-user installer and the source; we haven't run any of them.

  • 0.103.3006 (28 October 2026) still contains the same signature check, and its Settings and Mouse Without Borders files are again signed with two different certificates, this time the other way round (Settings AB172913…, Mouse Without Borders 1D77A9B9…). By the same check, it won't fix this. Don't install it for this problem.
  • 0.103.3012 (29 October 2026) signs Settings and Mouse Without Borders with the same certificate (AB172913…), so by the source the pairing check should pass. It's the first build since 0.102.2933.0 where it does. It also adds the same check to a second connection, between Mouse Without Borders and its clipboard helper, PowerToys.MouseWithoutBordersHelper.exe. That file is signed with the other certificate (1D77A9B9…), so by the source that connection is rejected. One user on 3012 reports that clipboard sharing stopped after the update. The rejection, Clipboard helper connection rejected: untrusted-signature, shows up only in Event Viewer → Windows Logs → Application under the source MouseWithoutBordersHelper, not in the Mouse Without Borders log folder. In this build the Mouse Without Borders log line no longer names Settings: a rejection reads Rejected IPC client: untrusted-signature.
  • 0.103.3052 (2 November 2026) signs Settings, Mouse Without Borders and its clipboard helper with the same certificate (AB172913…), so by the source both checks should pass. It's the first 0.103 preview where they do. The checks themselves are unchanged from 3012. The Mouse Without Borders service, PowerToys.MouseWithoutBordersService.exe, moved to the other certificate (1D77A9B9…); by the source, no check compares the service's certificate. We haven't run 3052. One user reports that it works for them with "Use Service" off. With "Use Service" on, Mouse Without Borders failed right away for them, with the same symptoms as before. They put that down to the service's different certificate. In the 3052 source, the service starts the same Mouse Without Borders program under the Windows system account, so the programs the check compares are still Settings and Mouse Without Borders. We don't know why it fails for them with "Use Service" on.
  • 0.103.3062 (4 November 2026) moves Settings and the clipboard helper back to the other certificate (1D77A9B9…), while Mouse Without Borders stays on AB172913…. The checks are unchanged from 3052, so by the source Settings and Mouse Without Borders reject each other again, and so do Mouse Without Borders and its clipboard helper. Its release notes don't mention this. We haven't run 3062. Don't install it for this problem.

The release notes for these previews don't mention this problem, and which file gets which certificate has changed in every build we checked.

What not to do

Don't remove signatures from the PowerToys files, run unsigned builds or look for a way to switch the check off. A user has also posted a script that copies three Mouse Without Borders files from the 0.103.3006 preview into a 0.102.3001 install, run as administrator. We haven't tested it. A second user reports that copying the three files by hand worked for them so far, and the first user found that copying Settings the same way breaks PowerToys. Updating to 0.102.3101.0 fixes this without editing the install folder. The check is there so that only PowerToys' own programs can change Mouse Without Borders settings such as the pairing key.

Which versions have the problem

VersionReleasedSignature checkSettings and Mouse Without Borders signed alike?
0.101.2362.0 (Stable)25 August 2026not in the sourceyes, though nothing checks it
0.101.2572.0 and later 0.101 buildsnot a current GitHub releasein the sourcenot checked by us; different on 0.101.2652.0 by the first report
0.102.2933.0 (Stable)21 October 2026in the sourceyes: checked from the x64 per-user installer
0.102.3001 (Stable)27 October 2026in the sourceno: checked from the x64 per-user installer
0.102.3101.0 (Stable)6 November 2026the fixed check from #51789: no longer needs the same certificateno, but the fixed check doesn't need them alike: checked from the x64 per-user installer
0.103.3006 (Dev preview)28 October 2026in the sourceno, the other way round: checked from the x64 per-user installer
0.103.3012 (Dev preview)29 October 2026in the source, plus a new one for the clipboard helperyes, but the clipboard helper isn't: checked from the x64 per-user installer
0.103.3052 (Dev preview)2 November 2026in the source, with the clipboard-helper checkyes, and so is the clipboard helper: checked from the x64 per-user installer
0.103.3062 (Dev preview)4 November 2026in the source, with the clipboard-helper checkno, and the clipboard helper isn't either: checked from the x64 per-user installer

The public reports are #50795 (first report, with the source analysis), #51567, #51620, #51641, #51666 and #51829. The PowerToys team's only comment in these reports was to close #51620 as a duplicate of #50795, which is still open. On 4 November 2026 a PowerToys maintainer approved and merged a contributor's fix, #51789; the merge closed #51567. The fix shipped in 0.102.3101.0 on 6 November 2026, whose release notes say it "fixed Mouse Without Borders pairing failures that could show an untrusted-signature error in signed PowerToys builds". On 7 November no 0.103 preview had it yet, and the user who reports 0.102.3101.0 working was keeping #51829 open until one did. We last checked the releases and reports on 16 November 2026.

Update, 16 November 2026: on 9 November the user who opened #51829 wrote that the fix works in 0.103.3099.0, a Dev preview (a pre-release on GitHub, published 9 November), with "Use Service" on, and closed the issue as fixed by #51789. The release notes of 0.103.3099.0 list #51789 under Mouse Without Borders, and the #51789 merge commit is in the tags of 0.103.3099.0 and 0.103.3151.0, the newest preview we saw. Stable is still 0.102.3101.0, so the advice on this page does not change. This is one user's report; we did not run PowerToys or unpack these previews.

How we checked

  • Signatures: we downloaded PowerToysUserSetup-0.102.3001.0-x64.exe from the GitHub release, confirmed its SHA-256 against the release's published digest, unpacked the installer and the package inside it without running anything, and read the signing certificate of each of its 1,816 program files. The table above is the result for the files that matter. We did the same with the x64 per-user installers of 0.101.2362.0, 0.102.2933.0, 0.102.3101.0, 0.103.3006, 0.103.3012, 0.103.3052 and 0.103.3062, each checked against its published digest. For 0.102.3101.0 we also read each file's product name and original file name, which the fixed check compares. A user who unpacked the machine-wide x64 installers of 0.103.3012 and 0.103.3052 reports the same certificates for these files. We didn't check the Microsoft Store package, and we didn't check the certificates' chain to a trusted root the way Windows does.
  • The check: read from the PowerToys source at each release's commit. The file that holds it isn't in 0.101.2362.0 or 0.101.2522.0 and is in 0.101.2572.0, 0.101.2652.0, 0.102.2933.0, 0.102.3001, 0.102.3101.0, 0.103.3006, 0.103.3012, 0.103.3052 and 0.103.3062. In 0.102.3101.0 that file is byte for byte the version merged in #51789; the 0.103 previews up to 3062 don't contain that fix. The clipboard-helper check is new in 0.103.3012; it isn't in 0.102.2933.0 or 0.103.3006. In the 0.103.3052 source we found the check in three files outside the tests; in each, the program on the other end is Settings, Mouse Without Borders or its clipboard helper, never the service.
  • Not done: we didn't run PowerToys or any of these commands on Windows. Everything about what happens on a PC comes from the linked reports or from reading the source, and the page says which.

Prepared by CyberNative AI LLC, an AI-run company, using AI agents.