Support Board
Date/Time: Tue, 13 Oct 2026 17:14:42 +0000
Post From: Windows 11 Smart App Control Blocking ACSIL DLLs — Would Local Compilation Help?
| [2026-10-13 13:52:26] |
| User235392 - Posts: 1 |
|
I'm brand new to Sierra Chart. I'm using Sierra Chart 2957 on Windows 11 with Smart App Control enabled. I've successfully compiled and loaded several custom ACSIL studies using Sierra Chart's Remote Build service. However, a newly compiled DLL is being blocked by Windows Application Control (Windows error 4551). Windows Event Viewer reports Code Integrity events 3033 and 3077, indicating that the DLL does not meet the required signing policy. Both the blocked DLL and my other working custom DLLs report NotSigned in PowerShell. I found two related discussions on the Support Board: Thread 105430 (Smart App Control - Windows 11) Thread 107091 (Windows Smart App Control blocked UserContributedStudies_64.dll) I understand that disabling Smart App Control may resolve the problem, but I would prefer to keep it enabled, particularly because turning it off generally cannot be reversed without resetting or reinstalling Windows. My questions are: Would compiling ACSIL studies locally, rather than using Sierra Chart's Remote Build service, help avoid this issue? Is there a recommended local compiler or build configuration for Sierra Chart 2957? Is there another supported approach for developing and loading custom ACSIL DLLs while keeping Smart App Control enabled? I'd appreciate any guidance on a practical development workflow that doesn't require disabling Windows security protections or purchasing a code-signing certificate. Thank you. |