Reply to thread

Message

<blockquote data-quote="NoVirusThanks" data-source="post: 702637" data-attributes="member: 68429">[USER=50782]@Windows_Security[/USER]Sorry, the var is %FILESIGNER% and not %PROCESSSIGNER%.Have tested it now and it works fine.[USER=32260]@Andy Ful[/USER]The &#039;C:\Users\*&#039; exclusion is applied to C:\Users\ and all its subfolders\files.Wildcard char * means any character and any length.[USER=58943]@ForgottenSeer 58943[/USER]Can you try to first uninstall OSA and then install it?I suspect the issue may come up if OSA is installed over the top or due to some strange Windows 10 behaviors.Or if the new OSA (.exe files changes) is not whitelisted\excluded in the currently installed security software.Moreover, probably a reboot would fix it somehow.[USER=55987]@HarborFront[/USER]It should work fine with HMPA, ESET, Windows OS, etc.[USER=58988]@Telos[/USER]Will fix that FP in the next build.[USER=46633]@Darrin[/USER]Yes, will add Pale Moon and other browsers to the list.</blockquote>

[QUOTE="NoVirusThanks, post: 702637, member: 68429"] [USER=50782]@Windows_Security[/USER] Sorry, the var is %FILESIGNER% and not %PROCESSSIGNER%. Have tested it now and it works fine. [USER=32260]@Andy Ful[/USER] The 'C:\Users\*' exclusion is applied to C:\Users\ and all its subfolders\files. Wildcard char * means any character and any length. [USER=58943]@ForgottenSeer 58943[/USER] Can you try to first uninstall OSA and then install it? I suspect the issue may come up if OSA is installed over the top or due to some strange Windows 10 behaviors. Or if the new OSA (.exe files changes) is not whitelisted\excluded in the currently installed security software. Moreover, probably a reboot would fix it somehow. [USER=55987]@HarborFront[/USER] It should work fine with HMPA, ESET, Windows OS, etc. [USER=58988]@Telos[/USER] Will fix that FP in the next build. [USER=46633]@Darrin[/USER] Yes, will add Pale Moon and other browsers to the list. [/QUOTE]

Verification