elibarzilay

I have two issues with start11 on a specific laptop. (A second laptop + desktop do not have this problem.) The first issue is that I have no "Start11" start menu entry. Not when searching for it via typing, and not in the full list. Using the windows start menu also doesn't have it. When I use "Force not touch mode device", the windows builtin icons + time are all displayed at an offset towards the bottom and half visible. Using "force touch" o

I don't, and never had.

[quote who="sdRohan" reply="41" id="3967597"] Ill do you one better, MS update caused it to flag Chrome itself. You are saying we should fix what MS breaks. We have built an entire software division around that [e digicons];)[/e] Let me know the result of running the bat file when you can, please. [/quote] The question is whether you can do something about it. In the case of just resetting the fi

[quote who="sdRohan" reply="38" id="3967328"] Quoting elibarzilay, reply 37 I don't believe your statement here, that OS updates do not frequently cause apps that were working before to have issues after, is a commonly shared belief. [/quote] I didn't say anything about frequency of breakages.&nbs

As I said, using the KVM feature is already so minimally useful that I don't see much point in fighting my firewall or whatever to keep that working. [quote who="sdRohan" reply="36" id="3967271"] I know you honestly believe it to be a problem \ design issue with the app [/quote] If it is a firewall problem, then there is certainly a problem with the app: how many apps would you install if they require you to fiddle with your f

Until yesterday, I have been using the KVM feature, and it worked fine. The only thing that changed is that my master desktop was updated to Win 24H2 -- and now the KVM window shows fine, but no input goes through: neither mouse nor keyboard interaction. Related: Multiplicity provides three ways to connect: Seamless: fails for me if the remote reboots, or the network goes down for a bit. Seamless display: fails after a few minutes (same as above).

JFYI, this is the same problem that I reported, and it was never resolved.