Sign Flet Windows Client
Los mantenedores suelen responder en 1 día
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Description
I'm developing a Python application using Flet on Windows. The Flet desktop application fails to launch because Windows Code Integrity blocks multiple native DLL plugins under the Flet desktop runtime.
Windows displays “flet.exe - Bad Image” dialogs with error status 0xC0E90002. The corresponding Code Integrity events are Event ID 3077 and reference policy ID {0283ac0f-fff1-49ae-ada1-8a933130cad6}.
I would like to run Flet Desktop while keeping Windows Smart App Control enabled.
Environment
- OS: Windows (Smart App Control enabled)
- Python: 3.10.5
- Flet: 1.0.5
- Flet Desktop: 1.0.5
- Flet CLI: 1.0.5
- Project type: Python desktop application
- Previous Flet Desktop version tested: 1.0.3
Steps to reproduce
- Install Flet and Flet Desktop in a Python virtual environment.
- Run the application using
python main.py. - Windows blocks native DLL plugins loaded by the Flet desktop executable.
- Launch the cached desktop executable directly to reproduce the error.
Actual behaviour
The application does not open successfully. Running python main.py returns to the PowerShell prompt without displaying a Python traceback.
Launching the desktop executable directly produces Windows “Bad Image” dialogs with error status 0xC0E90002.
Code Integrity Event ID 3077 reports that the desktop process attempted to load DLLs that did not meet the signing-level requirements or violated the active code-integrity policy.
The following DLLs have been observed in the blocked-event logs:
audioplayers_windows_plugin.dllflutter_secure_storage_windows_plugin.dlllocal_auth_windows_plugin.dllgeolocator_windows_plugin.dllrive_native_plugin.dllrecord_windows_plugin.dllmedia_kit_libs_windows_video_plugin.dll
The affected runtime is located under:
%USERPROFILE%\.flet\client\flet-desktop-full-1.0.5\flet\
PowerShell's Get-AuthenticodeSignature reports NotSigned for the tested desktop executable and DLLs.
Code Integrity event details
- Event ID:
3077 - Policy ID:
{0283ac0f-fff1-49ae-ada1-8a933130cad6} - Windows error status:
0xC0E90002 - Process:
flet.exe - Reproduction observed: 27 October 2026, approximately 9:53–9:57 PM local time
Version comparison
The issue was first observed with Flet Desktop 1.0.3. I upgraded flet, flet-desktop, and flet-cli to 1.0.5, but the problem persisted with the new cached runtime.
Expected behaviour
Flet Desktop should launch successfully on a supported Windows configuration with Smart App Control enabled, without required native plugins being blocked by Code Integrity.
Questions
- Is this a known compatibility issue between the Flet desktop runtime's native plugins and Windows Smart App Control?
- Is there an official signed or otherwise compatible Flet Desktop runtime that works with Smart App Control enabled?
- Are all the listed plugins required for desktop startup, or can unused plugins be excluded through a supported configuration?
- Is there a recommended diagnostic or workaround that does not require disabling Windows security protections?
I can provide screenshots of the “Bad Image” dialogs and the relevant Code Integrity event logs if needed.
Thank you for your help.
- Lenguaje dominante
- Python
- Estrellas
- 17.4k
- Forks
- 737
- Merge medio
- 1 d 13 h
- PR fusionados (30 d)
- 62
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de flet-dev/flet
-
feature: python 3.15 supportAbiertofeature request
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
flet-dev/flet#6985 · 2 comentarios · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
flet build: common [tool.flet.deep_linking] is ignored on Android and iOSPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertobug packaging platform: mobile
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
bug: `flet test` fails with `ModuleNotFoundError: No module named 'pydantic_core._pydantic_core'`Posiblemente ocupada @ndonkoHenri la tomó hace 1 día. Abiertobug
flet-dev/flet#7022 · 3 comentarios · 1 reacción · 1 asignado ·
Los mantenedores suelen responder en 1 día
Todos los issues de flet-dev/flet
Issues similares
-
priority middle
Dificultad 1/5 Menos de una hora Aptitud para principiantes 62/100
KATO-Hiro/AtCoderClans#12940 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 76/100
huggingface/huggingface_hub#5283 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
ccxt/ccxt#31045 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug example
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
Los mantenedores suelen responder en 1 día