OS = Windows 7 Home Premium 64-bit
Mezzmo version 4.1.3.0 - it is set to run the media server only when the Mezzmo application is running.

My library is spread across multiple hard drives in my media server. Recently, one of them failed and had to be replaced. Though, I wasn't able to do it until the following day. The automatic maintenance schedule is set for 10:00 PM. So, it did run through at least one automatic maintenance while the hard drive was "gone." I replaced the hard drive and restored its contents from backup into the exact same folder and file structure that it had before the crash. I then ran a manual maintenance cycle with it set to update only missing attributes. It has now been running for over a day and a half, and it is only at 23% done. It's either very slow or completely stuck. I can't tell because it's not changing anything in the status display. I went into the options and turned on the diagnostic logging. Then selected File - Exit. With my server setting noted above, this shuts down both the server service and the application. It asked if I wanted to stop the currently running user task, which was the manual maintenance I started. I selected yes and waited. Windows then showed the application as Not Responding, and then it crashed after short wait. Crash dump was created. The link to that file (Mezzmo.exe_1439808259.zip) on my Google Drive account has been shared to your support Email.

Now I have restarted the application. Both it and the service are running. I again started the manual maintenance as above. It has reached about 22% in a few minutes, and now it is very slow again. In the options, it does show that diagnostic logging is turned on, but nothing is being recorded in any of the log directories. Files processed and files updated have incremented at least a couple of numbers while I type this message, but very, very slowly. I again selected File - Exit. It again asked if I wanted to stop the currently running user task, which was the manual maintenance I started. I selected yes and waited. After a few seconds, Windows showed the application as Not Responding, and then it crashed again. The link to that crash dump has also been shared to your support Email.

Throughout all this, no logs were produced at all in the diagnostic logs directory. Please advise.