MediaMonkey forum

For the last year, anytime I try to install a new version of MediaMonkey, I get the following error:

C:\Program Files (x86)\MediaMonkey 5\DeskPlayer.dll

Unable to register the DLL/OCX: RegSvr32 failed with exit code 0x3.

I'm able to click "ignore the error and continue (not recommended)", after which it pops up a second time, and then I click it again and everything's fine.

As far as I can tell there's no obvious functionality of the program that has been impacted but I wouldn't even know what I'm looking for.

My laptop is a Samsung Galaxy Book Go with an ARM64 processor, running Windows 10 Home version 22H2.

I've tried running the installer as administrator, it didn't help.

Hi,

It sounds as if the deskplayer process from an earlier version of MM never shut down correctly on your PC (this issue has since been fixed, but I'm guessing that the file on your machine is from an older version of MMW).

You best bet would be to:
- use ProcessExplorer to terminate the process before installing
- OR reboot your PC before installing

If the process can't be terminated, iobitlocker is useful for terminating files that are locked by another process.

-Rusty

I opened ProcessExplorer and didn't find any MediaMonkey or Deskplayer processes there, and I've rebooted many times over the year that I've had this issue.

I've just ignored it so far and told it to press on with the installation. What if any ill effects should/would I be seeing if this ends up presenting a problem?

Start Explorer as Administrator and then RENAME Deskplayer.Dll -> 1deskplayer.dll that should allow MM to install without error.

Hard to say what the side effect of running an old version of deskplayer.dll would be since we don't know how old the file is and since it's not a scenario that we test. But fyi, deskplayer.dll is the 'microplayer' so if you're not using it, it probably has no effect.

fyi, though (as an alternative to Peke's suggestion), I just noticed that processexplorer can be used to 'unlock' files (in addition to terminating proceses. I've used iobitunlocker in the past, but there are some comments on alternativeto.net that it may not be trustworthy any longer. Details about processexplorer are at: https://www.techadvisor.com/article/731 ... elete.html

-Rusty

Hi,
In addition to @Rusty Comments I also use https://lockhunter.com/download.htm that is also proven to work.

I'm still getting the error with each new installation of MM. As far as I can tell the dll isn't locked at all; I was able to rename it and even delete it freely without starting explorer as Administrator. (I am assuming you are referring to the file that is in the MediaMonkey folder under Program Files, and not another copy somewhere else.)

I tried using LockHunter but I think it might not work on my machine; it gives me an error "Cannot start service. OsError: 1275 - This driver has been blocked from loading". (Though I know of course you're not responsible for that...)

Isn't that error related just to registering the dll? And maybe that the dll itself is already replaced before that error popups?
Whats are the dates on the file? (created and modified)
Does manual registrating the dll works?
Open cmd/terminal as admin, copy command below, and hit enter.
regsvr32 "C:\Program Files (x86)\MediaMonkey 5\DeskPlayer.dll"
Could also try, to first unregister the dll file before registring it again with:
regsvr32 /u "C:\Program Files (x86)\MediaMonkey 5\DeskPlayer.dll"
If still get an error.
WinKey(flag)+R, then type: eventvwr
Then press enter, then look at Windows Logs --> at Application, and and System, and tell what kind of errors you have at the time of installing MM.
What versions of 2015/2017 VC redistributable etc are installed on your machine? Try installing the new version for that.
Got Atmel Studio installed?
If using a other virusscaner then Windows Defender, try turning if temporary off before installing, and see if that helps, perhaps the virusscanner is "looking" at the file at the moment of installing.

For MM devs: whats the DeskPlayer.temp.0 used for?

Aha. Manually attempting to register the DLL gives this:

The Module "C:\PRogram Files (x86)\MediaMonkey 5\DeskPlayer.dll" may not be compatible with the version of Windows that you're running. Check if the module is compatible with an x86 (32-bit) or x64 (64-bit) version of regsvr32.exe.

I'm starting to suspect that this is related to my ARM64 processor.

could you try this version of regsvr32.exe as that is the 32bit x86 version (and regsvr32.exe without the path is for arm64)

Command:
C:\Windows\SysWow64\regsvr32.exe "C:\Program Files (x86)\MediaMonkey 5\DeskPlayer.dll"

And did you try:
Right click mediamonkey exe installer file, properties, compability, and take a look at the "change emulation settings".

I don't have a ARM64 machine, so you might have to make a printscreen for me, for those emulation settings.

CrashMonkey さんが書きました: ↑木 10 17, 2024 6:46 pm could you try this version of regsvr32.exe as that is the 32bit x86 version (and regsvr32.exe without the path is for arm64)

Command:
C:\Windows\SysWow64\regsvr32.exe "C:\Program Files (x86)\MediaMonkey 5\DeskPlayer.dll"

Same result.

CrashMonkey さんが書きました: ↑木 10 17, 2024 6:46 pmAnd did you try:
Right click mediamonkey exe installer file, properties, compability, and take a look at the "change emulation settings".

I don't have a ARM64 machine, so you might have to make a printscreen for me, for those emulation settings.

Any change to those settings results in the installation failing much earlier. Only the default works.

Well lets wait what the dev's has to say about it with this new information. Perhaps they can adjust/modify the dll to support arm64 aswell.

Hi,
Desk Player do not have any value in Win 11 as it it is Task Bar player which do not exist in Win 11.

Perhaps then during install on arm64 system, if error while registering the dll file do not show a popup and just continue with installation? or not try to register it on those systems. Then installation would go flawless.

Hi,
Can you please generate debug log during installation as noted here https://www.mediamonkey.com/forum/viewtopic.php?t=86643 it may help us where MM fail exatly and try to filter things out.

You can send us ZIP-ed debug log in support ticket.

I added this as https://www.ventismedia.com/mantis/view.php?id=21283