Can you please detail what works and where exactly it fails?

I am having this same issue in build 2433

[quote=hintergrundrauschen post_id=481482 time=1620900910 user_id=13700]
2404 runs fine! :D
[/quote]

Great! ;-)
Thx for confirmation.

2404 runs fine! :D

Thanks!

This issue was fixed as https://www.ventismedia.com/mantis/view.php?id=17812 for build 2403.
We are planning to post 2404 soon, just testing it more before posting.

Ok so obviously the dbgview log fail (c:\synosrc) is related to my synology sync. I deactivated this, the fail is gone but MM still shows no different behavior.

c:\synosrc\dog-builder\source\synosyncfolder\lib\cloud-filter\win-cf\placeholder-info.cpp (54) | Failed to get placholder info. C:\Users\Claude\Music\# MMDB\MM_20210512191717.DB

Wait for event ID :1, delay :0, callstack :

[0512/192321.976:ERROR:shared_image_stub.cc(470)] SharedImageStub: unable to create context
[0512/192321.976:ERROR:gpu_channel.cc(449)] GpuChannel: Failed to create SharedImageStub
[0512/192321.977:ERROR:gpu_channel_manager.cc(767)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.

Sorry for my late reply.
2402 doesn't run either.
Install seems to go fine. Resource Monitor will show heavy CPU load forever.

Dbgview debug log does not show major breakdowns but this fail, repeatedly:
[code]c:\synosrc\dog-builder\source\synosyncfolder\lib\cloud-filter\win-cf\placeholder-info.cpp (54) | Failed to get placholder info. C:\Users\Claude\Music\# MMDB\MM_20210512191717.DB[/code]
Later on it waits forever, repeatedly:
[code]Wait for event ID :1, delay :0, callstack :[/code]

Starting up MM with --enable-logging=stderr --v=1
the command line log shows, endlessly repeating:
[code][0512/192321.976:ERROR:shared_image_stub.cc(470)] SharedImageStub: unable to create context
[0512/192321.976:ERROR:gpu_channel.cc(449)] GpuChannel: Failed to create SharedImageStub
[0512/192321.977:ERROR:gpu_channel_manager.cc(767)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.[/code]

What was left behind. Certain files are considered user files and not removed: https://www.mediamonkey.com/support/knowledge-base/mediamonkey-install-config/how-to-completely-uninstall-mediamonkey/

2401 and 2401 will not run on my bog standard Windows 10 setup. In fact, trying to install them leaves behind junk that prevents the re-installation of 2338 which does run. I have to manually hunt down and remove the components your failed version leaves behind. Aren't you guys supposed to be software professionals?

Sounds like https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=98923
that is being worked on as https://www.ventismedia.com/mantis/view.php?id=17812

Did build 2401 run for you?

I will install the debug version of the beta so see what data will generate.

5.0.1.2402 Beta seems to install fine (on top of existing MM5 release), but starting up the splash screen stays visible forever and nothing ever happens. Going back to the release version, everything is fine. Running on lastest Win 10 pro.