Reply to thread

Message

<blockquote data-quote="HeiDef" data-source="post: 613871" data-attributes="member: 60542">Thanks [USER=51905]@Evjl&#039;s Rain[/USER] for the test and video.&nbsp; Good production!Even though you don&#039;t currently recommend RansomOff due to some stability issues, we&#039;ll get those fixed and hopefully you&#039;ll change your mind.&nbsp; Just a couple of notes.First for memory usage, and this doesn&#039;t just apply to RansomOff, but for any application you are measuring memory usage for.&nbsp; The regular &quot;Working Set&quot; column is not an accurate representation of the actual memory used by the app.&nbsp; Working set is actually a shared memory region with other processes and the operating system.&nbsp; So it&#039;s a little misleading.&nbsp; A better representation is the private memory value which is more realistic value of what the app itself is using.&nbsp; Not sure which column you were looking at for the ~80MB but I&#039;m guessing that&#039;s the regular shared working set value.Don&#039;t judge the startup speed by when you see the icon in the system tray.&nbsp; RansomOff has a delay built it on load to wait for Explorer to fully load before adding the icon.&nbsp; The driver and service is loaded well before you see the icon.&nbsp; Why it is not catching things on boot up though is something we will explore.&nbsp; Can you provide me the hashes of the samples that loaded on boot?We are working on the Office compatibility issue now as well.&nbsp; But did one of your test samples also cause a BSOD?&nbsp; I&#039;m a little unclear from the video.&nbsp; If so, would you please also provide that hash so we can test to find out the cause?&nbsp; Thanks again.</blockquote>

[QUOTE="HeiDef, post: 613871, member: 60542"] Thanks [USER=51905]@Evjl's Rain[/USER] for the test and video. Good production! Even though you don't currently recommend RansomOff due to some stability issues, we'll get those fixed and hopefully you'll change your mind. Just a couple of notes. First for memory usage, and this doesn't just apply to RansomOff, but for any application you are measuring memory usage for. The regular "Working Set" column is not an accurate representation of the actual memory used by the app. Working set is actually a shared memory region with other processes and the operating system. So it's a little misleading. A better representation is the private memory value which is more realistic value of what the app itself is using. Not sure which column you were looking at for the ~80MB but I'm guessing that's the regular shared working set value. Don't judge the startup speed by when you see the icon in the system tray. RansomOff has a delay built it on load to wait for Explorer to fully load before adding the icon. The driver and service is loaded well before you see the icon. Why it is not catching things on boot up though is something we will explore. Can you provide me the hashes of the samples that loaded on boot? We are working on the Office compatibility issue now as well. But did one of your test samples also cause a BSOD? I'm a little unclear from the video. If so, would you please also provide that hash so we can test to find out the cause? Thanks again. [/QUOTE]

Verification