The year is 2024, and humanity has finally returned to the vicinity of the Moon. We have harnessed the power of the Space Launch System, a multi-billion dollar marvel of engineering designed to propel four brave souls into the cosmic void. And yet, the greatest threat to the Artemis II mission wasn’t a solar flare, a micro-meteorite, or a fuel leak. It was the “Processing” wheel of death on Microsoft Outlook.

NASA commander Reid Wiseman recently reported that his Microsoft Surface Pro was running two instances of Outlook, neither of which functioned. While the flight director, Judd Frieling, assured the public that this is “not uncommon,” we should all be collectively terrified that a lunar mission is being managed with the same software stability as a mid-tier accounting firm in Scranton.

**The “Relatability” Trap**
The article suggests this tech issue is something “some of us back on Earth can relate to.” Here is a radical thought: we shouldn’t be able to relate to astronauts. The moment a lunar commander has to deal with the same “Account Error” pop-up that ruins my Tuesday morning, the magic of space travel dies a little. We want our astronauts using glowing green terminal lines and complex telemetry, not staring at a “Not Responding” window while their emails to Mission Control sit in the Outbox. If I’m hurtling toward the lunar far side at 25,000 miles per hour, the last thing I want is for my primary communication tool to be an app that struggles to sync a calendar invite.

**The Choice of Hardware: The Surface Pro**
NASA chose the Microsoft Surface Pro as the Personal Computing Device (PCD) for the crew. A tablet with a kickstand. In zero gravity. One can only assume the kickstand was a high-priority feature for a mission where the concept of “down” doesn’t exist. Using a consumer-grade tablet for a deep-space mission is like bringing a Segway to the Dakar Rally; sure, it’s “tech,” but maybe it’s not the right tool for the terrain.

**The “Two Outlooks” Mystery**
Wiseman reported seeing two Microsoft Outlooks. This is the ultimate Microsoft experience: the software is so invasive it begins to replicate via binary fission. Most of us struggle to get one instance of Outlook to display a signature correctly; Wiseman had to deal with a digital doppelgänger. The fact that *neither* worked is the most honest representation of the Microsoft ecosystem ever recorded in the history of the vacuum of space.

**Remote IT Support at 240,000 Miles**
The solution was for Mission Control to “remotely access” the device. Imagine the latency. We’ve all sat through an IT support session where a technician moves your mouse cursor with a three-second delay. Now, multiply that by the distance to the Moon. “Can you see my screen, Houston?” followed by a 2.5-second round-trip delay for the word “No.” It’s a miracle the fix didn’t involve the astronaut having to hold his Surface Pro out the window to get a better signal.

**The “Not Uncommon” Admission**
Flight director Judd Frieling’s claim that this is “not uncommon” is perhaps the most damning indictment of modern aerospace logistics. If your software glitches are “common” during a flight to the Moon, you haven’t built a space-faring OS; you’ve built an expensive frustration simulator. We are currently spending billions to put boots back on the lunar surface, yet we are apparently content with the mission’s productivity being held hostage by a bloated email client that hasn’t seen a meaningful stability update since the Windows XP era.

In the end, NASA fixed the glitch, and the mission continues. But let this be a lesson to future Mars explorers: if you’re planning on going to the Red Planet, maybe just use Webmail. Or better yet, send a postcard. It’s faster, more reliable, and it won’t ask you to “Restart to Apply Updates” while you’re mid-orbit.