Windows v3.1.2 launch crash: `0xc0000142` / `APPCRASH` in `VCRUNTIME140_1.dll`

[marksftw]

Summary

A Windows user can download and install Maple v3.1.2, but launching the installed app fails immediately with:

The application was unable to start correctly (0xc0000142).

Reliability Monitor reports an APPCRASH for maple.exe with fault module VCRUNTIME140_1.dll and exception code c000001d.

Affected Version

• Maple: 3.1.2
• Installer: Maple_3.1.2_x64-setup.exe
• Install path: C:\Users\JohnSmith\AppData\Local\Maple\maple.exe

User Environment

Windows edition: Windows 11 Business
OS Version: 10.0.26200.2.0.0.256.48

CPU:
Name: Intel(R) Core(TM) Ultra 5 236V
Manufacturer: GenuineIntel
Architecture: 9
AddressWidth: 64

This is a modern Intel x64 machine, so this does not appear to be an ARM/wrong-architecture issue.

Reliability Monitor Report

Source
Maple

Summary
Stopped working

Date
6/29/2026 3:17 PM

Status
Report sent

Description
Faulting Application Path: C:\Users\JohnSmith\AppData\Local\Maple\maple.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: maple.exe
Application Version: 3.1.2.0
Application Timestamp: 6a42b058
Fault Module Name: VCRUNTIME140_1.dll
Fault Module Version: 14.44.35211.0
Fault Module Timestamp: c5fb6649
Exception Code: c000001d
Exception Offset: 0000000000005548
OS Version: 10.0.26200.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 808d
Additional Information 2: 808dc6839912c3ba4f96f4db52bcb753
Additional Information 3: 2e97
Additional Information 4: 2e97d496fde0870caccfa5145bbcac1d

Bucket ID: 3322289121a678b8f723cf4ec162fb00 (1667404224216103680)

Notes From Testing

• Another Windows machine was able to:
  • keep the installer after SmartScreen warning,
  • run the installer,
  • launch Maple successfully.
• So this does not appear to be a universal installer failure.
• SmartScreen/download reputation is a separate issue and should not be conflated with this launch crash.

Relevant Packaging Details

The Windows package intentionally installs runtime DLLs next to maple.exe:

onnxruntime.dll
VCRUNTIME140.dll
VCRUNTIME140_1.dll
MSVCP140.dll
MSVCP140_1.dll

The release manifest includes:

VCRUNTIME140_1.dll
42b5f76f1f0ae03c93fc4c107adf83c5f14e86032474860032cfe672d0836546

onnxruntime.dll
579b636403983254346a5c1d80bd28f1519cd1e284cd204f8d4ff41f8d711559

The app-local VC runtime version matches the crash report:

VCRUNTIME140_1.dll 14.44.35211.0

The app also links ONNX Runtime 1.22.0 for TTS. Based on repo docs, maple.exe has a load-time dependency on onnxruntime.dll, which means a TTS-related native dependency can affect startup before the app UI appears.

Suspected Cause

This looks like a native startup dependency failure in the bundled Windows runtime stack.

Exception Code: c000001d means illegal instruction. Since the CPU is modern x64, the most likely area to investigate is the app-local native DLL set, especially the interaction between:

• maple.exe
• bundled onnxruntime.dll 1.22.0
• bundled VC++ runtime DLLs from 14.44.35211

Even though Reliability Monitor names VCRUNTIME140_1.dll, the root trigger may be another native dependency calling into it during process initialization.

Recommendations

1. Avoid loading ONNX Runtime at app startup on Windows.

   • Use dynamic loading on Windows as Linux already does with ort load-dynamic.
   • Initialize ONNX/TTS only when the user actually uses TTS.

2. Make TTS failure non-fatal.

   • If ONNX Runtime fails to load or initialize, Maple should still launch.
   • Show an in-app “Voice/TTS unavailable” error instead of failing the whole process.

3. Ship a temporary Windows hotfix build without TTS/ONNX startup dependency.

   • This is the least invasive way to confirm the suspected root cause.
   • The affected user should only need to try a replacement installer, not run more diagnostics.

4. Consider testing with a different VC++ redistributable bundle.

   • The fault module is VCRUNTIME140_1.dll version 14.44.35211.0.
   • If ONNX deferral does not fix it, try a build using a previous known-stable VC runtime version.

5. Add a Windows startup smoke test.

   • Fresh install on Windows 11.
   • Launch app before any TTS model download/use.
   • Verify startup does not depend on ONNX Runtime successfully initializing.

Desired Outcome

Maple should launch successfully even if ONNX Runtime, TTS, or app-local native runtime initialization fails. Native optional features should degrade gracefully after startup.