In short, yes. AppLocker will generally take effect at double-click scenarios and be the mechanism that performs blocking of the application. This has implications and workarounds if you want to add PolicyPak Least Privilege Manager to an existing Microsoft Applocker deployment.
Here is a PolicyPak Least Privilege Manager direct rule which would take effect when a user double-clicks an application, like Procmon which would normally throw a UAC prompt.
The result is that a double-click of the application is still blocked by Applocker as shown here.
However, the user may be taught to right-click and “Run with PolicyPak” which will then perform the direct rule operation and elevate the application. An example of the steps can be seen here.
Note that the “Apply on demand” checkbox for direct rules will have no effect while Applocker is running.
When PolicyPak Admin Approval is on, once again, double-click is blocked by Applocker.
However, right-click “Run with PolicyPak” then provides the Admin Approval prompt. Both Short codes and Long codes work as expected.
PolicyPak SecureRun is different from AppLocker because it can key off the file ownership / SecureRun member.
With SecureRun™ is run alongside Applocker, there is no difference to the statements above, except you also get all the added benefits of SecureRun are enabled as expected. This is not a recommended configuration but it should work. Please consider retiring Applocker and using PolicyPak SecureRun. See our recommendations why in this article: https://blog.netwrix.com/2021/12/02/applocker-pros-cons-and-alternatives/