I've started getting the following error on one of my three PCs:  Warning:  Failed to rename <filename>.tmp.  The process can not access the file because it is being used by another process. 

So far (once), if I rename the file with the correct extension and run a verify, all appears well, but I'm not excited about depending upon a backup that had a warning. 

I'm only seeing this on one of my two Win 7 Pro systems, and I haven't seen it on my Win 10 Pro system.  I run my backups with only Reflect and (usually) one Explorer window running beyond what's normally running after a boot.  There are no obvious culprits (no change in my behavior, no new software, no major updates of old software, ...). 

Has anyone seen this?  Am I safe in my assumption that if validation is successful that it's a good backup?  I'd really like for this warning to go away. 

Thanks

Does the same thing happen when you run the backup operation in your WinPE rescue media environment?  If not, live AV protection would be first on the "usual suspects" list and it would be worth adding Reflect to its list of exclusions if you haven't tried that already.

Regards, Richard V. ("Arvy")

I've seen this happen multiple times using the Windows RE environment for making image backups.

I've also learned that if you leave the <filename>.tmp file on your backup media and perform a backup of another machine that Macrium's first step is to delete the temp file.

Very annoying when you're trying to backup several machines in a given day, to have to manually check and rename files.

Hope someone finds a fix for this.

Do you see the same issue when you run an image backup using Reflect from within Windows?  What version of Reflect are you using?  This thread is in the V6 forum from quite awhile ago.

Did not notice this was in the V6 forum.

I am running V7.3.5925 and since I have support also opened a help ticket.

Found this thread through search, and being new to forum didn't notice it was in a V6 thread.