---
name: link-exit-0xc0000142-under-load-reads-as-a-toolchain-repair
description: todlando 2026-09-08 x2 — `linking with link.exe failed: exit code 0xc0000142` (STATUS_DLL_INIT_FAILED) on a shared box under build contention; presents as "Visual Studio build tools may need repairing"; it is a load symptom, not a toolchain defect
metadata:
  type: reference
---

Twice on 2026-09-08 (12:28Z cold build killed under contention; 15:28Z a `-p spt` test build beside a live golden twohost-a job) a Windows link step died with `exit code: 0xc0000142` — `STATUS_DLL_INIT_FAILED` — and cargo printed the repair-your-Visual-Studio-build-tools hint on top of it. Zero cells ran; the leg was VOID, not red.

**Why:** the hint is cargo's generic text for that status; on a shared runner box the status arises from process-startup pressure (desktop heap / DLL init under many concurrent link.exe and rustc), not from a broken toolchain. Reading the text at face value sends someone to repair the wrong thing.

**How to apply:** on `0xc0000142` from link.exe/cc, print the box-wide builder census beside it and classify the leg VOID-under-load; re-run alone before touching the toolchain. Related: [[a-path-predicate-builder-census-is-intermittently-blind]], [[windows-lock-contention-is-not-wouldblock]].