Start a new topic

Cannot Read Config File Error 2nd time in 2 weeks

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.

Login or Signup to post a comment