本版更新

针对商店审核「启动即崩溃」(10.1.2.10) 的第二轮加固。

修复

运行时升级：自包含运行时从 .NET 10.0.8（2026-05）升级到 10.0.12（2026-09），包含其间四轮服务更新的全部运行时修复。审核报告中两轮崩溃点位于 .NET 运行时内部（coreclr.dll 同一偏移），升级运行时是最直接的修复
启动路径加固：启动用的隐藏主窗口（热键消息宿主，0x0 大小、立即隐藏）不再创建为分层透明窗口——分层窗口在部分核显驱动上是 WPF 渲染线程致命错误的已知雷区，从启动路径上移除；窗口本身不可见，行为零变化

启动分步追踪：启动流程的 10 个里程碑（进程启动 → 数据目录 → 配置 → 主窗口 → 托盘 → 分区初始化 → 完成）逐步落盘到 startup-trace.log，每步立即写盘。若再出现启动问题，日志最后一行即死亡边界，可为定位提供确切证据

Second round of hardening for the Store certification launch crash (10.1.2.10).

Runtime upgrade: the self-contained runtime moves from .NET 10.0.8 (May 2026) to 10.0.12 (Sep 2026), carrying all runtime fixes from four servicing rounds in between. Both certification crashes landed inside the .NET runtime itself (same coreclr.dll offset), so upgrading the runtime is the most direct fix
Startup path hardening: the hidden helper window used at startup (hotkey message host, 0x0 size, immediately hidden) is no longer created as a layered transparent window — layered windows are a known danger zone for WPF render-thread fatal errors on some integrated-GPU drivers. The window is invisible, so behavior is unchanged

Step-by-step startup trace: ten startup milestones (process start → data directory → config → main window → tray → zones → done) are appended to startup-trace.log and flushed to disk at every step. If a launch issue ever reappears, the last line in the log marks the exact death boundary