Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Sign Flet Windows Client

オープン
  • 何か問題がありますか？
#7,011 コメント 8 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@FeodorFitsner がすでに取り組んでいます。

2026年10月27日 から。

  • #7016 @FeodorFitsner による — マージ済み

評価

この issue はまだ評価されていません。

説明

platform: windows

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

  1. Install Flet and Flet Desktop in a Python virtual environment.
  2. Run the application using python main.py.
  3. Windows blocks native DLL plugins loaded by the Flet desktop executable.
  4. 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.dll
  • flutter_secure_storage_windows_plugin.dll
  • local_auth_windows_plugin.dll
  • geolocator_windows_plugin.dll
  • rive_native_plugin.dll
  • record_windows_plugin.dll
  • media_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

  1. Is this a known compatibility issue between the Flet desktop runtime's native plugins and Windows Smart App Control?
  2. Is there an official signed or otherwise compatible Flet Desktop runtime that works with Smart App Control enabled?
  3. Are all the listed plugins required for desktop startup, or can unused plugins be excluded through a supported configuration?
  4. 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.

主要言語
Python
スター
17.4k
フォーク
737
平均マージ
1日 14時間
マージ済み PR（30日）
62

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

flet-dev/flet のほかの issue

flet-dev/flet の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。