NoVirusThanks OSArmor

[Deleted member 178]

I think Umbra does a clean install, not an update.
Maybe this is his opportunity to LOL us all...

LOL at the updating-method dudes, i feel sorry for your pain....in fact , not at all !!! hahahaha

 

[RoboMan]

Is OSA safe to use again after 1809 update?

 

[Deleted member 178]

Is OSA safe to use again after 1809 update?

Just wait the updated version.

 

[Deleted member 178]

Is OSA safe to use again after 1809 update?

Just wait the updated version.

 

[RoboMan]

Is my OSArmor 1.5 ever come back from war?

 

[LDogg]

Is my OSArmor 1.5 ever come back from war?

Who knows it may do!

~LDogg

 

[shmu26]

Novirusthanks is not going to abandon it. He will put out a new build, according to his famously unpredictable schedule.

 

[RoboMan]

Novirusthanks is not going to abandon it. He will put out a new build, according to his famously unpredictable schedule.

Following this schedule they will make it compatible with 1809 when we're all about 1901 LOL

 

[In2an3_PpG]

Following this schedule they will make it compatible with 1809 when we're all about 1901 LOL

I can imagine business clients & other projects having taken precedence over updating OSArmor to work with 1809. NoVirusThanks was probably not aware 1809 might break OSA. Just my opinion.

 

[NoVirusThanks]

Quick update (beta build):

Here is a new v1.4.1 (pre-release) test1:
https://downloads.novirusthanks.org/files/osarmor_setup_1.4.1_test1.exe

*** Please do not share the download link, we will delete it when we'll release the official v1.4 ***

So far this is what's new compared to the previous pre-release:

+ Fixed compatibility issue on Windows 10 1809
+ Fixed some false positives

To install it, first uninstall the previous build, then reboot (not really needed but may help), and install the new build.

Please confirm me it works fine on your Windows 10 1809 OS.

* The GUI still says 1.4, I will update the text to 1.4.1 on next beta build *

 

[Burrito]

Quick update (beta build):

Here is a new v1.4.1 (pre-release) test1:
*

Thank you.... it is appreciated.

 

[harlan4096]

It seems OSA 1.4.1 is again operative with RS5 1809, got a warning again in my VM where I test Panda Dome Premium

 

[noob guy]

Quick update (beta build):

Here is a new v1.4.1 (pre-release) test1:
https://downloads.novirusthanks.org/files/osarmor_setup_1.4.1_test1.exe

*** Please do not share the download link, we will delete it when we'll release the official v1.4 ***

So far this is what's new compared to the previous pre-release:

+ Fixed compatibility issue on Windows 10 1809
+ Fixed some false positives

To install it, first uninstall the previous build, then reboot (not really needed but may help), and install the new build.

Please confirm me it works fine on your Windows 10 1809 OS.

* The GUI still says 1.4, I will update the text to 1.4.1 on next beta build *

It works fine so far! Thank you NoVirusThanks !

 

[plat]

A little thing...made a gif (apologies for quality) to illustrate that Edge can open the first time but is blocked next time. Any value at all? By the way, so glad to have OSArmor back, now asking whether EXE Radar Pro will be updated as well for v.1809. Currently, I'm running v. 3.1.0.0 build 1-15052015 in Lockdown mode.

Spoiler

 

[silversurfer]

OSA v1.4.1 blocks (advanced settings) now like before

 

[RoboMan]

Anybody knows how to correctly whitelist on OSArmor? Am I supposed to compelte all the fields? (process, parent, signer). If I add the full process router, like C:/Users/RoboMan/AppData/Wunderlist/Wunderlist.exe" it won't even care...

 

[Azure]

Anybody knows how to correctly whitelist on OSArmor? Am I supposed to compelte all the fields? (process, parent, signer). If I add the full process router, like C:/Users/RoboMan/AppData/Wunderlist/Wunderlist.exe" it won't even care...

Does that file trigger an alert? All files that trigger alerts are written on the log folder.
You can enter the information found there into the exclusion helper. You don't need to complete every field to exclude a file.

 

[shmu26]

Anybody knows how to correctly whitelist on OSArmor? Am I supposed to compelte all the fields? (process, parent, signer). If I add the full process router, like C:/Users/RoboMan/AppData/Wunderlist/Wunderlist.exe" it won't even care...

As was mentioned, the easiest way to whitelist is straight from the prompt.
If not, the next easiest way is just to fill in the full path, and leave everything else blank.

 

[given]

That the whole point.
if you install a 3rd party security soft, it means you don't fully trust/are satisfied by what the built-in security of the OS offers, from this it is a duty to learn what the 3rd party soft can do and use it to the best way possible to supplement what the OS offers.

Using a soft at default setting is already a mistake, default setting were made to avoid installation/usability issues. NO ONE should ever use default settings. If a user can't manage or have the will to learn the software he uses, in our case OSA, better for him to stick using what Win10 offers.


it is isn't ill advice, just the basic logic. With OSA, user dont need CFA , simple as that.

You don't need a bullet-proof vest when you stay in a tank.

you are one of the funny dude around here in MT bro @Umbra i really like that line "no need bullet-proof vest when you stay in the tank" good one bro @Umbra

 

[NoVirusThanks]

Have officially released OSArmor v1.4.1:

Prevent Malware and Ransomware with OSArmor | NoVirusThanks

[25-Oct-2018] v1.4.1.0

+ Fixed compatibility issue on Windows 10 1809
+ Fixed some false positives
+ Minor improvements

If you find any issue or false positive please let me know.

@plat1098

Replied to your PM.