![]() ![]() I already mentioned here, as well as in the other GitHub issue referenced above, that the template reply I received from support was not useful and that's why I've tried to pursue the issue here. First, I'm expecting engagement here in the GitHub issue, not from your support team. Some entries from MEGAsync.log that get logged at every I'm not sure if you're serious. How can I resolve this, and how can I get MEGAsync into a normal state, where it doesn't do a full scan and rebuild of its database from scratch at every startup? ![]() Basically doing everything from scratch at every startup, and that's presumably why I have to wait for 10+ minutes of 'Scanning' at every startup. I've looked in the log file called MEGAsync.log and to me it appears that what is happening is that the MEGAsync client considers itself to be in a "crashed" state, and it is then deleting everything in the local database, and then doing a full scan on my synced folders. As soon as I add in any synced folders, startup of MEGAsync takes ages, because it's forcing itself to do a full scan every single time. I've also tried completely uninstalling and reinstalling the MEGAsync client, but that made no difference either. Please refer to that issue to see more of my comments regarding this problem. ![]() Eventually that user found that they could solve their problem by changing their MEGA password via the web. I'm currently using v4.7.0 on Windows 10, but the problem existed also with v4.6.8.Īnother user logged a similar issue in #722 where I took part in the discussion. In other words, every single time MEGAsync starts, the system tray icon has the message 'Scanning' for more than 10 minutes. Every time I start MEGAsync, it deletes everything in my local database and then forces a full scan, which takes more than 10 minutes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |