Windows 10 doesn't respond to CTRL-C after a while

[b.e.wilson]

My running instance of CumulusMX (3038) on Windows 10 will stop responding to a CTRL-C command after a while, typically a more than a week after the instance is started. The operation of the instance is perfectly normal at the time. The instance will still respond to a killtask command issued by the task manager. This behavior has been present since at least v3026.
On two occasions the instance messed up, and stopped updating the website. It would not respond to either a killtask command nor to a CTRL-C. I had to stop the instance by rebooting.
Sorry I have nothing better to help diagnose the problem.

[steve]

I don't run MX for any length of time on Windows, but I do run it for long periods on Linux, and I've never had that problem. I've not heard of anyone else having the problem. Perhaps a thread has hung and refuses to die. Does the diags file show anything at all in response to the CTRL-C?

[b.e.wilson]

The logs only show what appears to be normal operation until one CTRL-C, kill process or shutdown command closed it. The one it saw was a kill process command from the task manager. It never appeared to "see" the CTRL-C.
I'l keep an eye on it, wait a week and try again to stop the process with a CRTL-C, see if I can duplicate the problem.

[water01]

I am running CumulusMX, admittedly on Windows 7, but it is running 24/7 and for long periods of time (usually between Windows updates) and I do not have this problem.

[duke]

I am running CumulusMX, admittedly on Windows 7, but it is running 24/7 and for long periods of time (usually between Windows updates) and I do not have this problem.

Ditto on Win10