Stops working and sometimes doesn't work on start.

[Tape-Worm]

Stops working and sometimes doesn't work on start.

[Tape-Worm]

When it happens again, I'll get the log for you. It seems random, so it can work fine for hours or days and then die.

[sw3103]

The logs haven't revealed a great deal, but I have noticed a small anomaly where the _autoPauseTimer was allowed to go over the specified 5 seconds, and was still running whilst Move Mouse was performing the actions. I am not sure at this moment whether this is the cause or a symptom of the issue.

I have left Move Mouse running with your exact configuration on a VM to see if I can reproduce the issue.

Thanks for your patience.

[sw3103]

Hi,

Could you please send me the log file along with the times these events occurred?

[email protected]

Thanks

[rgagnon24]

I have this same issue. I noticed it seems you have to click on the mouse's face once after the program starts to get the timers to engage, but it does just stop working after some random amount of time.

Where would the log file be found? (Using v4.16.3)

Also... 80MB Memory usage seems excessive for what this does

[sw3103]

I have this same issue. I noticed it seems you have to click on the mouse's face once after the program starts to get the timers to engage, but it does just stop working after some random amount of time.

Where would the log file be found? (Using v4.16.3)

Also... 80MB Memory usage seems excessive for what this does

https://github.com/sw3103/movemouse/wiki/Troubleshooting

[Tape-Worm]

Finally! I have your log, I've uploaded it to my website, you can grab it from this link:
https://www.tape-worm.net/public/MoveMouseLog.zip

It stopped working around 9-9:30 AM (MST) this morning (2024-04-02).

[sw3103]

Hi Mike,

Thanks for the logs. I have been away for a couple of weeks hence the lack of response.

I'll have a look soon and hopefully see if I can spot the issue.

[Tape-Worm]

Hi Mike,

Thanks for the logs. I have been away for a couple of weeks hence the lack of response.

I'll have a look soon and hopefully see if I can spot the issue.

No worries or rush. It's probably just all in my head, but adding blackout times seems to have helped a bit (I still get the problem, just not as frequently).

[sw3103]

It's been running faultlessly for nearly six days now. How long did it normally take for you to see the issue?

[Tape-Worm]

Sometimes it'd screw up every day, other times it took a week or more.

[VasaXter]

I have similar issue, MM won't resume the work. When logged, it look like it keeps resseting the counter.
I had this issue starting like month and something ago, but when I started logging it magically started behaving properly.
With new version it goes like this for whole time. (setting is move each 60s, autopause, sesuem after 90s)
Tried to change various settings, running MM as admin, nothing helps

2024-05-10 11:05:04.076 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:04.327 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:04.578 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:04.828 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:05.079 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:05.330 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:05.580 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:05.830 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:06.081 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:06.331 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:06.582 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:06.832 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:07.083 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:07.333 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:07.584 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:07.834 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:08.084 [DBG] _autoResumeTimer_Elapsed 00:00:00.0160000
2024-05-10 11:05:08.335 [DBG] _autoResumeTimer_Elapsed 00:00:00.0160000
2024-05-10 11:05:08.585 [DBG] _autoResumeTimer_Elapsed 00:00:00.0160000
2024-05-10 11:05:08.836 [DBG] _autoResumeTimer_Elapsed 00:00:00.0160000
2024-05-10 11:05:09.086 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:09.337 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:09.588 [DBG] _autoResumeTimer_Elapsed 00:00:00.0160000
2024-05-10 11:05:09.839 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:10.090 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:10.340 [DBG] _autoResumeTimer_Elapsed 00:00:00.0160000
2024-05-10 11:05:10.590 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:10.841 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:11.092 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:11.343 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:11.594 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:11.846 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:12.097 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:12.347 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:12.598 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:12.848 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:13.099 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:13.349 [DBG] _autoResumeTimer_Elapsed 00:00:00
2024-05-10 11:05:13.600 [DBG] _autoResumeTimer_Elapsed 00:00:00.0150000
2024-05-10 11:05:13.850 [DBG] _autoResumeTimer_Elapsed 00:00:00.0150000
2024-05-10 11:05:14.101 [DBG] _autoResumeTimer_Elapsed 00:00:00.0150000
2024-05-10 11:05:14.351 [DBG] _autoResumeTimer_Elapsed 00:00:00.0150000
2024-05-10 11:05:14.601 [DBG] _autoResumeTimer_Elapsed 00:00:00.0150000
2024-05-10 11:05:14.852 [DBG] _autoResumeTimer_Elapsed 00:00:00.0150000

[sw3103]

I have similar issue, MM won't resume the work. When logged, it look like it keeps resseting the counter. I had this issue starting like month and something ago, but when I started logging it magically started behaving properly. With new version it goes like this for whole time. (setting is move each 60s, autopause, sesuem after 90s) Tried to change various settings, running MM as admin, nothing helps

