it started off gradually, but now every time I run the program and leave it running it becomes unresponsive requiring me to go open task manager and force close the program to get it to run a task like checking for missing episodes, or moving new media to media storage locations and it'll run good for a moment but if I come back an hour or so later to see if it's found any new episodes and it's there running but not doing anything and completely unresponsive. It's running on a Windows 10 21H2 OS Build 18044.1766 VM running on a Dedicated server with Dual Processors, 1 processor is dedicated for the VM along with 32GB RAM. No other programs are unresponsive, The OS isn't unresponsive. The Entire systems only runs CPU less than 5% and RAM less than 10%. In short, it's not a hardware or OS issue. has been an ongoing intermittent issue but after the last update has become a daily (Multiple Times Daily) type of issue where I must force close it to use the program but only a temporary fix. An hour can go by, and I check it again and can't get it to do anything until I force close it and restart it. I've uninstalled it, re installed it. Didn't fix it. I figured it may be due to the size of my Library. I removed my library and only added a small folder with limited media, and it still freezes up. I've tried it on various machines but getting the same results when I've used the program for years and leave it running 24/7 and haven't had any serious issues until recently where the program is useless if left running more than an hour as it'll freeze and do nothing. I started the program and in the time it took me to write this is all the time it took. I captured my screen and will share a link to a video showing what happens. https://www.youtube.com/watch?v=cdZxTKc4zmw

also experiencing this error, usually happens when processing downloads of movies and getting to the end of the task.

also freezing when manually fetching metadata for movies/tv

running on Windows 11, Hyper-V virtual box

I am also experiencing this issue. Windows 10 Pro.

I've seen in a similar thread someone suggested making sure the Show extended T.V. show statuses (can't be slow) should be unchecked as it may cause issues. I made sure that's unchecked under General settings and never been a setting I've enabled. I've still been experiencing this but a couple of days after posting it hasn't been happening constantly and I've made no changes.

I've observed that when this happens, MCM cannot be moved, resized or minimized. Shutting down via task manager is the only way to stop it.

Glad to see this is not just happening to me. Thanks for posting the issue on GitHub

Glad to see this is not just happening to me. Thanks for posting the issue on GitHub

Yea, I've still been experiencing it. Not as often though. It was happening within 30 minutes of starting the program constantly, sometimes within like 5 minutes. But the last week or so maybe. shortly after I posted this It hasn't been occurring constantly. But it's definitely happening too often. I've uninstalled, then re-installed it. I've spun up a clean windows VM on one of my servers to see if it was something on that specific machine and it still happens so I dont think it's something on my end unless it's a setting I'm overlooking causing it.

FWIW, I'm having the same kind of issue, and it's been happening for a while now. Any assistance to either roll back to the prior version, or help to get it resolved in the current (or a new version) would be greatly appreciated.

And just to add my observations. MCM appears to be completely frozen and unresponsive. Yet when I use Task Manager to end the process, it appears to receive a request to shut down, and MCM appears to clean up and then close down. So there's some process in MCM that's hanging up the UI, but it'll still receive other requests in the background.

I'm not sure if I fixed mine 100%, yet. Here's what I found: I went to my server folders and found that the properties were "Read Only." I changed it to "Read and Write," and so far, MCM hasn't frozen. I'll update if that changes. Unsure why the file properties changed in the first place, tho...