Knowledgebase
MediaMonkey isn't working ( crashes / freezes / won't start )
Updated by Russell Samuels on Jan 16, 2018

There have been reports of instability / crashes / failure to run caused in a few different scenarios:

  1. Some anti-virus apps (Symantec/Norton in particular) will falsely flag MediaMonkey as a risk and close it when it attempts to access the system without providing any explanation. The solution in this case is to contact Symantec/Norton and report a false-positive so that they update the virus definition. A workaround is to re-install MediaMonkey in Portable mode.
  2. Certain third-party apps (SideSync, JIT-V, ...) consume significant amounts of memory triggering errors such as "Not enough storage is available to process this command". This can be resolved by using regedit to modify:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\IRPStackSize
    to a value between 15 and 50.
    More on this at https://windowsinstructed.com/fix-not-enough-storage-is-available-to-process-this-command/ .
  3. If an application firewall such as Zone Alarm or Comodo is installed and configured to prevent keyboard scanning (MediaMonkey monitors the keyboard for various multimedia keys and shortcuts). To solve this, configure your firewall to allow keyboard scanning for MediaMonkey.
  4. Some applications are incompatible with MediaMonkey's skin engine, preventing MediaMonkey from running beyond the splashscreen. To resolve, Go to Tools > Option > Skin and enable 'Override skin theme with Windows system theme'.  Examples of such apps:
    - Windows Blinds.
    - Samsung MultiScreen
    - Vista Transformation Pack
    - AnVir. Uncheck "Show additional icons in the titles of windows" under "Options > Windows Enhancement > System Menu and Dialogs".
    - TeamViewer. Disable Quick Connect, log out of TeamViewer before using MediaMonkey or run the unskinned version of MediaMonkey.
    - RealVNC. Disable Mirror Driver in RealVNC, log out of RealVNC before using MediaMonkey or run the unskinned version of MediaMonkey.
  5. If Quicktime has been corrupted in some manner, it may prevent MediaMonkey from starting up. To resolve this:
    - re-install the latest version of Quicktime from Apple.
    AND/OR
    - Disable the iPhone/Touch plug-in. To do so:
    a) Close MediaMonkey
    b) Rename d_iphone.dll in the \Program Files\MediaMonkey\Plugins folder to d_iphone.dll.off
    c) Restart MediaMonkey.
  6. On some systems with some portable devices (e.g. U3 keys, or Zumodrive) that create a virtual drive, operating MediaMonkey with the device connected has been reported to cause instability. To solve this:
    o Edit the MediaMonkey.ini file to ignore the virtual drive letter of the U3 device:
    In change IgnoreDriveLetters=AB to e.g. IgnoreDriveLetters=ABG
    Where G: is the virtual drive created by the application.
    For information about editing MediaMonkey.ini see:
    http://www.mediamonkey.com/support/index.php?/Knowledgebase/Article/View/16
    o Disable the virtual drive. e.g. turn your U3 drive into a regular USB flash drive, as described at: http://www.u3.com/uninstall/ . Note that you can get much of the same functionality via: http://portableapps.com and http://www.portablefreeware.com
  7. In some cases certain apps may lock the MM.DB file while MediaMonkey is attempting to perform an operation on the database, resulting in corruption in the DB. This can result in MediaMonkey appearing to freeze on startup. This can occur with:
    - Backup applications
    - Folder Lock. Solution is to uninstall (use Truecrypt instead)
    To recover from this problem, do a Clean Install of MMW as described at
    http://www.mediamonkey.com/support/index.php?/Knowledgebase/Article/View/53
    or
    install MMW in Portable mode to a separate folder like c:\MMWTemp and do not import existing database.
    To prevent this problem from recurring you can either:
    i) Set your backup app to exclude MM.DB and MediaMonkey.ini from Automatic Backup
    ii) Ensure that MediaMonkey is closed before backup operations occur - Applian Replay Player. Solution is to uninstall.
  8. There are known conflicts with Zecter ZumoCast. A workaround is to:
    a) Exit Zumocast
    b) Go to the Windows Shell (i.e. type the following in the Windows search bar: cmd)
    c) In the Shell, type: regsvr32.exe /u "C:\Program Files\Zecter\ZumoCast\ShellExt.dll"
    d) Press ENTER then exit the Windows Shell, Run MediaMonkey and ZumoCast
  9. In some cases, MediaMonkey may crash and Windows will show a 'StackHash error'.  This is usually indicative of a system issue, but in some cases may be resolved as follows:
    a) Click on the Start menu and then go to the Control Panel
    b) Click on System Maintenance and then System
    c) Choose Advanced System Settings.
    d) Under System Properties, select Settings from the Performance section at the top.
    e) Click on the Data Execution Prevention tab.
    f) Select “Turn on DEP for all programs and services except those I select”.
    g) Find the MMW executable file ("MediaMonkey.exe" and "MediaMonkey (Non Skinned).exe" )
    h) Select the EXE causing the error and click Open to add it to your DEP Exceptions list.
    i) Click OK to save your new settings.
    j) Restart the system, and the error should not occur.
  10. If you're subscribed to NPR Podcasts and using MediaMonkey 4.1.5 or older MediaMonkey may crash do to a bug in the NPR Podcasts. Either update to MediaMonkey 4.1.6 or disconnect your PC from the internet, start MediaMonkey and unsubscribe from any NPR Podcasts you're subscribed to. After this you can reconnect your PC to the internet.
(1710 vote(s))
Helpful
Not helpful

Comments (0)