Launcher: Windows rc.8 setup does nothing after SmartScreen Run anyway #123

Closed
opened 2026-11-15 22:56:03 +00:00 by BeanBot · 13 comments
Member

Reported by Sanoku on Discord

What happened

On Windows 11, running LongshotLauncher-v1.0.0-rc.8-windows-x64-setup.exe shows 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

  1. Download the Windows setup from the official release page.
  2. Open it and choose Run anyway in SmartScreen (or disable SmartScreen).
  3. Observe that setup does not start. The same failure is reported for rc.6, rc.7, rc.8, rc.9, and the current nightly.

System

  • OS: Windows 11
  • The rc.9 WER report gives Windows build 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 in Avalonia.Media.FontManager.GetDefaultFontFamilyName(FontManagerOptions options) and terminates the process as an unhandled exception. Event Viewer reports APPCRASH with faulting module KERNELBASE.dll, exception code 0xe0434352; report ID 178a165c-0bcb-4746-9b71-bd7e5b8fbb31.

Missing information

  • Exact nightly version/build and setup filename
  • Whether each download completed and the file size for each version
  • Any Windows Security/Protection History entries
  • Launcher/setup log, if available
  • Windows 11 edition/version details beyond the build above

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.txt on Discord.

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.

Reported by [Sanoku on Discord](https://discord.com/channels/1569849200047427645/1570784344241340417/1571658899012976692) ### What happened On Windows 11, running `LongshotLauncher-v1.0.0-rc.8-windows-x64-setup.exe` shows 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 1. Download the Windows setup from the official release page. 2. Open it and choose **Run anyway** in SmartScreen (or disable SmartScreen). 3. Observe that setup does not start. The same failure is reported for rc.6, rc.7, rc.8, rc.9, and the current nightly. ### System - OS: Windows 11 - The rc.9 WER report gives Windows build `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 in `Avalonia.Media.FontManager.GetDefaultFontFamilyName(FontManagerOptions options)` and terminates the process as an unhandled exception. Event Viewer reports APPCRASH with faulting module `KERNELBASE.dll`, exception code `0xe0434352`; report ID `178a165c-0bcb-4746-9b71-bd7e5b8fbb31`. ### Missing information - Exact nightly version/build and setup filename - Whether each download completed and the file size for each version - Any Windows Security/Protection History entries - Launcher/setup log, if available - Windows 11 edition/version details beyond the build above 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.txt` on Discord. ### Related fix The older Windows packaging issue was fixed in [PR #37](https://git.magicbean.dev/MagicBeanDev/LongshotLauncher/pulls/37), first included in v1.0.0-rc.3. It does not explain this separate startup crash.
Author
Member

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.

From [Sanoku on Discord](https://discord.com/channels/1569849200047427645/1570784344241340417/1571658899012976692): 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.
Author
Member

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](https://discord.com/channels/1569849200047427645/1571658899012976692/1571667229639184385): Added that rc.7 and rc.6 also fail to start, alongside rc.8 even after SmartScreen was disabled and the installer redownloaded.
Author
Member

Updated with more from Sanoku on Discord: Added that the current nightly also fails; exact nightly version and installer details remain unknown.

Updated with more from [Sanoku on Discord](https://discord.com/channels/1569849200047427645/1571658899012976692/1571667552759840800): Added that the current nightly also fails; exact nightly version and installer details remain unknown.
Author
Member

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](https://discord.com/channels/1569849200047427645/1570784344241340417/1571658899012976692): 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.
Author
Member

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 version 10.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 is 178a165c-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.

From [Sanoku on Discord](https://discord.com/channels/1569849200047427645/1570784344241340417/1571658899012976692): 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 version `10.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 is `178a165c-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.
Author
Member

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.

Updated with more from [Sanoku on Discord](https://discord.com/channels/1569849200047427645/1571658899012976692/1571676571339718711): Added the .NET runtime exception and stack-trace diagnosis from the user's attachment, clarifying the rc.9 setup failure.
Author
Member

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 empty during Avalonia font-manager initialization. The issue remains unresolved.

From [Sanoku on Discord](https://discord.com/channels/1569849200047427645/1570784344241340417/1571658899012976692): 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 empty` during Avalonia font-manager initialization. The issue remains unresolved.
Author
Member

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 module KERNELBASE.dll, exception 0xe0434352, Windows build 10.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 on Discord](https://discord.com/channels/1569849200047427645/1570784344241340417/1571658899012976692): Sanoku reports the failure persists in `LongshotLauncher-nightly-98-476965b3-windows-x64-setup.exe`, despite PR #131 being included. Event Viewer reports APPCRASH (faulting module `KERNELBASE.dll`, exception `0xe0434352`, Windows build `10.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.
Owner

From Sanoku

From Sanoku
Author
Member

From Sanoku on Discord:

Sanoku reports the failure persists in LongshotLauncher-nightly-99-c5e27ee0-windows-x64-setup.exe on Windows 11 (build 10.0.26100.9974). The attached .NET runtime log now shows System.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 exception 0xe0434352 (Report ID 40c5fee0-33a5-42a6-a783-221e6a2727b1). This is a follow-up failure after PR #131 fixed the missing-default-font crash in nightly-98.

From [Sanoku on Discord](https://discord.com/channels/1569849200047427645/1570784344241340417/1571658899012976692): Sanoku reports the failure persists in `LongshotLauncher-nightly-99-c5e27ee0-windows-x64-setup.exe` on Windows 11 (build 10.0.26100.9974). The attached .NET runtime log now shows `System.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 exception `0xe0434352` (Report ID `40c5fee0-33a5-42a6-a783-221e6a2727b1`). This is a follow-up failure after PR #131 fixed the missing-default-font crash in nightly-98.
Owner

Should be fixed in nightly

Should be fixed in nightly
Author
Member

From Sanoku on Discord:

Sanoku reports the latest failure now displays a diagnostic dialog rather than silently failing. Screenshot shows Could not create glyphTypeface for embedded Inter DemiBold; Skia reports 0 font families, DirectWrite reports DllNotFoundException: 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](https://discord.com/channels/1569849200047427645/1571692349463986377/1571692349463986377): Sanoku reports the latest failure now displays a diagnostic dialog rather than silently failing. Screenshot shows `Could not create glyphTypeface` for embedded Inter DemiBold; Skia reports 0 font families, DirectWrite reports `DllNotFoundException: 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.
Author
Member

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 Avalonia FontManager initialization in LongshotLauncher-v1.0.0-rc.9-windows-x64-setup.exe. Event Viewer reports KERNELBASE.dll, exception 0xe0434352, Windows build 10.0.26100.9974, report ID 79dcc67f-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.

From [Sanoku on Discord](https://discord.com/channels/1569849200047427645/1571692349463986377/1571752993873723393): Sanoku additionally attached the rc.9 .NET runtime stack trace, confirming `System.InvalidOperationException: Default font family name can't be null or empty.` during Avalonia `FontManager` initialization in `LongshotLauncher-v1.0.0-rc.9-windows-x64-setup.exe`. Event Viewer reports KERNELBASE.dll, exception `0xe0434352`, Windows build 10.0.26100.9974, report ID `79dcc67f-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.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
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#123
No description provided.