For the second time in 2 weeks when Desktop Search started in Windows 10 I received the dreaded Cannot read config file - erase index message. I believe this was triggered by a lockup of my machine. Its unacceptable that the backup config that the software creates does not work.
As I workaround I have turned off the automatic start of Copericnic on machine startup and I backup the entire file folder so that I can do a restore if the index fails.
For the second time in 2 weeks when Desktop Search started in Windows 10 I received the dreaded Cannot read config file - erase index message. I believe this was triggered by a lockup of my machine. Its unacceptable that the backup config that the software creates does not work.
As I workaround I have turned off the automatic start of Copericnic on machine startup and I backup the entire file folder so that I can do a restore if the index fails.
0 Votes
0 Commentaires
Connexion ou S'inscrire pour poster un commentaire