OpenClaw Companion crashes on startup with .NET Runtime error 0x80131506 #1706

Activity

1. github-project-automation

   added this to Windows Companion Appon Oct 12, 2026
2. clawsweeper

   added

   P0Emergency: data loss, security bypass, crash loop, or unusable core runtime.Emergency: data loss, security bypass, crash loop, or unusable core runtime.

   clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.ClawSweeper marked this issue as needing maintainer review before automation.

   clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.

   impact:crash-loopThis issue is about crashes, hangs, restart loops, or process-level availability.This issue is about crashes, hangs, restart loops, or process-level availability.

   impact:ux-release-blockerA non-technical user is blocked without terminal, logs, config, or support.A non-technical user is blocked without terminal, logs, config, or support.

   issue-rating: 🦪 silver shellfishThin issue quality; more reproduction proof or environment detail is needed.Thin issue quality; more reproduction proof or environment detail is needed.

   on Oct 12, 2026
3. clawsweeper commented on Oct 12, 2026

   

   clawsweeperBot

   on Oct 12, 2026 – with ClawSweeper

   Last edited by clawsweeper

   More actions

   Codex review: this still needs some work.

   Summary
   Keep open: this issue documents an official-release startup failure, and neither current source nor related fixes establish that the reported CoreCLR error is resolved.

   Reproducibility: no. high-confidence current-main reproduction is available: the release, OS, runtime version, and fatal event are documented, but the native stack and loaded module paths are absent; this read-only review ran no application, builds, or tests.

   Next step
   Provide guided collection of redacted native failure details and loaded runtime versions, then select a targeted repair with a visible recovery launcher.

   Review details

   Best possible solution:

   Repair the diagnosed startup failure and provide a visible Doctor or recovery launcher that remains accessible when Companion cannot start.

   Do we have a high-confidence way to reproduce the issue?

   No high-confidence current-main reproduction is available: the release, OS, runtime version, and fatal event are documented, but the native stack and loaded module paths are absent; this read-only review ran no application, builds, or tests.

   Is this the best way to solve the issue?

   A targeted repair needs native failure evidence first; reinstalling system .NET or applying fixes for different XAML and shell failures does not establish a solution.

   AGENTS.md: found and applied where relevant.

   Remaining risk / open question:

   • The native failure stack and loaded runtime paths are missing, leaving application, bundled-runtime, and operating-system compatibility causes unresolved.
   • No current-main reproduction or reporter-confirmed repair establishes resolution.

   Codex review notes: model internal, reasoning medium; reviewed against d318127350b5.

   Label changes

   Label changes:

   No label changes.

   Label justifications:

   • P0: The non-technical reporter cannot reach first launch after reinstalling the official release, and further diagnosis requires external tools or support.
   • impact:crash-loop: Every reported launch terminates Companion before its tray icon appears; automatic restart looping is not established.
   • impact:ux-release-blocker: The startup failure prevents access to onboarding and in-app diagnostics, with no demonstrated in-product recovery.

   Evidence reviewed

   What I checked:

   • Concrete released-app failure and unanswered diagnostic request: The full issue reports v2026.9.8-1 terminating on Windows 11 build 22000.194 with Event 1023, coreclr.dll, and 0x80131506 despite reinstalling; the reporter's follow-up explicitly identifies them as non-technical and asks for guided diagnostic collection. The full comments and timeline contain no fixing PR or successful retest.
   • Published operating-system expectations: The current README advertises Windows 10 20H2 or later, or Windows 11; it does not exclude the reported Windows 11 build. (README.md:23, d318127350b5)
   • Runtime packaging and existing workaround: The x64 release publish command uses --self-contained. Current main and the affected release's project file both contain the production Debugger.IsSupported=false workaround; merged fix: prevent .NET 10 COM wrapper memory leak in production #1215 (fix: prevent .NET 10 COM wrapper memory leak in production) addresses retained COM wrappers rather than establishing a repair for this immediate fatal startup error. (.github/workflows/ci.yml:1057, d318127350b5)
   • Startup diagnostic boundary: App registers managed exception handlers after InitializeComponent and run-marker initialization. Diagnostics export requires the running DebugPage, while its Doctor action targets a WSL Gateway; these paths do not demonstrate recovery from an earlier fatal Companion runtime failure. (src/OpenClaw.Tray.WinUI/App.xaml.cs:312, d318127350b5)
   • Existing tests do not establish this failure is fixed: StartupWindowUiTests exercises configured, unconfigured, restarted, and corrupt-identity launches; DiagnosticsBundleBuilderTests checks sanitized log export. Neither inspected test supplies the reported OS/runtime failure scenario, and no tests were executed during this read-only review. (tests/OpenClaw.Tray.UITests/StartupWindowUiTests.cs:14, d318127350b5)
   • Canonical search distinguishes nearby failures: Searches across issues and PRs for the exact error, CoreCLR, startup crashes, build 22000, and references to this issue found no verified fixing item. [Bug] Windows Hub tray (OpenClaw.Tray.WinUI.exe) crashes repeatedly with access violation in Microsoft.UI.Reactor.Core during UI mount #1173 describes Reactor mounting access violations, and Crash at startup on Windows 11 #1707 reports a stowed XAML exception. Merged fix: open the Hub when private desktop shell services are unavailable #1783 (fix: open the Hub when private desktop shell services are unavailable) handles unavailable optional shell services; no shared root cause is established.

   How this review workflow works

   • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
   • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
   • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
   • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
   • Maintainers can also comment @clawsweeper review to request a fresh review only.
   • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge; those execution lanes are retired.
   • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

   Reviewed October 26, 2026, 12:37 PM ET / 16:37 UTC.
4. phamvanminh991 commented on Oct 12, 2026

   

   phamvanminh991

   on Oct 12, 2026

   Author

   More actions

   Thank you for reviewing this issue.

   I am a non-technical Windows user. I have already reinstalled OpenClaw Companion and installed .NET Desktop Runtime 10.0.12, but the application still crashes on startup with error 0x80131506.

   Could you please provide step-by-step instructions for collecting the required diagnostic logs, or suggest a simpler diagnostic method?

   I can provide additional information and screenshots if needed.
5. clawsweeper

   added

   clawsweeper:intake:supportPreliminary submission classification; full source review pending.Preliminary submission classification; full source review pending.

   and removed

   clawsweeper:intake:supportPreliminary submission classification; full source review pending.Preliminary submission classification; full source review pending.

   on Oct 26, 2026
6. github-actions commented on Nov 10, 2026

   

   github-actionsBot

   on Nov 10, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue has been automatically marked as stale due to inactivity.
   Please add updated OpenClaw Windows details or it will be closed.
7. github-actions

   added

   stale

   on Nov 10, 2026
8. roboclaw-bot commented on Nov 10, 2026

   

   roboclaw-bot

   on Nov 10, 2026

   Contributor

   More actions

   @phamvanminh991 This is still unresolved, and reinstalling the system .NET runtime is not a confirmed fix for the self-contained Companion package. You already supplied the CoreCLR version and exception code. For the next useful detail: reproduce one launch, open Start > Event Viewer > Windows Logs > Application, and look for an Application Error entry at the same time as the .NET Runtime entry. Please report whether that adjacent entry exists and its fault offset, omitting computer/user names and personal path prefixes. A maintainer can then arrange private native-stack collection if needed. Do not post a full crash dump publicly.
9. github-actions

   removed

   stale

   on Nov 11, 2026