ST Edge AI Core 4.1.0 – Smart App Control blocks opt_merge_zero_pad.pyd on Windows 11
Subject: ST Edge AI Core 4.1.0 – Code Integrity blocks unsigned Python modules on Windows 11
Hello ST Support Team,
I am using ST Edge AI Core v4.1.0 (build 4.1.0.20732) with the STM32N6570-DK target to analyze a MobileNetV2 INT8 TFLite model.
When running the stedgeai analyze command, the process fails with the following error:
DLL load failed while importing opt_merge_zero_pad: A policy control application has blocked this file.
System information:
-
Windows 11 Pro, build 26200
-
Python 3.13.12
-
ST Edge AI Core 4.1.0 (build 4.1.0.20732)
-
STM32 MCU module v4.1.0
-
STM32N6 target
Additional investigation:
Windows Smart App Control is enabled.
I checked the Windows Code Integrity Operational log and found Event ID 3077 entries confirming that Windows blocks the following ST Edge AI Core modules:
-
frontend\concatenate_outputs.cp313-win_amd64.pyd -
middleend\opt_merge_zero_pad.cp313-win_amd64.pyd -
irs\base\memory_assets.cp313-win_amd64.pyd
The log reports that these files do not meet the Enterprise signing level requirements or violate the active code integrity policy.
I also checked the digital signatures of all .pyd files in the installation directory. All 438 files returned NotSigned using PowerShell's Get-AuthenticodeSignature command.
The SHA256 hash of opt_merge_zero_pad.cp313-win_amd64.pyd is:
FB22EB702ED7C268D9CF74502226A6F8DD1F659E38F9D2C459A39A694A3E5F0B
I have also checked the ST Maintenance Tool, but no updates are available. Restarting Windows did not resolve the issue.
Questions:
-
Are these
.pydmodules expected to be unsigned in ST Edge AI Core 4.1.0? -
Is this a known compatibility issue with Windows 11 Smart App Control or Code Integrity policies?
-
Is there an officially signed replacement, patch, or updated version available?
-
Is there a recommended and officially supported workaround that allows ST Edge AI Core to run without disabling Smart App Control?
I would appreciate your guidance, as this issue currently prevents me from analyzing models for the STM32N6 target.
Thank you for your assistance.
Best regards
