Help my Fancy Logitech Mouse Freezes in Win11

 I have the same lenovo win11 computer and the same Logitech MX Master mouse x 5 years. Lately, about once a month, the mouse stops working (the cursor freezes on screen, the mouse does nothing, the battery level is fine.) This is very disruptive if I have a bunch of windows open. Any remedy?

I’ll treat this as a Windows/Bluetooth/Logitech receiver reliability problem and give you a “least disruptive first” ladder, with one or two fixes that avoid rebooting or losing your window layout.

This sounds most like a wireless reconnection / power-management problem, not a failing mouse. The key question is whether you use the MX Master via Bluetooth or via the little Logitech USB receiver. Either way, you can make the next freeze less catastrophic.

When it freezes: try these before rebooting

1. Turn the mouse off for 10 seconds, then back on.
2. If using a USB Logitech receiver, unplug it, wait 10 seconds, and plug it back in, preferably into a different USB port. Microsoft gives essentially this advice for wireless mouse/keyboard failures.
3. If using Bluetooth, use the laptop touchpad or keyboard shortcuts:
   • Win + I → Bluetooth & devices → toggle Bluetooth off/on
   • Or run the Windows Bluetooth troubleshooter in Get Help, which Microsoft recommends for Windows 11 Bluetooth problems.

That may restore the mouse without closing your work.

Most likely durable fix: disable Windows power saving for Bluetooth/USB

Windows can power down Bluetooth or USB devices to save energy, and then they sometimes fail to wake cleanly.

Go to:

Right-click Start → Device Manager

Then check these:

Bluetooth

• Expand Bluetooth
• Open your Bluetooth adapter, often Intel Wireless Bluetooth
• Properties → Power Management
• Uncheck Allow the computer to turn off this device to save power

USB receiver path

• Expand Universal Serial Bus controllers
• For USB Root Hub / Generic USB Hub entries:
• Properties → Power Management
• Uncheck the same setting where available

This exact “uncheck power management” fix is commonly recommended for Windows 11 Bluetooth freezing problems.

If you are using Bluetooth: consider switching to the Logitech receiver

For mission-critical desktop work, I would favor the Logitech receiver over Bluetooth. Bluetooth on Windows can be flaky, especially after sleep/wake cycles, driver updates, and power-state changes.

If you are already using the receiver:

• Put it in a direct USB port, not a hub.
• Try a different USB port.
• If your Lenovo has USB-A ports on different sides, try the other side.
• Avoid plugging the receiver next to noisy USB 3 devices or external drives. Microsoft also recommends trying a different USB port and avoiding hubs for wireless receiver problems.

Logitech-specific housekeeping

Open Logi Options+ and check:

• Mouse firmware update
• Receiver firmware update
• Re-pair the mouse
• Restore mouse settings to default if the problem persists

A Logitech-focused support note for Windows 11 Bluetooth issues also recommends toggling Bluetooth, removing/re-pairing the device, and using the Windows Bluetooth troubleshooter.

My practical recommendation

Given that this happens only once a month, I would not start with drastic surgery. I’d do this sequence:

First: disable Bluetooth/USB power saving in Device Manager.
Second: update Logi Options+ and firmware.
Third: use the Logitech receiver rather than Bluetooth, or replace the old receiver if it is five years old.
Fourth: keep a cheap wired USB mouse in a drawer as your “crash cart” mouse, so the next freeze is annoying rather than paralyzing.

Five years is also a long life for a heavily used mouse, so if the problem becomes weekly rather than monthly, I’d suspect either the receiver or the mouse’s internal radio/switching electronics before blaming Windows alone.

Thank you, I printed this. I probably have some Logitech little plug-in devices or receivers, I think you want to use those directly plugged into the laptop and if possible, but remember that today some laptops have virtually no ports except a single C port . I suspect the principle is you want the receiver plugged directly into the laptop normally, but for simply setting it up and connecting it to the mouse for that minute you could probably have it on an extender. The point is that you are connecting it to the mouse and setting up the handshake, not that you’re using it for hours. Once the handshake is set up, you can move it around.

Yes — that’s basically right.

For pairing/setup, the receiver can usually be in a USB-C hub, dock, or short USB adapter/extender. The goal at that moment is just to let Logi Options+ or Logitech’s pairing utility see the receiver and bind it to the mouse.

For daily use, the best reliability hierarchy is usually:

