Artemis computer running two instances of MS outlook; they can't figure out why

Original Article ↗ Hacker News Discussion ↗

Scope of the Problem

  • The Outlook issue is on a non‑critical “personal computing device” (PCD), a Surface Pro laptop used for email, office apps, and media, not for guidance or life‑critical control.
  • Mission Control remotely accessed the laptop, fixed the issue, and took it offline afterward; this is treated like normal IT troubleshooting, just with high latency.

Why Windows/Outlook in Space

  • NASA has long used off‑the‑shelf laptops (e.g., ThinkPads on Shuttle/ISS) that go through their own “space hardening” process.
  • Drivers cited in the thread: astronauts and staff already know Windows/Office; NASA/DoD culture is deeply Microsoft‑centric; training, procedures, and documentation are built around MS tools; changing platforms is bureaucratically hard.
  • Some see this as de facto “corporate welfare” and organizational inertia (“nobody gets fired for choosing Microsoft”).

Critiques of Outlook and Windows

  • Many express disbelief that Windows and Outlook are in a spacecraft at all, even on non‑critical systems, citing MS’s perceived bugginess, update behavior, telemetry, and multiple confusing Outlook versions (classic, “new”, Windows 11 app).
  • Specific Outlook complaints: bloat, resource usage, search regressions, multiple instances, and Exchange complexity.
  • Concern that unsealed, auto‑updating OSes could waste expensive bandwidth, generate unpredictable traffic, or behave contrary to documented settings (e.g., metered connections).

Alternatives and Trade‑offs

  • Proposed alternatives: Linux + Thunderbird/Claws, text clients (mutt, Alpine), local webmail, simple custom MUAs, or maildir‑based setups; arguments that smaller, minimalist clients would be more reliable and resource‑efficient.
  • Counterarguments: bespoke or niche solutions are costly to develop, certify, and train on; COTS email + Exchange is familiar, low‑bandwidth with local cache, and “good enough” for non‑mission tasks.

Safety, Reliability, and Architecture

  • Several stress that real flight software follows strict safety‑critical rules (e.g., NASA “Power of Ten” style guidelines) and runs on separate systems; laptops are treated like office gear.
  • Others argue that even non‑critical onboard systems should be tightly controlled (no live updates, minimal unknown code) because link capacity and predictability are part of “real” space engineering.

Broader Themes and Humor

  • Thread mixes serious concern with humor about Clippy/Copilot in space, “enshittification” reaching orbit, and modern spaceflight needing remote Outlook support alongside React dashboards.