See ticket 13679:
https://www.mediamonkey.com/support/?wp ... t-id=13679

Just tested with 3167 - seems even worse.

rusty wrote: ↑Wed Sep 03, 2025 3:02 pm Hi Edgar,

So if I understand correctly:
0 MediaMonkey (standard/non-portable installation) is closed/not running
1 insert CD
--> AutoPlay is triggered and causes MediaMonkey to Launch and play the CD
--> 'Not found' dialog appears and the app is frozen (even as playback continues)

Is that right?

-Rusty

Not quite...

MM not running and not run since last reboot
insert CD to auto-rip
MM hangs at splash

or


MM not running and just nuked with task manager
not found CD still in tray
double-click MM's desktop icon
MM hangs at splash

Ludek had me try something (see ticket 13679) which seems to have cleared the roadblock

Hi Edgar,

So if I understand correctly:
0 MediaMonkey (standard/non-portable installation) is closed/not running
1 insert CD
--> AutoPlay is triggered and causes MediaMonkey to Launch and play the CD
--> 'Not found' dialog appears and the app is frozen (even as playback continues)

Is that right?

-Rusty

Just tried again via auto-launch with CD insertion of another "not found in MusicBrainz" CD - again it hangs; sorry no log.

I just tested 3166 for the first time. On two successive launches via double-clicking on my desktop it hung at the splash screen. I was capturing a log and was planning on attaching it to ticket 21491 but did not do so so opened a new ticket:
Ticket #13679: "3166 hangs at splash screen"

Since the issue with “orphans” ( seems to have been successfully quashed ) was not in evidence on either of these “hangs” but on both of them there was a CD in the tray which was not found in the online database ( seems to be a recurring factor ) that might be a place to start looking.

On a side note, related to CDs not found in the database, MM 2024 has always had a lot of problems (seemingly) related to this factor. I keep wanting to create a new ticket but the problems are just so complicated (and intermittent) – I find it hard to generate a useful bug report – sorry!

Ludek wrote: ↑Sat Aug 09, 2025 9:54 am

Nevertheless, as of the previous version (3162) the “orphaning” issue remains.

It's weird that there have been leftovers even if you haven't started MediaMonkey yet,
could you verify whether you haven't installed MediaMonkey as service in the past?

Options > Library > Media Sharing > [INSTALL AS SERVICE..] ?
Do you have [UNINSTALL SERVICE...] button there instead?

Sorry for the delay...The button reads [Install as service] and I have never even looked at it before. I did not see the hang after installing 3165 but I also did NOT remove MM from my AppData (which seems to acerbate the problem). Next time I will try to remember to clean AppData before installing.

Hey all,
Been following this thread closely—thanks to everyone for sharing detailed logs and updates. I was also facing similar splash screen hangs post v3107, especially on first launch. After updating to 3110, things seem noticeably smoother. Splash screen still lingers a bit longer than older builds, but no hard crashes so far.
Appreciate the devs jumping in and tracking this through Mantis. Fingers crossed the final RC nails it down completely. Will keep testing and report back if anything resurfaces.

Nevertheless, as of the previous version (3162) the “orphaning” issue remains.

It's weird that there have been leftovers even if you haven't started MediaMonkey yet,
could you verify whether you haven't installed MediaMonkey as service in the past?

Options > Library > Media Sharing > [INSTALL AS SERVICE..] ?
Do you have [UNINSTALL SERVICE...] button there instead?

I just installed (well tried to) today's (debug) release (3163) and found an interesting problem. As earlier reported, I too have had problems with hanging at the splash screen and have supplied numerous logs. In this instance, because I was installing a new version, I had not yet started DebugView – although I doubt that it would have provided any useful information <shrug>.

The installation proceeded as normal until it got around to trying to delete a number of the chrome-based DLLs. It suggested that I do so manually. I went ahead and tried to do so, but could not. I opened the Task Manager and found that MediaMonkey 2024 (which had not be started/used in four days) still had a few entries hanging around even though it was closed. Manually task ending these entries resolve the problem of installation. There has been some prior indication that this orphaning of background tasks might be related to the “hanging…” problem (although, in this case it does not seem to have enhanced the likelihood as I have not experienced the problem lately). Nevertheless, as of the previous version (3162) the “orphaning” issue remains.

mopar4x wrote: ↑Mon Jul 21, 2025 4:22 pmUnfortunately it's back for me, too.

Please capture this in a debug log (step 4b): https://www.mediamonkey.com/forum/viewtopic.php?t=86643

2024.2.0.3162

Sorry for delayed response. Problem still exists.

mopar4x wrote: ↑Mon Jul 21, 2025 4:22 pmUnfortunately it's back for me, too.

On what build (Help > About)?

Unfortunately it's back for me, too.

At least for me, it does seem related to processes. When MM launches correctly, 4 processes start up (viewing Task Manager under the Details tab). When it freezes, only 3 processes start up, and then 2 will close after a few seconds and it will hang on the remaining process. If I select "End task" and relaunch, this will usually rinse/repeat. Also, rebooting Windows does not seem to affect this scenario (MM will sometimes freeze on launch right after a fresh boot).

However, I've found that once it's in a frozen state, if I launch a NEW instance of MM BEFORE ending the hung process, and THEN select "End process tree" on the hung item, the new instance of MM will start up all 4 processes and run as normal.

Oddly, I know if it's going to hang or not based on the splash screen; if the corners change from round to square, it just froze.

Please capture this in a debug log (step 4b): viewtopic.php?t=86643

Mine hasn't done it for a while but it did again yesterday. Force quit and restart and it worked OK.