Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
Other security for Windows, Mac, Linux
NoVirusThanks OSArmor
Message
<blockquote data-quote="NoVirusThanks" data-source="post: 1019812" data-attributes="member: 68429"><p>We've released OSArmor v1.8.2:</p><p>[URL unfurl="true"]https://www.osarmor.com/download/[/URL]</p><p></p><p>Here is the changelog:</p><p></p><p></p><p></p><p>If you have automatic updates enabled then OSArmor should auto-update in the next hours.</p><p></p><p>Else you can install it "over-the-top" of the installed version, reboot is not needed.</p><p></p><p>* If you used test builds you should manually update to this final version (install over-the-top is fine).</p><p></p><p>If you find false positives or issues please let me know.</p><p></p><p>A few information:</p><p></p><p>We added this new option "Allow known safe third-party processes behaviors" so users/companies have the option, if required, to disable the internal rules to allow known and safe third-party software behaviors (can be used to create personalized exclusion rules only for the third party software you have installed).</p><p></p><p>We also added this new option "Do not monitor non critical programs" (may be renamed in future) so users can choose to monitor any program (such as third-party file managers, etc) instead of monitoring only critical programs.</p><p></p><p>The above two options (enabled by default, at the moment) will help in reducing false positives, especially the first one.</p><p></p><p>The option "Enable internal rules to allow safe behaviors" now handles only system-related known and safe processes behaviors (highly recommended to have it enabled).</p><p></p><p>[USER=96560]@Victor M[/USER]</p><p></p><p>This new version fixed the issue you reported, mainly to make it work:</p><p></p><p>1) Create two new users in the AD server, e.g Dev-SUA and Dev-Admin</p><p></p><p>2) On the W10 PC go on Account -> Access work or school -> click on Connect</p><p></p><p>3) Click on the link "Join this device to a local Active Directory domain"</p><p></p><p>4) Enter the domain and then enter the username and password for the user that will be SUA (e.g Dev-SUA)</p><p></p><p>5) Select the account type as Standard User Account</p><p></p><p>6) Then restart the PC.</p><p></p><p>Repeat steps from 2 to 6 but for Administrator account (basically, enter username Dev-Admin and set it as Administrator)</p><p></p><p>Then on OSArmor enable the option "Password-protect power options with Windows Admin Credentials"</p><p></p><p>From the SUA account, when you are prompted to enter the credentials to unlock OSArmor window/right-click menu/etc, select the username (Administrator account) e.g DOMAIN\Dev-Admin and enter its password.</p><p></p><p>That will work fine (tested here on a Windows Server 2022 and a Windows 10 and Windows 11 VM).</p><p></p><p>It is important that you connect both SUA and Admin accounts because OSArmor option "Password-protect power options with Windows Admin Credentials" requires that you enter credentials for an Administrator account (and in this case it must be connected to the AD domain).</p><p></p><p>[USER=80139]@Guilhermesene[/USER] [USER=57429]@Zero Knowledge[/USER]</p><p></p><p>We're running some tests with multi-year subscription in these days (2 years plan), if all goes well we should add them very soon.</p><p></p><p>We're also discussing about discounts for multi-products purchased in a bundle (e.g OSArmor + SysHardener).</p><p></p><p>Will update here as soon as I can share more details.</p><p></p><p>[USER=80139]@Guilhermesene[/USER]</p><p></p><p>The behavior you described is correct for OSArmor <= 1.8.1, now with the final release of OSArmor v1.8.2 we introduced this new option:</p><p></p><p>"Do not monitor non critical programs" -> If you uncheck it, all programs (also non critical like Total Commander and any other third-party file manager) will be monitored.</p><p></p><p>At the moment it is enabled by default.</p></blockquote><p></p>
[QUOTE="NoVirusThanks, post: 1019812, member: 68429"] We've released OSArmor v1.8.2: [URL unfurl="true"]https://www.osarmor.com/download/[/URL] Here is the changelog: If you have automatic updates enabled then OSArmor should auto-update in the next hours. Else you can install it "over-the-top" of the installed version, reboot is not needed. * If you used test builds you should manually update to this final version (install over-the-top is fine). If you find false positives or issues please let me know. A few information: We added this new option "Allow known safe third-party processes behaviors" so users/companies have the option, if required, to disable the internal rules to allow known and safe third-party software behaviors (can be used to create personalized exclusion rules only for the third party software you have installed). We also added this new option "Do not monitor non critical programs" (may be renamed in future) so users can choose to monitor any program (such as third-party file managers, etc) instead of monitoring only critical programs. The above two options (enabled by default, at the moment) will help in reducing false positives, especially the first one. The option "Enable internal rules to allow safe behaviors" now handles only system-related known and safe processes behaviors (highly recommended to have it enabled). [USER=96560]@Victor M[/USER] This new version fixed the issue you reported, mainly to make it work: 1) Create two new users in the AD server, e.g Dev-SUA and Dev-Admin 2) On the W10 PC go on Account -> Access work or school -> click on Connect 3) Click on the link "Join this device to a local Active Directory domain" 4) Enter the domain and then enter the username and password for the user that will be SUA (e.g Dev-SUA) 5) Select the account type as Standard User Account 6) Then restart the PC. Repeat steps from 2 to 6 but for Administrator account (basically, enter username Dev-Admin and set it as Administrator) Then on OSArmor enable the option "Password-protect power options with Windows Admin Credentials" From the SUA account, when you are prompted to enter the credentials to unlock OSArmor window/right-click menu/etc, select the username (Administrator account) e.g DOMAIN\Dev-Admin and enter its password. That will work fine (tested here on a Windows Server 2022 and a Windows 10 and Windows 11 VM). It is important that you connect both SUA and Admin accounts because OSArmor option "Password-protect power options with Windows Admin Credentials" requires that you enter credentials for an Administrator account (and in this case it must be connected to the AD domain). [USER=80139]@Guilhermesene[/USER] [USER=57429]@Zero Knowledge[/USER] We're running some tests with multi-year subscription in these days (2 years plan), if all goes well we should add them very soon. We're also discussing about discounts for multi-products purchased in a bundle (e.g OSArmor + SysHardener). Will update here as soon as I can share more details. [USER=80139]@Guilhermesene[/USER] The behavior you described is correct for OSArmor <= 1.8.1, now with the final release of OSArmor v1.8.2 we introduced this new option: "Do not monitor non critical programs" -> If you uncheck it, all programs (also non critical like Total Commander and any other third-party file manager) will be monitored. At the moment it is enabled by default. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
