"confirmation: the following files no longer exist..." appears repeatedly

[dawid.kielak]

For a number of months, about once a week, when I start Music Bee, I get the error you can see in the screenshot. The files are there, and if I choose `no', then the only change I see is that the `date added' field gets reset to the current date. Clicking `yes' sometimes has the same effect, and sometimes removes the files.

All of the files have Polish diacritics in their names, but I have hundreds of other such songs. It is always the same 4 songs that the warning is about.

It does not happen every time I start Music Bee, but it does happen quite often.

[phred]

Clicking 'yes' will remove the information from MB's database, so before clicking 'yes' make 100% certain the files do not exist in the -exact- location as indicated on the warning. It's quite possible the files exist (and play) but have been moved to a new location by means other than MB. In which case MB would only know that they're no longer where it thinks they are. It's not a good idea to move files using Windows Explorer or anything else outside of MB. If you do, you should rescan the files so MB knows where they are.

[Steven]

try the patch version as i vaguely recall something like that was fixed
https://getmusicbee.com/patches/MusicBee35_Patched.zip
unzip and replace the existing musicbee application files

[dawid.kielak]

I am afraid the patch didn't help, and neither did rescanning.

[Mayibongwe]

Long shot, but can you also post a screenshot of your Preferences > Library > Monitored Folders  section.
And do you perhaps have one of these artists' folders set to be excluded from the monitoring?

In the past, while investigating an issue from another thread, I noticed that users are allowed to set the same folder to be both included and excluded from monitoring,
And that had caused some funny behaviour at the time along the lines of what's been reported here.

[dawid.kielak]

Here is the screenshot:

[The Incredible Boom Boom]

One way you could test whether the characters are causing this issue is replacing them in the filenames with Latin ones.