Yeah, no. I can pretty much guarantee that it's not an HBS problem, especially if you never restored an image. Do you have CL cloud sync turn on?
CyberLock 8.0
- Thread starter danb
- Start date
Yeah, no. I can pretty much guarantee that it's not an HBS problem, especially if you never restored an image. Do you have CL cloud sync turn on?
Do you use any software to clean/optimize your computer? I'm unsure if that could be the cause...
Restores work fine. As i said, i am not sure what it is that causes it, hence my question if you where aware of any issue.
Yes, some programs have problems when restoring an image. For example, I always had to reactivate PDFelement, GOM Player Plus, and CyberLock (not always) after restoring an image. I experienced this issue with all the imaging software I used: Macrium Home (CyberLock), EaseUS (GOM Player Plus), and HBS (PDFelement).
That issue is not your imaging app. The issue is because your imaging app is doing its job. When you restore an image, sometimes the system identifier can change between the new and the older pre-restore system. More often than not it's the disk identifier that changes. That's why you have to reactive some stuff; because your license is tied to that old identifier. It's not a bug.
I meant to say that I, too, experienced program issues after using imaging software for restoration, not that the software itself was faulty. I appreciate the information you provided.
Yeah, there probably is not a lot we can do on our end if the user / backup software restores files from a previous state. If you guys have any ideas on what we might want to do on our end, please let me know... and I will think about it some more as well.
Since my last post, when i fixed it, it has reverted - again. My foremost suspicion is actually restarts, after 8-10 restarts it reverts. But that should be due to some sort of compatibility issue. An issue i can not figure out.
Can you exclude C:\ProgramData\CyberLock\ from the Hasleo Backup?
This is all very odd. I've never had this issue with Hasleo Backup Suite. I think something else is at play here.
I can try, but if you read my latest posts, i do not think it is HBS that is the problem. Mere turn on and turn offs of the pc is what triggers this, most probably in collaboration with something.
Anyway, just tell me what, how, to do it.
Last edited:
I have never used Hasleo, so I would have no idea.
But I thought of something we can try. Can you make a copy of all of the files in the C:\ProgramData\CyberLock\ folder when it is working correctly and store them somewhere. Then make another copy of the same files in the same C:\ProgramData\CyberLock\ folder, and zip up both sets of files and send them to me? At least we will get to see what is changing and when it is changing.
I think i have found it, i had the program SSD Fresh installed, and it shared Ms Visual 2017 with CL. After installing it all seems good. At least so far.
About uninstalling SSD Fresh, that thrashed CLs functionality and no self protection from CL warned or poped up about the messing with it.
That is great to hear! The .db files are protected in that nothing can read or write to them except CyberLock. As far as permissions on the actual .db files go, no software does this as far as I know... this could turn into a real pain for the user and for the backup software (and other utilities). Besides, CyberLock automatically protects these files from malware since it does not allow the malware to run in the first place.
Please read my above posts, they answer both questions.
Also, you said "i had the program SSD Fresh installed, and it shared Ms Visual 2017 with CL". Why would SSD Fresh "share" Visual Studio? with CyberLock?
You may also like...
-
Introducing VoodooSoft's RansomGuard EDR - Streamlined EDR for Consumers and SMB- Started by danb
- Replies: 37
-
-
-
-