fix(windows): the no-fonts message says why Windows would not load DirectWrite in the launcher, and DLLs are looked up as before (#123) #137

Merged
HumanBean merged 1 commit from HumanBean/LongshotLauncher:fix/directwrite-diagnostics into main 2026-11-16 06:20:25 +00:00
Owner

The launcher still cannot start on Sanoku's PC (#123), and nothing yet says why: on that PC PowerShell loads C:\WINDOWS\SYSTEM32\dwrite.dll and DirectWrite lists 192 font families, but inside the launcher the same DLL is "not found", so the cause is something that holds only the launcher's process back.

What we know

  • Nightly 99's message (from #134): Skia 0 font families, DirectWrite DllNotFoundException, no DWriteCore.dll, Windows 10.0.26300.
  • Sanoku's PowerShell check: DWriteCreateFactory and GetSystemFontCollection succeed, 192 families; Font Cache running; fonts and Segoe UI present.
  • where DWriteCore.dll: none. CPU: Intel i9-10900K, AMD64 (no emulation).
  • Most likely: security software that runs unknown, unsigned programs with restrictions.

Change

  • The no-fonts message adds:
    • dwrite.dll from System32: loaded by its full path, with Windows' error number and text when it fails.
    • Restrictions: the process's mitigation policies (dynamic code, signature, image load, child process, side channel) when any is set.
    • Other modules: up to 12 DLLs in the process that are neither Windows' nor the launcher's own (security software, overlays).
    • The process's architecture.
  • Its advice names security software instead of sfc /scannow: the PC's fonts are fine.
  • #134's narrowed DLL search (SetDefaultDllDirectories) is taken back: no DWriteCore.dll was the cause, and Windows' own dwrite.dll failed to load all the same. The DWriteCore.dll lookup stays, for the message.

Tests

  • dotnet build App -c Release and -r win-x64 build.
  • python -I tests/test_launcher_core.py and python -I tests/test_release.py pass.
  • Not run on Windows.

No screenshots: the message only shows on a PC whose fonts fail.

🤖 Generated with Claude Code

The launcher still cannot start on Sanoku's PC (#123), and nothing yet says why: on that PC PowerShell loads `C:\WINDOWS\SYSTEM32\dwrite.dll` and DirectWrite lists 192 font families, but inside the launcher the same DLL is "not found", so the cause is something that holds only the launcher's process back. ## What we know - Nightly 99's message (from #134): Skia 0 font families, DirectWrite `DllNotFoundException`, no DWriteCore.dll, Windows 10.0.26300. - Sanoku's PowerShell check: `DWriteCreateFactory` and `GetSystemFontCollection` succeed, 192 families; Font Cache running; fonts and Segoe UI present. - `where DWriteCore.dll`: none. CPU: Intel i9-10900K, AMD64 (no emulation). - Most likely: security software that runs unknown, unsigned programs with restrictions. ## Change - The no-fonts message adds: - `dwrite.dll from System32`: loaded by its full path, with Windows' error number and text when it fails. - `Restrictions`: the process's mitigation policies (dynamic code, signature, image load, child process, side channel) when any is set. - `Other modules`: up to 12 DLLs in the process that are neither Windows' nor the launcher's own (security software, overlays). - The process's architecture. - Its advice names security software instead of `sfc /scannow`: the PC's fonts are fine. - #134's narrowed DLL search (`SetDefaultDllDirectories`) is taken back: no DWriteCore.dll was the cause, and Windows' own dwrite.dll failed to load all the same. The DWriteCore.dll lookup stays, for the message. ## Tests - `dotnet build App -c Release` and `-r win-x64` build. - `python -I tests/test_launcher_core.py` and `python -I tests/test_release.py` pass. - Not run on Windows. No screenshots: the message only shows on a PC whose fonts fail. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
fix(windows): the no-fonts message says why Windows would not load DirectWrite in the launcher, and DLLs are looked up as before (#123)
All checks were successful
CI / Compile and test (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 3s
73f86333a1
The no-fonts message now gives dwrite.dll's load from System32 with Windows' error, the restrictions Windows holds the process to,
the DLLs other software put in it, and the process's architecture. #134's narrowed DLL search is taken back: no DWriteCore.dll was
the cause, and Windows' own dwrite.dll failed to load all the same.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
HumanBean deleted branch fix/directwrite-diagnostics 2026-11-16 06:20:25 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/LongshotLauncher!137
No description provided.