[Milhouse]

@Milhouse, it must be my issue or other people would report it by now.

I know what you are saying to reverse the upgrade and find which one is the one causing the issue. The problem is that it worked until the upgrade and it doesn't after upgrade even if I reverse the upgrade back. I haven't tried backing up the database but I don't have working copy anymore. It is local database on RPi and files on NAS SMB NTFS.

I had 3 scenarios:

1. Working fine #0407 RPi on the TV. I upgraded to #0602 and scanned new movies. Some of the movies didn't scan. I removed the source, deleted associated entries and scan in again. More movies were unrecognized. Reversed the upgrade to #0407, deleted the source and scanned in again. The same thing, the same movies were unrecognized.

2. Separate RPi on projector working fine #0405. I scanned new movies first. All OK. Upgraded to #0602. No issues all looking good. Changed slightly filename in one of the questionable movies. It turned into unrecognized movie. Won't scan it again. There is no menu coming up where I can adjust manually the title. I renamed the file back to original and it appeared correct with the poster. All under #0602.

3. I made quick fresh SD card with official Kodi 17. Scanned the files in without any problems. Upgraded to #0602. Rename one file. No issues. Window pups up with manual selection of related title.

I also have another media box with Kodi 17 working without issues.

Not really sure what to suggest. It sounds like a corruption of some sort, but it's unlikely to be database related as the db migration in #0602 doesn't change your old v109 database, it only creates a new v110 database so that when you go back to an older pre-#0602 build it will be using your old (apparently working) v109 database again.

I could understand if the v110 db was giving you problems, but not when you go back to your v109 database and that also now has problems - this is what confuses me, as something else must have changed and it's not the database. My only thoughts are that perhaps a setting has become corrupted - try a fresh guisettings.xml - or a source has changed in some way, or something else outside of Kodi is behaving differently (maybe a scraper website is playing up?)