Advanced user who needs to tweak render presets per project reports a persistent (22.3 through 23.0) but intermittent (random intervals) error "After Effects warning: Could not rename the file xxxx to xxxx." The folder is in the AppData\Roaming tree, redirected by Group Policy on our Windows domain.
I can recreate a similar problem by rapidly scripting file creation, renaming, deletion loops with no delay in the same folder. Running such loops for about 2hrs this morning, I generated a small number of "Cannot create" responses to the Powershell Rename-Item command.
My end user just wants the software not to dump his presets. It appears that the result of this failed copy is loss of both the temporary file ('...output.nnnn.nnnn.txt') and the default settings file ('...output.txt'), with a stock edition replacing them. End user says, "If there were just a 'Retry' button on the dialogue..."
It seems the code here does not do a safe rename operation. Aside from checking the code on your end, is there anything I can do on mine to improve this situation?