Open stevemagruder opened 1 year ago
By the way, thank you for this great tool. It's working well enough so that I could uninstall a dedicated app that was giving me even worse issues.
Hi @stevemagruder, thank you for the report! MWB clients should work in all combinations of service/non-service. I have a similar setup as you (win 10 laptop + win 11 desktop) and couldn't reproduce your issue. Can you please try:
The red outline means that the keys are not matched.
OK, here's the steps I took:
OK, so it's now in a state where it's all working. But isn't it peculiar that turning Use Service on would knock out MWB like this, even if re-connectable?
By the way, my Windows versions have changed since the original report: Windows 11 Home 22H2 Build 22621.1778 (director laptop) Windows 10 Home 22H2 Build 19045.3031 (client laptop)
Also, I wanted to note a kind of side issue that I'm not sure is worthy to split into its own. Before successfully running as a service on the Win10 laptop, and I was hard-connected to my Win11 laptop - whenever I moused over to install an app on the Win10 laptop, and the UAC window popped up, MWB stopped working. But now that MWB is running as a service on Win10, that problem stopped happening.
Unfortunately, keeping this running as a service on Win10 isn't something I can keep stable. I've had to roll back my Win10 laptop to not running this as a service.
whenever I moused over to install an app on the Win10 laptop, and the UAC window popped up, MWB stopped working
I'm going to log this as a separate issue, as there's an issue every time UAC pops up.
I just added a third device, this time another Win 11 laptop with the same version of Windows as the first (director) device. I was able to run MWB as a service on that with no issue. So, this seems to be a Windows 10-related issue. No matter what I try, I can't get the service to work on the Win 10 laptop.
I've poked around a bit and from a couple sources, it appears MWB uses .NET Framework 4.0. The version of that on my Win11 laptops is 4.8.09032 and on the Win10 laptop, it's 4.8.04084. Might this be something to consider?
Thanks for the additional info, we'll look into it.
I eliminated one possible cause. I upgraded to a Wi-Fi 6 / Wireless-AX card on the Windows 10 laptop. Doing that fixed random network drops, likely owing to now using a device driver for wireless that's around a month old compared to 4 years old before. Unfortunately, this upgrade did nothing to change the outlines of the above described problem.
Hi @stevemagruder, thank you for the report! MWB clients should work in all combinations of service/non-service. I have a similar setup as you (win 10 laptop + win 11 desktop) and couldn't reproduce your issue. Can you please try:
- connecting to the director machine again using the "Connect" button
- restarting PowerToys on both machines
- pressing "Refresh connections"
The red outline means that the keys are not matched.
Thanks, this just solved my issue!
Doing what I've already done per the same instructions above won't be of assistance. Thanks anyway.
Microsoft PowerToys version
0.70.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
Mouse Utilities
Steps to reproduce
✔️ Expected Behavior
Running MWB as a service on the Win 10 client shouldn't have stopped the cross-border mousing capability. (Or should it have? Am I missing something?)
❌ Actual Behavior
Cross-border mousing stopped working per step 4 above.
Other Software
Windows 11 Home 22H2 Build 22621.1776 (director) Windows 10 Home 22H2 Build 19045.3030 (client)