NoVirusThanks OSArmor: An Additional Layer of Defense

I understand the concern, definitely. I just tried it out again, enabling block of Event Viewer as a test. Since I have a black desktop background in the lower right-hand side of the screen, the contrast of the white and orange exclusions pop-up was nice, not too harsh and the text was def. readable without difficulty. But not everyone has similar color combinations on the desktop, for real.

So yeah, a choice would be more interesting.

 

@novirusthanks , there's a major problem with the new NVT License Manager v. 1.5.

First, my system specs. - Win 10 Pro x(64) 21H2 fully patched.

This issue started on 3/20 when OSA ver. 1.6.8 downloaded the new NVT License Manager v. 1.5. Upon next system reboot, OSA was hosed and won't load. Multiple reinstalls of OSA ver 1.6.8 fixed the issue until the new NVT License Manager v. 1.5 downloaded again. Then OSA was hosed again. I tried to disable OSA updating but it didn't stop NVT License Manager v. 1.5 from downloading again.

I even tried installing the latest ver, 1.6.9 beta ver. figuring with NVT License Manager v. 1.5 part of the installer, it might stop this issue. It didn't.

There's a issue with SCM starting NVT License Manager v. 1.5 service. Why, I have no clue.

 

@n8chavez

The screenshot you posted about OSA, did you enable dark mode on Windows 10 and on the apps?

I will see what we can do to add a dark theme.

@itman

That is strange, I guess something other blocked NVTLicenseManager from starting? Maybe Appguard or similar?

@plat1098 reported a similar issue on #4041 where HMP blocked the setup file (it is now fixed) because it was new.

Please let me know.

@bellgamin

Writing the rule name in the "reason" is fine in my opinion: it help user find out what rule caused the block and including a detailed/technical description may confuse users, additionally some rules may need very long description text.

However, will see what can be done about this.

 

@novirusthanks, actually I'm now on Windows 11. However, I had the same issue with Windows 10. I enable a dark where whenever I can, either OS or app. Thanks for the hard work!

 

Thanks for giving it further thought.

In the meantime, please add a "Find" capability to the "Configure Real-Time Protections" panel of OSA's GUI. That would make it MUCH easier to locate a rule referenced on an Exclude alert.

 

Hi Bill,

There is a Search function available. Once you type a few letters, results will automatically display.

 

The only other security product I have installed is Eset Smart Security Premium. There were no conflicts from it in regards to prior ver. of NVT License Manager. I even went so far as to exclude NVTLicenceManager.exe from Eset real-time and HIPS to no avail.

I will also add that there appeared to be an issue with the original installation of NVT License Manager ver. 1.5 in that I saw its installer present in my Win User Temp directory although OSA did install it. Again, the problem manifests after a system restart.

Also, prior to the NVT License Manager ver. 1.5 update, I was experimenting with various drivers for my Realtek GBe Ethernet network adapter. This entailed uninstalling and installing associated drivers. Again, this had no affect on the ver. of NVT License Manager included in the OSA ver. 1.6.8 installer.

Is there any way to block the NVT License Manager ver. 1.5 update download so that I can run OSA ver. 1.6.8 and be protected?

 

@itman

Sent you a PM.

@n8chavez

Here is a screenshot of how OSA may look in dark mode:

 

@wat0114 -- THANKS! It works. I looked diligently for a "Find" in that panel's drop-down menus. I never would have guessed that it has an unlisted number.

@novirusthanks -- Your "dark mode" sample looks grrrreat!!!

 

You're most welcome

 

Here is a pre-release test 5 for OSArmor Personal v1.6.9:

Code:

https://downloads.osarmor.com/osa-personal-1-6-9-setup-pre5.exe

+ Added support for a dark theme if Windows Dark Mode is enabled

Screenshot of OSA when Windows Dark Mode is enabled:




* To test the dark theme, exit OSA GUI via OSA system tray icon -> Exit GUI -> Confirm action
* Now enable Windows Dark Mode and then start OSArmor UI
* In shorts, OSA GUI needs to be restarted

Please let me know if you find issues or FPs.

Thanks guys!

 

Aww, this is so nice! OK, well it's dark alright. I'll try it for a little while and see if I'll keep it. Thanks alot.

Spoiler

 

looks pretty good. congrats, @novirusthanks .

 

Ah yes.....Nice Thank you

 

I purchased a license in October 2020, and renewed the following year in 2021.

However, due my previous laptop failing in May/June 2021, I have not had this program installed, until today, on my replacement laptop.

As per the screenshot, after entering my license key to activate, it says that I have 'reached allowed activations limit'.

 

Wow! This is so nice. It's perfectly legible, perfectly clear, and not at all blinding. Well done!

 

https://www.wilderssecurity.com/thr...layer-of-defense.398859/page-163#post-3074923

 

That worked for the reset of activation, but it is a convoluted process.

I tried to get it show dark mode, but no success. Anyhow, I probably don't need it. Just as long as it is activated. @bjm Thanks for your help

 

Did you exit the OSA gui, enable Windows' dark mode, then restart OSA?

 

@n8chavez Your image was helpful. It did the trick.



P.S. I recommend that you remove your email address from your image.

 

Helping hand here

 

Well done, @Mr.X ...But, I thought only the original poster of the image, could make the change.

P.S I can still see the original image that has the details.

 

Obviously op has to download my edited image and replace his.
Thought I was clear with my intention

 

Meh. It's just my email. No big deal! It's in a lot of other places on the internets and googles anyways.

 

@novirusthanks -- At what version did OSArmor require VC++ 2015 redistributables (x86)?