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
No reviewers
Labels
No labels
area/build
area/install
area/saves
area/tooling
area/ui
area/updates
ci: approved
good first issue
gpu/amd
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
platform/linux
platform/steam-deck
platform/windows
priority
critical
priority
high
priority
low
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/LongshotLauncher!137
Loading…
Reference in a new issue
No description provided.
Delete branch "HumanBean/LongshotLauncher:fix/directwrite-diagnostics"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The launcher still cannot start on Sanoku's PC (#123), and nothing yet says why: on that PC PowerShell loads
C:\WINDOWS\SYSTEM32\dwrite.dlland 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
DllNotFoundException, no DWriteCore.dll, Windows 10.0.26300.DWriteCreateFactoryandGetSystemFontCollectionsucceed, 192 families; Font Cache running; fonts and Segoe UI present.where DWriteCore.dll: none. CPU: Intel i9-10900K, AMD64 (no emulation).Change
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).sfc /scannow: the PC's fonts are fine.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 Releaseand-r win-x64build.python -I tests/test_launcher_core.pyandpython -I tests/test_release.pypass.No screenshots: the message only shows on a PC whose fonts fail.
🤖 Generated with Claude Code