RansomOff

No worries. Definitely appreciate the feedback regardless. It only helps us improve.

It's unfortunate you had a bad experience though and we are sorry for that.

 

Lots of files and registry keys get created over the lifetime of any piece of software. The uninstaller's job is to generally just rid the system of start up references and main files. Many files, like drivers, cannot be deleted until restart. In that case, the uninstaller requests the OS to delete files on the next reboot. That's what RO does. However, that can be disrupted by a multitude of things outside of the original uninstallers control. So while we strive to delete everything, sometimes it's not possible and the files that are left have no meaning anyway other than some used hard drive space.

 

Found the downloading arrow on ransomoffs system trya icon confusing.
When i hovered over the icon with my mouse no information was displayed like i expect it would do.

Eventually i figured out it was indicating that a new release had downloaded.

 

There a list of known apps that stop RansomOff from installing? The installer launches and that's about it. I can launch the installer 10 times, they're all resident, and not have any issues with other applications or functions.

 

What OS version are you running? Any other security software on your machine? If you see the installer running (that's what you mean by resident right?) then there is something interfering. Without more details about your system and software configuration, it's hard to say for sure.

 

I wonder if anyone is still running RO without any problems? Haven't seen any feedback (positive or negative) lately.

How is everything going, have you managed to sell licenses to companies yet? I was just wondering.

 

Hi, I've seen a similar issue several times when I try to install a new program (the most recent one was with VEEAM Agent For Windows 2.1.0.423).....the installer program is running w/o using any CPU cycles so I need to terminate the task. I can start the installer multiple times and in Task Manager it is showing up multiple times but all are showing 0% CPU time. After completely shutting down RO, the installer runs fine.
My environment: Windows 10 Pro x64, RO version 5.2017.315.6969.RC1

 

Just tell Dave, though he does monitor this thread ...

He is very responsive.

 

Thanks for the notice. I'll take a look and try to test with VEEAM. Do you have to fully shutdown RO or can you just disable certain protections for it to work?

 

Just tried it again with VEEAM Agent for Windows and now the installer runs fine with RO system protection enabled.....shoot me.

 

We installed VEEAM a few times without any issues. It obviously seems like RO had some interaction to make the installer hang but it's hard to identify the cause without being able to recreate. You may not remember when it did hang but was your hard drive being heavily utilized? The VEEAM installer is pretty large (274MB) and if you had other IO intensive tasks going on the installer would have to compete for the resources which could give it the appearance of hanging. Just a thought.

 

Hi, could not remember if there was high I/O activity. Next time it happens again, I'll pay more attention to it.

 

We wanted to get this update out before the new year so here it is. Fixed a number of bugs and added some new features. We haven't built the auto-update packages yet but will get those up in the next day or two. Otherwise you can download the installer from https://www.ransomoff.com. Cheers!

5.2017.365.6848 (RC1) - 31 Dec 2017

• Improved non-standard display size support.
• Added wildcard support for exemptions, blocks, and backup paths.
• Added ability to manually add files and directories to block.
• Added UI color change settings.
• Improved process loading performance for Win8.1 and greater.
• Fixed password reset bug.
• Other minor bug fixes and UI tweaks.

 

Sorry I gone dark awhile but looking forward to keeping up with the releases like this as they become available.

I won't go into some subzero weather that's also delaying me while down with the flu but am working my way back.

Greetings and thanks for such outstanding continued support for all of us who appreciate everything put into this software invention

 

File extension actually doesn't matter. It detects via the file header.

 

Thanks. It sure is cold here on the East Coast so I feel for you. Always appreciate your testing thoroughness though and hope you can put the latest through its paces.

 

Thanks. Icon visibility is that last thing on the RO startup checklist. There is a lot of things that RO is doing in between boot and visibility and really RO should always be last in loading. That's because the RO service is validating all of the other applications that get loaded at boot. Remember, RO is not signature based so it's not as simple as just checking a hash or querying a database. It actually needs to wait for specific operations to occur for each process to continue. Four minutes though does seem like an unusually long amount of time. Was this the first time you restarted or subsequent reloads? Are you also in a VM? The first loading is always the longest because of setting up the database and initial exemption lists. We could make the icon show faster but if the system is still in its boot sequence having it visible won't make much difference other than a feel good factor.

 

When RO starts up, it makes a list of other start up items. It saves that so on the next reboot it will reference the list to help speed up protection decisions. On the very first reboot after install, that list will be empty. Also, if you add software while RO is running and is set to start with Windows, it won't be in the list RO previously made so it will take another boot cycle for it to be included. So every subsequent reboot won't make booting faster except for the first one when the list is initially empty.

The list however is not all inclusive for security reasons which can limit its effectiveness a bit. We have some ideas for making this process more robust by including things like execution history and tying in with RO's monitoring so that it can be much more useful. And that will hopefully make booting much quicker especially after each reboot.

The Simple/Advanced setting won't have any impact on boot performance.

 

Thanks! Adding exemptions will speed things up but you obviously have to be careful as there is a security trade off. Malware does target software to do its bidding and while RO looks for things like that, when it's exempted it'd be easier to slip through.

 

Maybe it would be a good idea to have an initial icon at initialization which is ghosted or black then the full final icon when it is fully loaded up?

 

That is a good idea. Should be relatively easy to implement as well. Thanks.