2024-05-10 11:05:04.076 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:04.327 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:04.578 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:04.828 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:05.079 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:05.330 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:05.580 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:05.830 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:06.081 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:06.331 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:06.582 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:06.832 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:07.083 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:07.333 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:07.584 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:07.834 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:08.084 [DBG] _autoResumeTimer_Elapsed 00:00:00.0160000 2024-05-10 11:05:08.335 [DBG] _autoResumeTimer_Elapsed 00:00:00.0160000 2024-05-10 11:05:08.585 [DBG] _autoResumeTimer_Elapsed 00:00:00.0160000 2024-05-10 11:05:08.836 [DBG] _autoResumeTimer_Elapsed 00:00:00.0160000 2024-05-10 11:05:09.086 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:09.337 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:09.588 [DBG] _autoResumeTimer_Elapsed 00:00:00.0160000 2024-05-10 11:05:09.839 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:10.090 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:10.340 [DBG] _autoResumeTimer_Elapsed 00:00:00.0160000 2024-05-10 11:05:10.590 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:10.841 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:11.092 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:11.343 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:11.594 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:11.846 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:12.097 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:12.347 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:12.598 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:12.848 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:13.099 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:13.349 [DBG] _autoResumeTimer_Elapsed 00:00:00 2024-05-10 11:05:13.600 [DBG] _autoResumeTimer_Elapsed 00:00:00.0150000 2024-05-10 11:05:13.850 [DBG] _autoResumeTimer_Elapsed 00:00:00.0150000 2024-05-10 11:05:14.101 [DBG] _autoResumeTimer_Elapsed 00:00:00.0150000 2024-05-10 11:05:14.351 [DBG] _autoResumeTimer_Elapsed 00:00:00.0150000 2024-05-10 11:05:14.601 [DBG] _autoResumeTimer_Elapsed 00:00:00.0150000 2024-05-10 11:05:14.852 [DBG] _autoResumeTimer_Elapsed 00:00:00.0150000

This is a separate issue. Something on your workstation (unlikely Move Mouse itself) is simulating user activity and resetting the idle time, which will not Move Mouse to automatically resume. I have seen this issue in the past which was due to a bug in some NVIDIA software.

My advice would be to run the script from the following section of the Troubleshooting guide to help you identify what may be the culprit:

https://github.com/sw3103/movemouse/wiki/Troubleshooting#idle-time

Presumably your idle time will be constantly getting reset. Try closing applications one at a time (look for the background ones running in your system tray), pausing between each one to see if your idle time is allowed to increase.

[Tape-Worm]

I've updated to the latest version (4.18, I wasn't aware it had been updated). I'll let you know if I run into the same problem.

And I'm a total dumbass. I didn't think to tell you I'm running MouseMove under a Hyper-V Windows 11 Pro VM. Sorry about that, I really should have mentioned that earlier. Totally slipped my addled old man brain.

[techtalk722]

*** BEGIN EDIT ***

I tried downgrading to 4.17 and that seems to have fixed the issue. It's been running for about 30 minutes now and nothing is going to sleep. The log file is still showing action every 30 seconds, but the mouse actually moves. Something changed in the newer versions.

*** END EDIT ***

Hi. I'm not sure if my issue is the same thing or not, but the symptom seems to be the same.

This started happening to me on a newly built Win10 VM. I have used MM for years (thank you, by the way) in other VMs as a way to maintain a presence status in Teams and keep the screen active while I do work in other VMs. I have previously used it in Win10 and Win11 with no issues. This time, Windows and MM don't want to work together. I am using the most current version, 4.18.2.

I have installed it and configured it as I have always used it, using a schedule during work hours with a stealth movement. I have also tried just leaving it with the default settings, but nothing seems to make it actually move the mouse. I've even configured actual slow movement (to see the mouse move), but the mouse just never moves. The screensaver will come on and Teams will revert to an 'away' status.

I have run the troubleshooting PS script and it runs for long periods of time with nothing ever resetting the idle state running in the script, even while MM is running. While watching the verbose log output, I can see it run every 30 seconds, but again, the mouse doesn't seem to actually move. Below is a sample from today of what is being posted to my log file every 30 seconds.

If this is the same issue and there's anything I can do or provide, please let me know. I love this tool.

2024-06-07 14:19:13.790 [INF] PerformActions Interval
2024-06-07 14:19:13.790 [INF] PerformActions _firstPass = False
2024-06-07 14:19:13.790 [DBG] BlackoutIsActive False
2024-06-07 14:19:13.790 [INF] CurrentState Executing
2024-06-07 14:19:13.790 [DBG] OnMouseStateChanged Executing
2024-06-07 14:19:13.790 [DBG] _vm_MouseStateChanged Executing
2024-06-07 14:19:13.792 [DBG] StopAutoPauseTimer
2024-06-07 14:19:13.792 [DBG] Action_PropertyChanged IntervalExecutionCount
2024-06-07 14:19:13.792 [DBG] Settings_PropertyChanged Actions
2024-06-07 14:19:13.792 [DBG] SaveSettings C:\Users\Switchkat\AppData\Roaming\Ellanet\Move Mouse\Settings.xml
2024-06-07 14:19:13.793 [DBG] Settings_PropertyChanged Actions
2024-06-07 14:19:13.793 [INF] Execute MoveMouseCursorAction | Name = | Distance = 10 | Direction = None | Speed = Normal | Delay = 5 | Trigger = Interval | Repeat = True | RepeatMode = Forever | IntervalThrottle = 1 | IntervalExecutionCount = 45 | InterruptsIdleTime = True
2024-06-07 14:19:13.793 [INF] Start
2024-06-07 14:19:13.793 [DBG] BlackoutIsActive False
2024-06-07 14:19:13.793 [DBG] StopAutoResumeTimer
2024-06-07 14:19:13.793 [INF] ExecutionTime 14:19:43
2024-06-07 14:19:13.793 [INF] CurrentState Running
2024-06-07 14:19:13.793 [DBG] OnMouseStateChanged Running
2024-06-07 14:19:13.793 [DBG] _vm_MouseStateChanged Running
2024-06-07 14:19:13.803 [DBG] StopBlackoutTimer
2024-06-07 14:19:13.803 [DBG] StartAutoPauseTimer
2024-06-07 14:19:13.803 [DBG] StopAutoPauseTimer