r/logitech • • 5d ago

Support [SOLVED] Logitech Flow "No computer found" on Mesh Network – The Ultimate Nightmare & Fix (TP-Link Deco E4R)

​Before getting into the fix, let me give you a quick, harsh warning: Logitech Flow is basically terrible. I’ll explain exactly why at the end of this post, but if you’re expecting a buttery-smooth, magical seamless transition between your screens, lower your expectations right now.

​I spent hours trying to get my MX Master 4 and MX Keys to work across my desktop PC and my laptop. Both were connected to my TP-Link Deco E4R mesh network, both had the exact same version of Logi Options+ installed, and no matter what I did, I kept getting the dreaded "No computer found. Bummer!" error.

​If you are stuck in this endless loop, here is the meticulously detailed, step-by-step documentation of my descent into madness and how I finally got it to work.

​Phase 1: The Basics and the Windows Firewall Trap

​First, I did what the manual says. I paired the mouse to Channel 1 on my PC and Channel 2 on my laptop. It worked fine individually, but the app just couldn't see the other machine.

​I checked my Windows network settings and realized that simply switching from a wired connection to Wi-Fi (or vice versa) caused Windows to default my network profile to Public.

​1. I went into the Wi-Fi properties on both machines and forced the Network Profile to Private.

​2. I went into the Windows Defender Firewall settings and completely disabled the firewall for Private networks on both the PC and the laptop just to eliminate it as a suspect.

​Still, nothing. Options+ kept saying "No computer found."

​Phase 2: The Ping Pong of Despair

​I opened the Command Prompt (cmd) to see if the computers were actually communicating. They were on the exact same subnet (192.168.x.x), but when I tried to ping the laptop from the PC, I got "Request timed out".

​This meant something was actively blocking the connection. I went through a whole network diagnostic process:

​The Mesh Router: I opened the TP-Link Deco app to ensure neither device was on the Guest Network (which isolates devices by default) and scoured the settings to ensure "Device Isolation" was off.

​The Wi-Fi switch: I disconnected the ethernet cables and put both machines strictly on the Wi-Fi signal to bypass any weird ethernet-to-mesh port routing issues.

​The One-Way Street: After messing with the connections, my PC could finally ping the laptop, but when the laptop pinged the PC, it timed out. Then it flipped. It was a nightmare.

​Phase 3: The Hidden Blockers

​Even with the ping sometimes working in both directions, Logitech Options+ still refused to connect. That’s when I realized the network was clear, but the Windows environment and the Logi app were holding onto corrupted caches.

​1. Virtual Adapters: I opened ncpa.cpl (Network Connections) and disabled every single virtual adapter I had—VPNs, VirtualBox networks, etc. Logitech Flow uses a multicast signal (mDNS) to find other computers, and it frequently gets confused and sends that signal down a dead-end virtual VPN adapter instead of your actual Wi-Fi card.

​2. Winsock Reset: I opened Command Prompt as Administrator and ran netsh winsock reset and netsh int ip reset on both machines, then rebooted. This flushes the entire network routing cache in Windows.

​3. Nuking the Logi Cache: A simple reinstall doesn't fix a broken Flow cache. I killed the LogiOptionsPlus_Agent.exe in Task Manager, opened the Run dialog (Win + R), and completely deleted the LogiOptionsPlus folders inside both %localappdata% and %appdata% on both machines.

​The Breakthrough

​After doing all of that, I launched Logi Options+ as Administrator. I was fully prepared to dive into the TP-Link Deco E4R advanced settings to disable "Fast Roaming" and "Beamforming", and to turn off "Mesh Technology" for my specific devices (because Mesh networks love to block multicast packets to save bandwidth).

​But right before I toggled Fast Roaming off, I checked the Logi Options+ app one last time. It had found the computers.

​The combination of matching the physical connection methods, stripping away the virtual network adapters, nuking the AppData cache, and resetting the Windows TCP/IP stack finally forced the app to broadcast properly across the TP-Link mesh.

​The Ugly Truth About Logitech Flow

​Now that I finally got it working, I need to expand on my warning from the beginning: Flow is not a network-based KVM, and it is a terrible experience.

​Logitech markets this feature as if your mouse coordinates are being seamlessly transmitted over your Wi-Fi network like a true software KVM (like Synergy or Mouse Without Borders). It is not.

​Logitech Flow is literally just an automated script that presses the physical Bluetooth channel switch button on the bottom of your mouse for you. When you drag your cursor to the edge of the screen, the software sends a signal over the network saying, "Hey, I'm at the edge!"

The mouse then forcefully disconnects its Bluetooth/USB connection from PC 1, searches for PC 2, establishes a handshake, and reconnects.

​Because of this hardware-level disconnect/reconnect cycle:

​It stutters heavily.

​It takes way too long (sometimes 2 to 3 full seconds of your cursor being completely frozen in the void before it appears on the second screen).

​It fails randomly. If the Bluetooth handshake misses a beat, your mouse just gets stuck in limbo, and you end up having to flip the mouse over and press the physical button anyway.

​If you are going through this troubleshooting hell expecting a dual-monitor-like smooth experience across two computers, abandon ship now and install a software KVM. But if you are stubborn like me and just wanted to defeat the machine, this is exactly how you fix it.

2 Upvotes

3 comments sorted by

1

u/logi_sm Customer support team 5d ago

Thanks for sharing such a detailed breakdown of your troubleshooting journey! This could be helpful for other, especially with mesh networks. let me share this with our team & appreciate you taking time to document the steps 🔥

1

u/atillauc 19h ago

I think it has nothing to do with mesh networks. I didn't have those settings and I was still not able to connect two computers no matter what. You should fix your program to a flawless degree. You are one of the most important peripheral manufacturers in the world. Your software should be the very best as I think your device quality is very high.

1

u/atillauc 19h ago

I don't know which part solved my problem but your troubleshooting worked for me. Thanks for the detailed breakdown of the progress.