When Multi Commander hangs it is often because it is waiting for some external operation to finished, but it can also be because of a problem within Multi Commander itself.
A 'hang' is when Multi Commander becomes unresponsive. The main user interface no longer accepts any input and you see the Windows message "Not Responding" in the title bar.
What To Do
If Multi Commander actually crashes a mini dump file is created and sent to our crash report system where we can investigate why it crashed.
For a hang this is not done automatically; to be able to find out why it hung, and to be able to fix it, we need to know what Multi Commander was doing when it hung. To do that, we need a dump of the hung 'MultiCommander.exe. process, but you, the user, will need to create that dump and send it to us.
Creating a Dump File
To create a dump file you can use the Windows Task Manager (For Windows XP or Windows Server2003 you have to use a tool like procdump).
Start Task Manager by pressing Ctrl+Shift+Esc (or right-click on the status bar and select "Start Task Manager"), select the Processes tab.
Find the "not responding" MultiCommander.exe process in the list, right-click it and select "Create Dump File".
When the dump file is saved you will be presented with a dialog telling you where the dump file was written.
The path in the dialog must be selected so that you can copy and paste that path into Multi Commander or Windows Explorer to go to that location.
Compress the dump file with Zip/7-zip/Rar. The fastest way is to just right-click the file and select "Send To > Compressed Folder".
Then upload that file to http://multicommander.com/upload and we can take a look and see what Multi Commander was waiting for and why it hung.
If you need feedback on your submitted file, then also post a message in the forum or send us an email.