Problem after version update

Hi @vivis10433457 , If the problem is with files last saved in an earlier full version opening renamed with a [Converted] suffix forcing a Save As on a regular Save, you can override that behavior via a script.

I assign this script (which overwrites the opened file with no dialog) the Command-S key command:

var doc = app.activeDocument;
var fp = doc.filePath;
var n = doc.name;

if (doc.converted) {
    doc.save (File(fp + "/" + n))
} else {
    doc.save()
}

Just keep in mind that the forced Save As is a safety feature, which gives you the option to leave the document from an earlier version unchaged in the event that you have problems with the new app version. I have an automated incremental backup system, and can go back in time and retrieve the earlier version, so I’m not very concerned with overwriting the earlier version with a script.

If you are not familiar with scripting I can post a compiled version for you to copy into your Scripting panel.

This would be expected behavior for major version upgrades (16.x to 17.x), but not for incremental updates within a version.

Are you saying it happens when doing an incremental update?

Don't upgrade until the project is done.