MediaMonkey forum

Hi.

I just upgraded to MediaMonkey v4.1.9.1758 RC, but every time I try to open it, it opens momentarily, then shuts down again.

I went back to MediaMonkey v4.1.9.1757 RC, and it works fine.


OS: Windows 10 64-bit.

Same with my installation of 1758; windows 8.1
reinstallation of 1757 does work

No such problem here. Capture a debug log (step 4b) and send to support: http://www.mediamonkey.com/forum/viewto ... ?f=6&t=341

actually I couldn't successfully install 1758 just now...error code 5 cannot replace the previous version file.
I'll send a debug record of that to support
thank you

Just installed 1758; crashes immediately upon start-up. Norton is blocking winamp.exe Suspicious.Cloud
Sent in debug log and .elf

I replaced winamp.exe with previous version, crashes still. No warning from Norton about Suspicious.Cloud; but still crashes immediately.
I deleted d_WMDM.dll from plugins folder as Pavle suggested; still crashes.

I'm having the same issue, on Windows 7. Debug version generated a debug report, which I sent.

Hi, strange,
there was no code change between 1757 and 1758 that could cause this.

The reason for the crash most probably is that the build 1757 somehow wasn't properly closed before installation of 1758, i.e. the files from 1757 has not been completely replaced.
To confirm, try installing of 1758 to another folder than 1757, or uninstall 1757 at first and ensure that the install directory is empty before installing 1758.

Do all that see crashes have Norton installed? http://www.mediamonkey.com/forum/viewto ... =6&t=82231

Ludek wrote:Hi, strange,
there was no code change between 1757 and 1758 that could cause this.

The reason for the crash most probably is that the build 1757 somehow wasn't properly closed before installation of 1758, i.e. the files from 1757 has not been completely replaced.
To confirm, try installing of 1758 to another folder than 1757, or uninstall 1757 at first and ensure that the install directory is empty before installing 1758.

I can confirm that this issue does not occur when doing a portable install.

That said, the issue remains when trying to overwrite the previous installation. I have noticed some peculiar things that I thought could be useful to share as well.

First: After such crashing of MediaMonkey, the task remains running in task manager for quite some time (maybe a minute or so) before disappearing and does not respond to administrator attempts to force kill the process.
Second: After the first crashing, but before the task disappears, if one attempts to open MediaMonkey again, it will hold open this time. In Sysinternals Process Explorer, though, there will be two processes of MediaMonkey.exe running (the currently open one and the one that was going to close but does not until the main instance is closed; the latter appears to remains idle and any attempts of user interaction will prompt an error and the task will remove itself).

I have tried making sure no server is installed or running, waiting for all processes of MediaMonkey to close, running the installation exe as administrator, closing any external programs that could conceivably be interacting with MediaMonkey files, rebooting and trying to install again after each adjustment. None of these has fixed the problem in the main installation.
Oh, and I don't have Norton installed, no. I have MalwareBytes and Windows Defender, but tried disabling those as well.

Yes, my crashes also result in multiple mmw processes running...sometimes after restarts, I see three icons MM on the task tray.

another change noticed about 1-2 weeks ago with different devices; UPNP and wireless sync failed, after working for several months.
UPNP: The MMW Beta server shows successful connection with a device (bluray player); but bluray player shows it cannot complete the UPNP connection, "check settings."
Sync MMA Beta and MMW Beta sometimes failed and sometimes appeared to work,, but when successful, opening the playlist on MMA caused it to crash immediately; and no files were in the playlist.

Can you all confirm that installing MMW as Portable fixes the crashing issues?

There is slight chance it is happening as we updated Signature in 1758 and Antivirus apps reporting that as problematic.

The portable install doesn't crash, but it acts as an entirely new install and does not see my existing library or license (lifetime gold).

Yes Pavle, installing 1758 as portable appears to have fixed crashing issue. I've also been able to use UPNP successfully.
Norton is now reporting it is safe to download and install; ? maybe because I added a rule to allow it?
It doesn't have my settings, but we don't expect it to as it's not accessing the other MMW installations/libraries.

I tried 1758 NOT as portable, installed to another location on hdd; but it starts scanning folders which it doesn't have access to, which renders it useless. It doesn't crash; but I can only shut it down with Task Manager.

1757 is still working.

Spoke too soon...now 1757 is not working. It cannnot access library; I ask it to create new library , and it doesn't start up.
Maybe because I've installed portable 1758 to test; and pre-existing 1757 is still installed in another folder on hdd.