Duplicate files being uploaded after renaming folder

[perigozin]

I have a folder with over 200GB of files that was already synced (using the backup option). Yesterday I renamed it from "Production" to "Audio" and now MEGA is uploading the files all over again. This is the second time it happens this week and from what I remember this was not an issue before (been using MEGA for years).

The worst part is the original folder that was renamed still exists when I access my MEGA account from a browser, so it takes twice as much space and I have to delete it manually.

Now I feel a little apprehensive renaming things because it might reupload duplicates or mess up with my files in the cloud.

[rautamiekka]

Try this:

1. Reboot MEGAsync.
2. Right-click the job in the app settings and select Deep rescan.

[perigozin]

Try this:

1. Reboot MEGAsync.
2. Right-click the job in the app settings and select Deep rescan.

I don't see this option anywhere in the desktop app

[rautamiekka]

Try this:

1. Reboot MEGAsync.
2. Right-click the job in the app settings and select Deep rescan.

I don't see this option anywhere in the desktop app

Go into the app settings, into the Backups tab, and right-click the backup job.

[perigozin]

Sorry, I can't find it

[rautamiekka]

Sorry, I can't find it

[image]

Your MEGAsync is very old, evident by all the missing all the extra info in the list.

[perigozin]

Sorry, I can't find it
[image]

Your MEGAsync is very old, evident by all the missing all the extra info in the list.

I trusted it to be updated automatically, as it's set in settings. Obviously this is poorly developed software because it always showed me there were no updates available, so I thought it was always up to date. Now I checked and indeed I was running version 4.13.0 while the newest one is 5.5.0. I wonder how many people are using old, outdated and unsafe versions because they trust the autoupdate/check updates feature without any type of warning.
Anyway, let's see if it solves my issue.

[rautamiekka]

Ya, the same happened to me when 5 was released, likely to others as well. Possibly the update system changed, thus 4.x.x couldn't see the update.