Launcher: Windows rc.8 setup does nothing after SmartScreen Run anyway #123
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/LongshotLauncher#123
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Reported by Sanoku on Discord
What happened
On Windows 11, running
LongshotLauncher-v1.0.0-rc.8-windows-x64-setup.exeshows a Microsoft Defender SmartScreen dialog identifying the publisher as Unknown publisher. After clicking Run anyway, nothing happens and the setup does not start. Disabling SmartScreen and redownloading did not resolve it. The user also reports rc.6, rc.7, rc.9, and the current nightly fail to start/install.Steps to reproduce
System
10.0.26100.9974.Error details
For
LongshotLauncher-v1.0.0-rc.9-windows-x64-setup.exe, the .NET runtime report states:System.InvalidOperationException: Default font family name can't be null or empty.The exception originates inAvalonia.Media.FontManager.GetDefaultFontFamilyName(FontManagerOptions options)and terminates the process as an unhandled exception. Event Viewer reports APPCRASH with faulting moduleKERNELBASE.dll, exception code0xe0434352; report ID178a165c-0bcb-4746-9b71-bd7e5b8fbb31.Missing information
The user said no launcher log was available. The screenshot shows SmartScreen's “Windows protected your PC” warning and “Publisher: Unknown publisher.” The .NET exception stack trace was provided in
message.txton Discord.Related fix
The older Windows packaging issue was fixed in PR #37, first included in v1.0.0-rc.3. It does not explain this separate startup crash.
From Sanoku on Discord:
Sanoku reports that they completely disabled Microsoft Defender SmartScreen and redownloaded the rc.8 setup, but it still does not launch. This suggests the failure is not resolved by bypassing SmartScreen. No additional log or Windows error details were provided.
Updated with more from Sanoku on Discord: Added that rc.7 and rc.6 also fail to start, alongside rc.8 even after SmartScreen was disabled and the installer redownloaded.
Updated with more from Sanoku on Discord: Added that the current nightly also fails; exact nightly version and installer details remain unknown.
From Sanoku on Discord:
Sanoku reports that v1.0.0-rc.9 also fails in the same way: “rc.9 just came out and sameissue.” Exact rc.9 setup filename and file size, Windows build, and any Windows Security/Event Viewer error remain unknown.
From Sanoku on Discord:
Sanoku provided a Windows Error Reporting APPCRASH for
LongshotLauncher-v1.0.0-rc.9-windows-x64-setup.exe. Event Name:APPCRASH; faulting module:KERNELBASE.dll; exception code (P7):e0434352; Windows version10.0.26100.9974. This gives the exact rc.9 installer filename and a crash report, but the underlying exception details/dump were not attached. The report ID is178a165c-0bcb-4746-9b71-bd7e5b8fbb31. The older packaging issue is covered by PR #37 (included in rc.3), but does not account for this distinct rc.9 crash.Updated with more from Sanoku on Discord: Added the .NET runtime exception and stack-trace diagnosis from the user's attachment, clarifying the rc.9 setup failure.
From Sanoku on Discord:
Sanoku says Google AI indicated the default-font exception must be fixed by the developer. No new diagnostic evidence was added; the existing runtime log already identifies
Default font family name can't be null or emptyduring Avalonia font-manager initialization. The issue remains unresolved.From Sanoku on Discord:
Sanoku reports the failure persists in
LongshotLauncher-nightly-98-476965b3-windows-x64-setup.exe, despite PR #131 being included. Event Viewer reports APPCRASH (faulting moduleKERNELBASE.dll, exception0xe0434352, Windows build10.0.26100.9974). The accompanying runtime log reportedly shows a later failure while creating the bundled Inter DemiBold glyph typeface. Please investigate this follow-up startup failure.From Sanoku
From Sanoku on Discord:
Sanoku reports the failure persists in
LongshotLauncher-nightly-99-c5e27ee0-windows-x64-setup.exeon Windows 11 (build 10.0.26100.9974). The attached .NET runtime log now showsSystem.InvalidOperationException: Could not create glyphTypeface. Font family: Inter (key: avares://LongshotLauncher/Assets/Fonts). Style: Normal. Weight: DemiBold. Stretch: Normal, failing during Avalonia text shaping/layout at initial window display. Event Viewer reports KERNELBASE.dll and exception0xe0434352(Report ID40c5fee0-33a5-42a6-a783-221e6a2727b1). This is a follow-up failure after PR #131 fixed the missing-default-font crash in nightly-98.Should be fixed in nightly
From Sanoku on Discord:
Sanoku reports the latest failure now displays a diagnostic dialog rather than silently failing. Screenshot shows
Could not create glyphTypefacefor embedded Inter DemiBold; Skia reports 0 font families, DirectWrite reportsDllNotFoundException: Dll was not found, and no DWriteCore was found, on Windows 10.0.26300.0. Sanoku says they will try restarting first. This follow-up failure is addressed by PR #134.From Sanoku on Discord:
Sanoku additionally attached the rc.9 .NET runtime stack trace, confirming
System.InvalidOperationException: Default font family name can't be null or empty.during AvaloniaFontManagerinitialization inLongshotLauncher-v1.0.0-rc.9-windows-x64-setup.exe. Event Viewer reports KERNELBASE.dll, exception0xe0434352, Windows build 10.0.26100.9974, report ID79dcc67f-3b42-4ee7-a931-2645048d3f42. The latest launcher nightly still displays the separate no-font diagnostic (DirectWrite DllNotFoundException, DWriteCore none found; Windows 10.0.26300.0); the main-site updates link reportedly does not open.