Windows Smart App Control does not allow latest wacup to run

[Nik22]

Hi,

I've updated to the latest 64bit of wacup but windows smart app control does not allow it to run.
What should i do?

Thank you.

[dro]

There's little that can be done if it doesn't want to allow things to run as trying to circumvent it will just exacerbate the problem with the not so smart way that app control appears to work. The only thing is disabling it but I'm not keen on that as a solution (same for doing things like turning off UAC for other problems). Maybe trying to install as a portable install might not have the same issue or by trying to use the x86 build instead if it still won't allow the x64 build to be installed.

[Obsidiann6]

Having the same issue with my Wacup 1.99.53.24784 32-bit on Windows 11. 75% of the times it gets blocked by Microsofts Smart App Control (https://support.microsoft.com/en-US/Windows/Security/Threat-Malware-Protection/smart-app-control-has-blocked-part-of-this-app). Is there not a way to sign the application and DLLs, so that Microsoft trusts it?

[dro]

Code-signing has zero guarantee it'll help & with the way that I'm doing wacup I just am not happy with what is required to attempt to get a code license from having to provide all of my personal information along with the exorbitant cost of keeping it renewed every year (the mess with notepad++'s code license from earlier in the year also imho showed up just how flawed & dodgy the whole code licensing setup is).

As for smart app control itself, it's not smart & is just inconsistent in it's behaviour re: bottom of https://getwacup.com/false_positives.html

[Lyric Video Studio]

Hi, fellow dev here. IV (or open source) code signing certificate DOES help you to get over the SmartScreen, but it takes time for it to start trusting it completely (enough "I trust this"-clicks). But, you're right, that it's very annoying to set up + renew often (no longer 3 years max!!!) and it does cost, sadly... IMO the whole SmartScreen / code signing thingie is broken in the core, it only checks the exe file signing, but not the underlying dll's and certainly not anything else that the exe might launch XD