"Your config is corrupt, please start over" on Windows 7

[phalox]

Hi Devs,

I've had this error multiple times so far and it's pretty annoying. Every time I have to reconfigure the synchronisation and every time I'm wondering if I should select the folder above, or the target folder itself. So, for completeness: if I do a selective sync, I just choose the target folder twice (local & remote).

Back to the issue: I usually get this on a fresh restart (now it was after shutting down, after installing windows updates).

Specs: Windows 7 Selective sync (just 1 folder) Running version 3.0.1

Thanks for your work. I like the comfort of having my most important files constantly backed up!

[fennectech]

Delete the content of .local/data/Mega Limited

[phalox]

Well, actually the mega tool allows me to click OK and then I have to start over. I'll see what your recommendation does when it happens again!

[fennectech]

This is likely to happen if you the program is intrrupted while saving its configuration to the disk Ether by a failing harddrive (Worst case) or the machine being powered off or the megasync client just bailing for some wierd reason i highly recomend you try out the freeware hdsentinel https://www.hdsentinel.com/hard_disk_sentinel_linux.php You do need to run it as root. If your drive is struggling ittl show up in there

[phalox]

I believe it's the latter: megasync bails out for a reason. HDD turns out totally fine (SSD less than a year old). I didn't have the issue anymore in the last month. Don't know if anyone else had the same problem?

I have seen it on one other system running Windows 7 (like I am).

On 6 July 2017 at 05:34, fennectech [email protected] wrote:

This is likely to happen if you the program is intrrupted while saving its configuration to the disk Ether by a failing harddrive (Worst case) or the machine being powered off or the megasync client just bailing for some wierd reason i highly recomend you try out the freeware hdsentinel https://www.hdsentinel.com/hard_disk_sentinel_linux.php You do need to run it as root. If your drive is struggling ittl show up in there

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/meganz/MEGAsync/issues/78#issuecomment-313286224, or mute the thread https://github.com/notifications/unsubscribe-auth/ADzJesb1G9s_aRsTRMnAUs_b1F8jdRM-ks5sLFXMgaJpZM4MX1i2 .

[fennectech]

Ahh your a windows user Cant help you then Sorry

[phalox]

Sorry that I am :-)

I've updated the title. Maybe someone else will have a similar issue. Who's working on the Windows version of the client? If there's a way I can send a log file, I'd happily do so!

[elektrinis]

Two years later, I just want to let you know I have a similar issue. In my case passwords works fine, but gets lost after couple restarts. I am also having problems with other programs, including password managers, MS office 365 etc, basically anything with higher security level. In my case nothing helped, including a fresh reinstall.

Did you solve the issue?

[x69toki]

Three years later, I just want to let you know I have a similar issue. In my case "Your config is corrupt, please start over" on Windows 10 Pro ver. 2004 (OS Build 19041.423) with MEGA v4.3.3.0

I am also having problems with other programs, including Microsoft OneDrive.

Any survivors?

[Kyiro]

Ughhh i'm also having this issue on Windows 10 Pro 2004 :/

[Kyiro]

I found this reddit post, which might help. https://www.reddit.com/r/MEGA/comments/h9f6ea/megasync_after_win_10_2004_upgrade/

[mattw-mega]

MEGAsync uses the WIN32 function CryptProtectData to store your settings, encrypted to a key that only your windows account knows. Possibly the 2004 update has either broken that function, broken the key, or changed your windows account somehow? It's not only MEGAsync affected by this: https://www.zdnet.com/article/windows-10-2004-glitch-microsoft-admits-bug-breaks-storage-spaces-corrupts-files/ I would recommend holding off on updating to 2004 until Microsoft resolves that (for myself, the 2004 update is not available - perhaps they have halted the rollout).

[Fuzzo]

Same problem here with Windows 10 and 11... any news on how to solve this?

[username77]

Same problem here with Windows 10 and 11... any news on how to solve this?

Same problem to me with win10/11. Would be nice to have an import/export setting with all synced folders and excluded files/folders too

[Fuzzo]

@username77 not yet unfortunately. I'm in touch with the support for that but till now they were not able to understand why this is happening. The problem looks survive to several MegaSync versions...

Another problem is that seems the MegaSync.exe file doesn't support a command line switch to enable debug mode, but only manually with CTRL+SHIFT key pressed when you double click in the MegaSync icon. As this problem happens at Windows startup and a command line switch to enable debug mode doesn't exist, the "manual" debug mode is completely unuseful...

[ghost]

I have the same problem on Windows 11 Pro 22H2 22621.2715, very annoying

[Fuzzo]

At the end, after a couple of tickets opened to support without success, a Windows 11 fresh installation solved the problem. I know, it's not a solution...

[inetprog]

Is there any solution to the issue?

[Senliast]

Have the same problem. From time to time it happens. I think it started after i installed Windows 11, on Windows 10 it did not happened or happened very rarly.