MediaMonkey Corrupts Windows (Explorer) [#21345]

[dypsis]

I've been testing this for awhile to ensure that it is MediaMonkey that is causing it.

Whenever I run MediaMonkey, Windows starts behaving very oddly. File Explorer stops responding properly. If I double click on a drive, the context menu opens and that's as far as I can go with it. I can't browse any files or folders. All other running programs start behaving oddly or won't work at all.

If I reboot, then Windows and all my applications run fine again.
If I run MediaMonkey again, then all the problems return.

I don't know the exact MediaMonkey version when this started happening, but it's been in the last three versions. It possibly goes back to earlier builds. I haven't tested every build in the past few weeks or more because I've been away.

I've gone back to v2024.0.0.3051, and it's behaving fine and not causing any problems.

Below is the Windows version I am running in case it's caused by a recent Windows update. I know there have been lots of changes recently.

I'm running Windows 11 Version 24H2 Build 26100.2161

[rusty]

Hi dypsis,

This sounds pretty serious, but we're unable to replicate this so far

Can you tell me:
- is the issue triggered just by launching MM (i.e. you don't have to do anything else)?
- does the issue occur when you run the latest MMW in portable mode?
- does explorer stop responding regardless of what you click in it?
- is the issue specific to the MMW debug build?
- could it be that an AV process is somehow responsible (what AV are you using)?
- once you close MM, does the issue in explorer persist until you reboot your PC?

Thanks!

-Rusty

[CrashMonkey]

When you test this.
Open Task Manager first, then mediamonkey.
Then look if there is any process using High CPU, Disk or Memory, and if there is please make a printscreen and post that here.

Also check for disk corruption:
Open Command Prompt (cmd) as Administrator and run/type:
sfc /scannow

Did this machine got reinstalled, since it left manufacture? If so, please say, it might not have all drivers installed properly (graphics/chipset). As windows and windows update does not always provide the right drivers for the system, and some manual installation is needed.

Also Check Event Vieuwer if there are any errors that happen during that time.

[rusty]

dypsis,

One other thing: we made a change in build 3054 that might be related:
https://www.ventismedia.com/mantis/view.php?id=21202

Can you confirm whether the issue occurs in build 3057 ( https://www.mediamonkey.com/forum/viewt ... 17#p521917 ) ?

Thanks!

[dypsis]

Hi dypsis,

This sounds pretty serious, but we're unable to replicate this so far

Can you tell me:
- is the issue triggered just by launching MM (i.e. you don't have to do anything else)?
- does the issue occur when you run the latest MMW in portable mode?
- does explorer stop responding regardless of what you click in it?
- is the issue specific to the MMW debug build?
- could it be that an AV process is somehow responsible (what AV are you using)?
- once you close MM, does the issue in explorer persist until you reboot your PC?

Thanks!

-Rusty

Yes, Rusty. It does sound serious. That's why I made absolutely sure that it was MM 2024 causing it before I created this thread.

Can you tell me:
- is the issue triggered just by launching MM (i.e. you don't have to do anything else)?
Just by launching MM 2024.
- does the issue occur when you run the latest MMW in portable mode?
Yes, I'm running MM 2024 in portable mode. I'm still using MM4 and have it installed.
- does explorer stop responding regardless of what you click in it?
Yes, but as I said in the first post, it's not just explorer that is affected. Explorer may be the cause, but it's not the only thing affected.
- is the issue specific to the MMW debug build?
I'm not using the debug build.
- could it be that an AV process is somehow responsible (what AV are you using)?
I don't use a third party AV or any other third party security software.
- once you close MM, does the issue in explorer persist until you reboot your PC?
Yes. I have to reboot to restore normal operations.

As I said in my first post, I have no issues with 2024.0.0.3051. It's possible that some later versions also work fine, but I haven't had time to go through every test build to identify when this bug was introduced.

[dypsis]

When you test this.
Open Task Manager first, then mediamonkey.
Then look if there is any process using High CPU, Disk or Memory, and if there is please make a printscreen and post that here.

Also check for disk corruption:
Open Command Prompt (cmd) as Administrator and run/type:
sfc /scannow

Did this machine got reinstalled, since it left manufacture? If so, please say, it might not have all drivers installed properly (graphics/chipset). As windows and windows update does not always provide the right drivers for the system, and some manual installation is needed.

Also Check Event Viewer if there are any errors that happen during that time.

1. I don't currently have 2024.0.0.3074 extracted (portable mode). I went back to 2024.0.0.3051 which works fine. I'll have to get back to you on that one when I get around to updating to a later broken version.

2. sfc /scannow is fine.

3. I build my own desktop computers, one of which I'm testing MM 2024 on. I haven't reinstalled Windows since it was built a few years ago. All drivers are installed.

[Peke]

Hi,
Does update to 3057 Triggers same behavior?

If yes, does clean portable install of 3057/3074 in new folders without importing observe same behavior?

I am asking because you caan easily start problematic versions and then start working one without restarting PC.

[dypsis]

dypsis,

One other thing: we made a change in build 3054 that might be related:
https://www.ventismedia.com/mantis/view.php?id=21202

Can you confirm whether the issue occurs in build 3057 ( https://www.mediamonkey.com/forum/viewt ... 17#p521917 ) ?

Thanks!

Yes, the issue is also in 3057.
It also has that Add/Rescan issue that has been resolved in a recent build.

I'm just back from a reboot.
It's not just explorer that has issues, but even buttons on other applications don't work as expected until I reboot.
The issue never occurs until I run MM 2024.

[dypsis]

Hi,
Does update to 3057 Triggers same behavior?

If yes, does clean portable install of 3057/3074 in new folders without importing observe same behavior?

I am asking because you caan easily start problematic versions and then start working one without restarting PC.

OK. I have an update.

I created a new portable extraction of 2024.0.0.3074 and when it offered to import settings from MM4, I clicked "Cancel" and MM 2024 opened up in its default state. I didn't import any music. I just closed it, and this bug didn't happen.

It doesn't really explain why MM 2024.0.0.3051 is working fine with my portable version that I've been using for years, but not with newer MM 2024 versions.

[Lowlander]

Any devices (drives/phones/CD drives) attached to the PC that maybe hanging in combination with being access (by MediaMonkey)?

[dypsis]

Any devices (drives/phones/CD drives) attached to the PC that maybe hanging in combination with being access (by MediaMonkey)?

No external hard drives, phones or optical drives are connected. I have one internal optical drive.

[FlexFlexerson]

Hi there, I'm having the exact same issue as OP. Have been running MM 2024 without issue and then all of a sudden the same problem started a few days ago. I'm running the latest MM 2024 build.

[Rob_S]

Have you both by chance recently received the update to windows 24H2?

[FlexFlexerson]

Have you both by chance recently received the update to windows 24H2?

Yes, I have. My computer says it was updated on 10/20 which doesn't really fit the timeline of when I noticed this problem beginning, but maybe my recollection is off.

[CrashMonkey]

Don't know it that is the cause, i have a few test machines with windows 24H2 and all latest update for that, and there MM runs OK.

Did you also look at eventvwr to see if you get any errors there?
Start -> type: eventvwr press enter.
Left side, expand "event viewer (local)", expand "Windows Logs" Look at "Application" and "System". Look for any warnings(yellow)/errors(red) items that happen during that time.
If its hard to find.
Open eventvwr first. Start mediamonkey, then go back to eventvwr and Select Application or System, and press f5(to refresh).
Post any errors you get, or a printscreen back here.