With 3213, I just had exactly the same experience as by post immediately above.
1) start DebugView
2) Insert CD, MM opens and auto-rips successfully; close MM
3) close DebugView (did not save log)
4) start DebugView again
5) insert another CD to auto-rip
[Unknown to me at this time, there is an orphan MM running]
6) use Task Manager to discover orphan – terminate its process
[MM now continues to launch auto-ripping as expected from step 5]
7) rip CD, close MediaMonkey, create log, close DebugView

I will attach the (much shorter) log which looks like it might have some useful information at the very top. Well, it is not allowing me to attach files and the log is too large to post here… Here is a link:
[shared privately via mantis]

Thanks for reporting, we are investigating the issue as https://www.ventismedia.com/mantis/view.php?id=21976

MediaMonkey 3210 beta – I just got a “hang [b]before [/b]splash screen” (really, an orphan situation). This time the symptoms were slightly different and the “steps to follow” might be a bit more intricate/complete…
0) reboot Windows 10 and do non-MediaMonkey 3210 related “stuff” for 24 hours
1) start DebugView
2) insert “never been seen by MediaMonkey” CDs (6, eventually)
3) the first inserted CD correctly auto starts MediaMonkey as well as the auto-rip upon CD insertion dialog – rip CD
[i][u](From this point on both MediaMonkey and DebugView remain running until specified.) [/u][/i]
4) leaving MediaMonkey and DebugView running, insert the second CD. The auto-rip upon CD insertion dialog [b]fails to open[/b], the CD is properly identified and listed (author, album, title) on the main window. “Rip CD” from the context menu appropriately opens the rip dialog – rip CD
5) CD 3 – exactly the same as step four – eventually ripping CD
6) CD 4 – similar to step four except, this time the “failed to find CD insertion Handler application” dialog pops up. But, again, the CD is correctly identified and the appropriate data (author album title) shows up in the main window. “Rip CD” from the context menu appropriately opens the rip dialog – rip CD
[i][u](From this point on, the “failed to find CD insertion Handler application” dialog pops up.)[/u][/i]
7) at this point, close MediaMonkey and DebugView (did not save the log because the “failed to find Handler” problem is under review by the MediaMonkey team and they do not appear, at this time, to need additional logs).
8) go to bed, leaving the desktop computer running (it is never off, nor does it ever go to sleep)
9) 8 hours later, (forgetting to start DebugView – sorry, no log) insert CD 5. At first, it seems like MediaMonkey does not auto-start but, recalling the problem with orphans from many months ago, I checked with the Task Manager and, sure enough, there was an orphan MediaMonkey process – using the Task Manager I killed this process and saw something I had seen once before…
10) after killing the orphan, the “auto-start” automatically resumed (without me reinserting a CD), and everything proceeded properly: splash screen; main window (appropriately sized and located); rip dialog (appropriately populated, but – the “failed to find Handler” did open).
11) start DebugView
12) CD 6 – exactly like step four

After stress testing 3184 extremely heavily, and a few quick “double-click the desktop icon” starts of the newly released 3200, I also believe that the issue has been resolved. Great job, team!

I have been running 3178 for a couple of weeks now with about 15 restarts and it has not failed to come up. Before now it would have hung about 3 times over that number.
So, yes, for me it seems that the problem has been fixed.
Thanks
Matt

my long running problem of hanging after a first start (after reboot) seems fixed in build 3178, both debug and normal builds. Thanks for continuing to work on this problem until fixed. Doug

Debug allows for capturing debug messages for the developers. It's not needed unless you need to capture debug messages.

[quote=Ludek post_id=530462 time=1763675687 user_id=7319]
Hi,
please test build 3178 posted today: https://www.mediamonkey.com/forum/viewtopic.php?p=530451#p530451
There is a fix for this issue..

Thanks!
[/quote]

Thank you but...
What's the difference between a Debug and a regular build?

I thought you might have this “hanging” problem resolved completely, but…
A few days ago I installed 3178 and tested it exhaustively, everything worked perfectly; except…

I did not get a chance to launch 3178 immediately after successive reboots and I did not get a chance after successive reinstallation. Today (after a Windows update forced a reboot yesterday), I inserted a CD to force 3178 to launch via “auto rip”. The first time it worked perfectly the second time, it appeared not to launch it all – no splash screen, no main window. I ejected the CD and close the tray on it again – same symptom, no splash screen, no main window, no rip window. Starting to wonder, I opened the Task Manager and found that 3178 was (apparently) running already.

At that point I used in the Task Manager to end the 3178 task – surprisingly, the splash screen popped into view briefly followed by the main window (and possibly, the rip window) before the entire task was ended by the Task Manager. I tried again, with the exact same results. I had DebugView running this whole time but it looks like it only got output from the one successful launch.

Ticket #14359: "3178 hanging BEFOR splashscreen" has been successfully submitted

After extreme stress testing I did not experience a problem with “hanging at the splash screen” using version 3178. More details on the ticket including successful logs. I have one more item on my stress test suite – repeatedly uninstalling, rebooting and then reinstalling. With previous versions that was a very reliable trigger for the problem. It might be a couple of days before I report back…

Hi,
please test build 3178 posted today: https://www.mediamonkey.com/forum/viewtopic.php?p=530451#p530451
There is a fix for this issue..

Thanks!

Got the chance to stress test 3175 today – it hung after five starts. I attached a log to ticket #14126 (and also changed the title of this post to reflect the current ticket number).

Hello, I've been running 3174 debug for several weeks, and it is much better than the previous versions (prior to 3171). I had been experiencing a failure rate of 30-50% after a reboot, which improved to a fail rate of 2 out of 30 launches (about a 6% fail rate). something was touched that had a positive impact, but it isn't bulletproof yet. I believe a change was made to the chromium engine (3171) when I saw the improvement. thx, doug

I just installed 3175 beta. I let it launch automatically from the installer – success. I launched it a few times via double click on the desktop icon – all successful. I used your supplied batch file to launch it twice – both successful. I then launched it ~10 times by double-clicking on the desktop icon – again, all successful. I am feeling very hopeful!

Tomorrow, I hope to rip a few CDs automatically via insertion in the drive. I will report the results and, hopefully, close this ticket.

[quote=Peke post_id=530176 time=1761951362 user_id=213]
Hi,
3174 is released, can you recheck?
[/quote]

Done and log sent – attached to aforementioned ticket. The bottom line is that 3174 still suffers the “hang”; but, I may have come up with a method of very reliably reproducing the issue.