Double-Instance Of Same Folder

[Darius1968]

In my last post, I questioned why a database entry from Sep. 15 was being registered in IMatch's History Panel as created on Sep. 20.  I found out that the reason was that IMatch had somehow, created two instances of the same folder, underneath a root directory, "_VLC Media Player".  (depicted in the two screenshots, below) 




Above, on the left, the original instance of the folder ("Quincy, M.E.") has the original file, which indeed, is noted as having been added to the database on Sep. 15.  However, on the right, there is a 2nd instance of that same folder ("Quincy, M.E"), which has a duplicate copy of a file, "Quincy M.E. (S8E8).mkv", which is identical to the original, with respect to contents and metadata, but as can be seen by comparing the IMatch Histories for each, there are differences. 

Finally, the 3rd and final screenshot, below, shows that in the eyes of the Windows 10 File Explorer, there's only one instance of that folder ("Quincy, M.E").



I'll attach a log file to help you try to figure out why IMatch is creating this double-folder-instance.  Yes, I have rescanned that top-level "_VLC Media Player" folder, with no resolution of the problem. 

[Mario]

I have no idea how you managed to do this.

Maybe changed the disk id?
Somehow tricked IMatch into adding a folder multiple times using relocate?
I would have a hard time to come up with a sequence of steps to force IMatch to add a physical folder twice.
I don't recall a user managing to do something like this, in all the years.

Just use the "Remove folder from database" command in the context menu. Keep the folder for which the files have the relevant content.

[Darius1968]

To fix the problem, I simply removed the folder, "_VLC Media Player", and then rescanned its top-level folder, which reinstated "_VLC Media Player" back into the database.  This time, without the double-instance of that problem folder! 
There's been no change of Disk ID, that I can tell.  There's only one media in this database, and that's simply my SSD "C" drive.  Strange...Strange!!!