Jump to content

Some MBAE installation executables are unsigned


Recommended Posts

wondered why this is. A signature for an executable file is some assurance of authenticity. I started this thread because I needed to add an exclusion to OSArmor to allow MBAE to update automatically so that I can prevent unwanted unsigned processes running in Windows temp folder. Not being as bright as I would like to think I am, this took a bit of time to get right but MBAE can at last happily update without OSArmor stopping the process.

The OSArmor exclusion rule for MBAE update reads as follows:-
[%PROCESS%: C:\Windows\Temp\is-*.tmp\mbae-setup-*.tmp] [%PARENTPROCESS%: C:\Windows\Temp\mbae-setup-*.exe] [%PARENTSIGNER%: Malwarebytes Inc]

MBARW seems to be exempt from this fun, both at installation and at update.

Edited by hake
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.