Could you check the statusbar and see if really only such a small amount of files is loaded?
If the figure of the loaded files is much bigger than the number of displayed files then I suspect that you have applied (unvolountarily) a filter. Press F3 to toggle the filter and see if that does something for you (except toggling the filter).
I double-checked: no space, no nothing in the filter line.
Meanwhile, the symptoms become more spooky:
I restarted Wine/mp3tag and voila: thousands of files present. Sacrificed a small mammal, sweared to donate you millions.
Ended the session, restarted to directory /++FIXTHIS (my workbench), again having displayed only 46 audio files in 7 directories while there are in fact 120 directories / 831 files (see screenshots attached).
This is the basic problem with remote diagnosis:
I cannot look over your shoulder.
What is different for those files that got loaded and those that have not.
As MP3tag does not even load them, it looks to me as though they do not get recognized as valid files.
Just a shot in the dark: could it be that some folders have a space character at the end? This would be illegal for windows file and folder names ...
These characters are other candidates for hickups: < > ? " : | \ / *
Again: if a function sometimes works and sometimes it does not then there is most certainly a reason for that.
But all in all it looks like a very local problem that you have to investigate, esp. as both reaction occur on the same machine.
So the basic question remains unanswered: what is the difference between those that get read and those that are not even detected as valid files?
\\?\unix\Volumes\skbox-- SORTTHISOUT\ is the directory I keep all mp3s to rework.
If this is set as the starting dir of mp3tag/wine, then some files/directories are read yet not all.
Working through those loaded, using the 'remove'-command to remove the finished from the UI until it is empty works for me. After all are done, I reload the same dir and sometimes new files appear, sometimes not.
Result: I never know if all files are read in or only a portion. And if it's only a portion, I cannot tell the reason.
Comparing the UI-results with a straight ls-Pipe to a dir.txt shows the same — yet no structural difference, no anomalies. No forbidden characters, blanks whatsoever. All dirs/files seem to be named technically correct.
(edit) earning some credibility herewith:
attached, find two screenshots. The first <mp3tag_ui-view.png> shows the 466 files as displayed by mp3tag/Wine.
The second <mp3tag_present-missing.gif> shows the same directory viewed through a file manager (DC Commander alike File Explorer on Win).
As there are no visible differences or anomalities — the phenomenon should be described sufficiently by now. BTW: r/w rights, ownership is identical to all files. As the user logged in, I do have all rights to manipulate files, no locks or whatsoever.