Cannot delete ffs_tmp file

Get help for specific problems
Posts: 5
Joined: 1 Nov 2021

observantsound

I can't delete this file that was created after a canceled mirror sync.
What do I do?

it says:
Cannot delete file "PATH"
ERROR_BAD_NETPATH
Cannot read file attributes of Z:\
ERROR_BAD_NETPATH

Image
Image
User avatar
Posts: 4008
Joined: 11 Jun 2019

xCSxXenon

Something broke your connection to the network share
Posts: 5
Joined: 1 Nov 2021

observantsound

Well yes, that would explain why the sync failed initially.
But now the connection is restored and I still can't delete the ffs_tmp file.
Anytime I try, with windows, mac, freefilesync, it takes a really long time to do anything and then returns with an error saying they can't delete it.

So what do I do now?
Posts: 1021
Joined: 8 May 2006

therube

(Your images didn't display, so here:
Image
Image)

I still can't delete the ffs_tmp file
What does happen when you try to?
User avatar
Posts: 4008
Joined: 11 Jun 2019

xCSxXenon

Windows tells you why you can't delete it, what is the reason? Permission error? The file does not exist? Directory corrupt or not accessible?
Posts: 5
Joined: 1 Nov 2021

observantsound

Hey hey! Apologies for the super late reply.
Lost track of this issue and just ignored it.

If I try to delete the file, Windows will try for a very long time and if I remember correctly it was a permission error.
User avatar
Posts: 2430
Joined: 22 Aug 2012

Plerry

As reported before, this issue is often resolved by a restart of your computer.
Posts: 6
Joined: 2 Jan 2022

S^$K9mmpyT5VVihtAWpy

For Windows,to completely remove FreeFileSync use Revo uninstaller. It will uninstall anything. I will remove everything in the registry. It is the best uninstaller I ever used.
User avatar
Posts: 4008
Joined: 11 Jun 2019

xCSxXenon

That is not at all relevant to the question proposed...
Posts: 5
Joined: 1 Nov 2021

observantsound

I checked again and funny enough, the file is gone...
I swear I had tried to restart the PC and it was still there.

But oh well, right now it's gone so the problem is currently solved.

Guess to prevent this in the future is to make sure that a sync process isn't interrupted