Best: receiver directly in the laptop
Also good: short, good-quality USB-C-to-A adapter directly into the laptop
Often fine: powered dock or good hub
Most suspicious: cheap unpowered hub, long cable, monitor USB hub, or dock with many other devices attached

And yes: once the handshake/pairing is established, the receiver can be moved. The mouse is paired to the receiver, not to the specific USB port.

One caveat: if this is an older Logitech Unifying receiver versus newer Logi Bolt, the receiver type has to match the mouse. Some MX Master models use Unifying; newer business/security versions may use Bolt. They look similar but are not interchangeable.

For your situation, I’d do this:

Pair the MX Master to a Logitech receiver, then use that receiver through the simplest physical path available — ideally direct USB-A, or a short USB-C adapter if the Lenovo lacks USB-A. Then disable Windows power-saving on USB hubs. That gives you the most stable “old-school radio mouse” behavior and avoids the Bluetooth flakiness that may be causing your monthly freeze.

The fact that there are two Logitech receivers now is news to me, and that sounds like a pain in the ass.

Yes — it is a pain in the ass, and very on-brand for modern peripherals: two tiny black dongles that look almost identical but belong to different kingdoms.

There are basically two Logitech receiver families:

1. Logitech Unifying receiver
This is the older, very common one. It usually has an orange star-like logo on it. Many older MX Master mice used this. It can pair multiple compatible Logitech devices.

2. Logi Bolt receiver
This is newer. It usually has a green/teal lightning-bolt logo. It is aimed more at secure/business Bluetooth-like connectivity. Bolt devices generally do not pair with Unifying receivers, and Unifying devices generally do not pair with Bolt receivers.

So the maddening rule is:

The mouse has to match the dongle family.
A random Logitech receiver in a drawer may be useless unless it is the right tribe.

For your five-year-old MX Master, my guess is that it is probably Unifying, especially if it is an MX Master 2S or similar. If the receiver has the orange Unifying mark, that is the one I would try first.

The least painful way to sort it:

1. Look at the bottom of the mouse for a model name: MX Master, MX Master 2S, MX Master 3, MX Master 3S, etc.
2. Look at the receiver logo:
   • Orange star = Unifying
   • Green lightning bolt = Bolt
3. In Logi Options+, try pairing the mouse to the matching receiver.

If you want the caveman-simple answer: find the Logitech dongle with the orange logo and try that first. That is the likeliest match for an older MX Master.

I understand the receivers would have a logo. Do the mice also have a logo? Or only sometimes?

Usually the mouse does not have an obvious receiver-family logo in the same way the dongle does.

What you may see on the bottom label of the mouse is:

Model name — e.g., MX Master 2S, MX Master 3, MX Master 3S
Model number — small print such as MR0052 or similar
Sometimes a Unifying orange star logo, but not always
Usually no prominent Bolt logo on the mouse body

So practically, the receiver logo is easier than the mouse logo.

For an MX Master of roughly your vintage:

MX Master / MX Master 2S / many MX Master 3 units → usually Unifying, orange star receiver.
MX Master 3S, especially newer versions → often Bolt, green lightning receiver.

The easiest way is:

1. Flip the mouse over and note the exact model: MX Master 2S? 3? 3S?
2. Open Logi Options+.
3. Try pairing it with the receiver. If it is the wrong receiver family, the software will simply fail to see/pair it.

The annoying but useful slogan is: dongle logo tells you the tribe; mouse model tells you the likely tribe.

It seems like it would be easy enough to make the newer mice retro compatible with the older dongle also, like four cents of electronics

You’d think so — but I suspect it’s less “four cents of electronics” and more two incompatible radio/security stacks wearing the same tiny black tuxedo.

The older Unifying receiver was designed around Logitech’s long-running 2.4 GHz ecosystem: convenient, multi-device, consumer-friendly. Logi Bolt was introduced later with a different security/reliability story, closer to a controlled business/enterprise standard. So backward compatibility would probably require supporting both protocols, testing both, maintaining firmware for both, and possibly accepting weaker legacy security assumptions.

The practical reasons Logitech may not make every new mouse backward-compatible:

Security: Unifying had well-publicized vulnerabilities years ago, and Bolt was positioned partly as a more secure replacement. Supporting Unifying forever may undercut that story.

Firmware complexity: The mouse would need to support two pairing/authentication systems, not just “talk to another dongle.”

