There are several rules for name and unneeded check in cmpro. In this case cmpro has to decide between (and since it's within a parent/clone relationship you have to take both sets into account):

- file in set2 is wrong named but belongs to set2 (one indicator: a wrong name)

and
- file in set2 is correctly named but wrong placed (needs to be put in the parent). (two indicators: correct name + correct hashvalue)

For the second case name AND hashvalue are correct so it's simply more likely than case one. name + unneeded check will show a "wrong placed" prompt.

So it's simply a case of which is the more likely case.

If you got fix missing enabled, it will automatically handle the problem for you because:
- fix unneeded/name will move the file to its correct place (set1)
- fix missing will automatically add it (correctly named) to set2.

It's recommended to have all check options enabled.


Roman Scherzer