Please start with updating to MediaMonkey 2024. Does the problem persist?

Note, you can choose to remove the MediaMonkey database file (mm5.db) (and you may need to anyway) instead.

Please capture the connecting of a USB device in a debug log (step 4b) and attach the log to a Support Ticket: viewtopic.php?t=86643

Please note the number in the log where you inserted the USB device.

Timestamp shows when a file was last modified.

Unfortunately without more information this will be hard to fix as no other reports have come in about this.

You'd need MediaMonkey 2024 not MediaMonkey 5 for iOS 18 support.

Which Build (Help > About) of MediaMonkey are you seeing this with?

Please see: https://www.mediamonkey.com/support/kno ... vironment/

1. Can you please show with a screenshot?
2. Can you please capture this in a debug log (step 4b) and attach the log to a Support Ticket: viewtopic.php?t=86643
3. Can you please show the popup in a screenshot?

You can safely install over the existing MediaMonkey 5, it's an update to MediaMonkey (unlike MediaMonkey 4 > 5). It is a major release requiring a new version License (Lifetime Licenses get a free upgrade).

The next year update will be the next major release.

I saw the initial image wrong. It's not a drive entry, instead it's a folder entry. That's really strange.

For that you only have Locate Moved/Missing Files as solution.

You're working on the working Z drive instead of the non-working ZMusic] drive. You need to fix the ZMusic] instead.

Did you try the above recommended re-assign drive?

Are the duplicated at this point?

Are you using a Mapped Drive of a network location? Then you ran into a Windows bug changing its driveID. You should be able to manually re-assign in MediaMonkey to fix this.

Do you allow Sync to remove files? A clean start may be required to get rid of the duplicates.