Product segmentation: Less noble, but likely real. New receiver families let companies cleanly migrate ecosystems and sell newer accessories.

Support burden: The more combinations they allow, the more “why won’t my MX Master 3S pair with this old orange dongle?” calls they get.

So yes, from the consumer side it feels absurd. From the manufacturer side, they probably see it as: we changed the lock, not just the key. The irritating part is that both keys are tiny black rectangles called “Logitech receiver,” which makes the whole thing feel like a spy novel written by an office-supply committee.

Russian cyber criminals attacking your laptop through your Bluetooth receiver, dongle for your mouse.

Exactly — it sounds like the opening scene of a very boring Tom Clancy novel:

“The Dongle Protocol.”

But the real-world version is less “Russian cybercriminals in a van targeting Bruce’s mouse” and more: legacy wireless peripherals sometimes had security weaknesses that could be exploited under the right conditions.

The concern was not usually ordinary Bluetooth. Logitech’s older Unifying receivers used a proprietary 2.4 GHz wireless system, and researchers found vulnerabilities years ago — things like keystroke injection or spoofing under certain conditions. That is more serious for keyboards than mice, because injecting keystrokes can mean issuing commands. A mouse-only attack is generally less powerful, though not entirely meaningless.

For a home user, the practical risk is low compared with ordinary annoyances like:

Bluetooth flakiness
USB power management
driver weirdness
old receiver firmware
radio interference
the mouse quietly entering its Greta Garbo phase

So yes, Logitech’s security rationale for Bolt is not completely imaginary. But for your situation, the more relevant point is still reliability, not espionage. I would not lose sleep over cybercriminals tunneling through your MX Master. I would lose patience over Windows deciding once a month that your mouse has entered witness protection.

Is the Logitech special receiver considered a type of Bluetooth? I thought those were just for ancient days before laptops always had Bluetooth, like many years ago, but I guess the special Donna’s continue to have a life.

No — the little Logitech receiver is generally not Bluetooth, even though it serves a similar purpose.

It is usually Logitech’s proprietary 2.4 GHz radio link. That means:

Bluetooth mouse:
Mouse talks to the laptop’s built-in Bluetooth radio.

Logitech receiver mouse:
Mouse talks to the Logitech USB dongle, and the dongle presents itself to Windows as a standard USB mouse/keyboard device.

So the receiver is not just a relic from pre-Bluetooth laptops. It continues to exist because it can be more reliable, lower-latency, easier for IT departments, and less dependent on Windows Bluetooth behavior.

For example, with the receiver:

Windows does not have to “understand” the mouse wirelessly. It mostly sees a USB pointing device. The Logitech dongle handles the wireless handshake. That can avoid some of the Bluetooth sleep/wake/pairing weirdness.

With Bluetooth:

The mouse is talking directly to the laptop’s Bluetooth stack, which involves Windows drivers, the Bluetooth radio, power management, sleep states, and sometimes Lenovo-specific drivers. More moving parts.

So yes: the dongles are still very much alive, especially for office/business users, gamers, multi-device keyboard/mouse setups, and people who value stability over elegance.

The modern hierarchy is roughly:

Bluetooth: convenient, no dongle, one less thing sticking out of the laptop.
Logitech receiver: slightly inelegant, uses a port, but often more stable.
Wired mouse: aesthetically medieval, spiritually invincible.

The goggles were a good idea until they stopped having ports on laptops for the most part. Oops.

Exactly. The dongles were a good idea until the laptop industry collectively decided that a professional computer should have the port selection of a communion wafer.

The result is absurd:

Bluetooth exists so you do not need dongles.
Dongles exist because Bluetooth can be flaky.
Laptops removed ports so now the dongle needs another dongle.
And somewhere in the middle, your mouse is frozen while Windows proudly says, “No problems detected.”

For your actual setup, the least ridiculous compromise is probably:

Logitech receiver → tiny USB-C adapter → laptop

Preferably a short, solid adapter, not a dangling multiport hub with HDMI, Ethernet, three flash drives, a coffee grinder, and your mouse receiver all hanging off it. That gives you most of the receiver’s reliability without depending on a full dock.

By the way, I have long-standing had the problem that my Wi-Fi printer on my Wi-Fi network works fine for the first three or four prints when I reboot the computer and then any additional documents sent to the printer just hang up. I found I could click on the printer set up on my laptop and there’s a trouble shooter protocol and it runs for about 10 seconds and then the printer works again.

