Alex Pankratov :
Aug 14, 2019
This means that the program configuration folder has disappeared in its entirety. The program itself cannot do something like this (because it simply doesn't not how to do that), so the cause is external. With nearly 100% certainty this was done by an antivirus or other software of "security" nature, most likely due to seeing an update package being saved there.
You can try and check the "quarantine" log for such software, see where it might've stashed the data. Alternatively, you can search for a file called bvckup2.log, which will be in the root of the config folder.
Once you found the copy of the config folder, exit the program, put the config folder back in its place (see below) and then start the program. If you switched bvckup2 to run in service mode, you will also need to stop "bvckup2" service before restoring the config folder.
In desktop mode all configuration data lives in %LocalAppData%\Bvckup2 folder.
In service mode, the user interface data lives in %LocalAppData%\Bvckup2 and the engine (service) data is in %ProgramData%\Bvckup2. All backup jobs are stored in the engine configuration.
See https://bvckup2.com/support/forum/topic/480 for complete details on what's stored where.