Dear Tropy team,
I am experiencing a Windows-specific issue that prevents Tropy from importing images.
After investigating the problem with Windows Code Integrity logs, I found that Smart App Control is blocking native components bundled with Tropy.
System
-
OS: Windows 11 Home
-
Windows build: 26200 (Windows 11 25H2)
-
Architecture: x64
-
Tropy stable: 1.17.3
-
Tropy beta tested: 1.18.0-beta.4
-
Smart App Control: enabled/enforcing
-
PowerShell: 7.6.6
The Windows registry reports:
VerifiedAndReputablePolicyState : 1
SAC_EnforcementReason : 1
CiTool also reports the active policy:
Policy ID: 0283ac0f-fff1-49ae-ada1-8a933130cad6
Friendly name: VerifiedAndReputableDesktop
Platform policy: true
Policy signed: true
Currently applied: true
Tropy 1.17.3
When importing an image, Tropy reports:
Failed to import items.
The original Tropy error indicated that Windows blocked:
C:\Users\theog\AppData\Local\tropy\app-1.17.3\
resources\app.asar.unpacked\lib\node\lib\sharp-win32-x64.node
The Code Integrity log then identified the underlying native library:
libvips-cpp-8.17.3.dll
Specifically, Windows Event ID 3033 reports that Tropy attempted to load this file but it “did not meet the Enterprise signing level requirements”.
Event ID 3077 reports the same block and identifies policy:
{0283AC0F-FFF1-49AE-ADA1-8A933130CAD6}
Tropy 1.18.0-beta.4
I also tested Tropy 1.18.0-beta.4 to determine whether the issue was specific to version 1.17.3.
The result is similar. Windows displays:
Smart App Control blocked a part of this app.
The Code Integrity log reports:
Event ID 3033:
Tropy attempted to load:
...\tropy-beta\app-1.18.0-beta4\
resources\app.asar.unpacked\lib\node\lib\node_sqlite3.node
The file did not meet the Enterprise signing level requirements.
And Event ID 3077 reports the same file and the same policy:
{0283AC0F-FFF1-49AE-ADA1-8A933130CAD6}
So the problem does not appear to be limited to libvips/sharp in Tropy 1.17.3. The 1.18.0-beta.4 build is also affected because another native component, node_sqlite3.node, is blocked.
Conclusion
It appears that Smart App Control / Code Integrity is preventing Tropy from loading native Windows binaries bundled with the application.
Tropy itself launches, but operations requiring these native components fail.
Could you please confirm whether the Windows binaries included with Tropy are expected to be compatible with Windows 11 Smart App Control, and whether a future release could provide appropriately signed/reputable native components?
I would be happy to provide the complete Code Integrity event logs or any additional diagnostic information you need.
Thank you very much for your help.
Best regards,