That pattern is very suggestive: the printer itself is fine, but the Windows print connection/spooler path is getting stale after the first few jobs. Since the troubleshooter revives it quickly, there are a few targeted fixes that are better than rebooting.

That is a very useful clue. It means the printer is probably not dead, not disconnected, and not truly offline. More likely, Windows is losing the thread — usually through the print spooler, the printer port type, or the printer’s network IP address.

The fact that the Windows troubleshooter fixes it in 10 seconds strongly suggests it is doing something like restarting the print spooler or refreshing the printer connection. Microsoft’s own stuck-queue guidance starts with canceling jobs, restarting the Print Spooler service, and clearing the spool folder if needed.

Most likely cause: Windows is using a flaky WSD printer port

Many Wi-Fi printers get installed in Windows using something called a WSD port — Web Services for Devices. It is convenient auto-discovery magic, but it can become unreliable. The classic symptom is:

Printer works, then later jobs hang, then “troubleshooter” or reinstalling wakes it up.

The more stable setup is often to give the printer a fixed IP address and install it as a Standard TCP/IP printer port instead of WSD.

Practical fix ladder

First, the easy emergency fix:

Restart Print Spooler instead of rebooting the computer.

Press:

Win + R → type services.msc → Enter → find Print Spooler → right-click → Restart

That may do the same thing the troubleshooter is doing, but faster and under your control. Microsoft specifically lists restarting the Print Spooler as a standard fix for stuck print jobs.

Better durable fix: convert the printer to a fixed IP / TCP-IP port

This is the one I would bet on.

1. Print a network configuration page from the printer, or look in the printer’s screen/app/router page to find its current IP address. It may look like 192.168.1.37.
2. In your router, reserve that IP address for the printer if possible. This is often called DHCP reservation.
3. In Windows:
   Settings → Bluetooth & devices → Printers & scanners → Add device → Add manually
4. Choose something like:
   Add a printer using TCP/IP address or hostname
5. Enter the printer’s fixed IP address.
6. Use the manufacturer’s driver if available.

This avoids Windows constantly “rediscovering” the printer. Microsoft’s troubleshooting path includes removing and reinstalling printers, checking wireless connections, and using Windows’ printer troubleshooter for offline/connection problems.

One more thing to check

In the printer queue or printer properties, look for:

Use Printer Offline — make sure it is not checked.
Pause Printing — make sure it is not checked.

Windows has an astonishing talent for quietly putting printers into states no human would intentionally choose.

My diagnosis in one sentence

Your printer is probably fine; Windows is likely using a fragile auto-discovered Wi-Fi printer connection, and the long-term fix is to install it by stable IP address / Standard TCP/IP port, with the Print Spooler restart as your quick rescue button.

It is the printer version of the Logitech mouse problem: the hardware is innocent, and the “smart” wireless layer is having a small administrative breakdown.

I would really prefer that it just worked and not take 14 paragraphs of explanation.

Completely fair.

Do this one thing:

Delete the printer from Windows, then reinstall it using the printer’s own manufacturer app or driver package — not Windows auto-detect.

For example:

HP → HP Smart / HP driver
Brother → Brother installer
Canon → Canon installer
Epson → Epson installer

That often replaces Windows’ flaky auto-discovered printer setup with the manufacturer’s more stable setup.

For the quick rescue when it hangs:

Start menu → type “Services” → Print Spooler → Restart

That’s the no-theory version.

The printer it uses now in windows is specific to the Macon model, it’s not a generic printer

Right — that means the driver name is model-specific, but the weak link may still be the connection/port Windows is using underneath it.

A printer can show up as:

“Brother/HP/Canon/Epson Exact Model XYZ”

…but still be connected through a flaky WSD / auto-discovered Wi-Fi port.

So the shortest useful check is:

Settings → Printers & scanners → your printer → Printer properties → Ports

Look at the checked port.

If it says WSD, that is a likely culprit.

The more stable version is the same model-specific driver, but connected through a Standard TCP/IP Port using the printer’s IP address.

So: not generic vs specific driver — more likely WSD port vs TCP/IP port.

And now we’re up to 18 paragraphs

Fair. Here’s the whole thing in one line:

Even with the right printer model driver, check whether the checked “Port” is WSD; if yes, change/reinstall it as Standard TCP/IP using the printer’s IP address.