88 comments

[ 4.7 ms ] story [ 87.9 ms ] thread
Why in the name of all that's holy would you use a Microsoft product on a mission like this? Just about the only thing you can trust about MS is that their software is buggy.
From the comments:

‪Andy Meyers‬ ‪@andymeyers10.bsky.social‬ · 3h I said “launch window”, not “Launch Windows”!

There was a literal meme in spaceforce about this. Have we learnt nothing ?

Microslop will now troll people outside of the Earth, a great achievement for them.

So does this mean they now also have... 2 Copilots... ? Terrible joke.

We migrated earlier this year and had a similar problem. Outlook (classic) works differently than the OWA version. They keep the classic version so people don't spontaneously throw a chair out a window. It's being phased out slowly.
I want to say something like "oh well, this is certainly a non-critical piece of software". Hopefully it's the convenient dashboard and there are other, more hardened consoles for fallback or something.

But in all seriousness, and without glibness or sarcasm: I cannot comprehend how there is any "unexpected" software running on that spacecraft, regardless of operating system.

EDIT*** For those who like me only watched the video and didn't read the thread: This is on a laptop that is non-critical, it is not a part of the spacecraft. Whew. Now I'm sad that one of the Linux distros didn't try to pitch themselves to the astronauts for a sponsorship... Would have been especially on brand for Pop_OS.

Oh ya I remember how some computer pulled a windows update over a satellite connection during a research flight (aircraft). That was super expensive, wow. Now Microsoft servers are banned at the outgoing point since you couldn’t reliably stop it the computer itself and new teams with new computers come in.
computer virus

noun

    A program which can covertly transmit itself between computers via networks (especially the Internet) or removable storage such as CDs, USB drives, floppy disks, etc., often causing damage to systems and data.

    A software program capable of reproducing itself and usually capable of causing great harm to files or other programs on the same computer.
The astronaut's quote needs to be a billboard ad.. "I also see I have 2 instances of Outlook, and neither of those are working".
Bashing on MS products and on ReactJS (apparently used by spacex UIs) is a common pastime here and I'm guilty of it myself.

But here we're talking about actual space rockets flying to space with humans in them.

My expectation would be that something like https://tigerstyle.dev/ would be followed or the NASA rules linked from there https://spinroot.com/gerard/pdf/P10.pdf

The poor technicians having to RDP with (what I imagine must be) a horrible latency. Although still might be better than some corporate environments lol
They do not have to RDP. Powershell remoting or SSH are way faster way to examine the system.
I didn't expect they are running Windows up there. Shouldn't be specialized and curated ... smthing else?
Is this actually true? What's next? A BSOD? I would have ever ever in my life bet that Microsoft software could be shipped in a spacecraft carrying human beings. Unbeliveable.
Everyone likes to point and laugh, sure, I'm getting a chuckle as well.

However, on more practical level, what are other options? Outlook, the desktop application works really well with local copies, is pretty low bandwidth and very familiar to end users.

IMAP with Thunderbird is probably only other option that would satisfy the requirements.

EDIT: Yes they need to get email in space. It's easy way to send documents back and forth.

Neither outlook nor thunderbird. Best option would be some web browser based email + local web server (on board)
A modern browser is much more complicated and heavier than the old Outlook, and probably the latest Outlook too.
> Outlook, the desktop application works really well with local copies

With local cache for an Exchange server, or with purely local mail (i.e., using .pst files). The latter is mediocre IME. Outlook is an Exchange client; other uses are not in its wheelhouse.

I'd have just set up a backup mail client if someone insisted on Outlook. These sorts of issues are very common, and having a backup is the textbook solution if something might go wrong.
Email is a pretty good way to send short text messages, but it's not great at sending files. The basic protocols are pretty simple and we've got a lot of experience using them. I can see the appeal of email.

There's no way that outlook is the best tool for the job though, and it's no surprise at all that they're having problems with it. It's a complete mess with insane amounts of overhead and bloat if all you want to do is send text. Even the message headers it sends/mangles are trash. It's a pain to work with on the end user side too. I can't imagine that they couldn't have written a basic email client that would do the job better with far fewer problems/resources or used/built off of any number of decades old open source projects.

mu4e in Emacs works well, or Notmuch, or even Gnus with a local Maildir. Or Mutt if you're more into that. None of these applications can be that much harder than flying the capsule can they?
What are they emailing? I'd guess that all of the telemetry data, visual data,etc is getting sent to mission control via radio link. What's the outlook email even for?
It's so HR can remind them to complete their yearly NASA ethics trainings on time.
I hope they don’t need to search an email. Outlook may be familiar but it’s a familiar pain.
> and very familiar to end users.

How is this a factor for the very few users going you use it? (besides, for the primitive needs familiarity is of questionable use to begin with, almost any gui email client would do)

Why on God's green earth is Windows running on the Artemis spaceship?
British nuclear subs were running Windows XP until at least 2017. It's easy to google, but the best article about it is No, Trident doesn't run on windows XP (https://ukdefencejournal.org.uk/no-trident-doesnt-run-window...), which ironically makes it very clear that Trident subs were running on Windows XP and had no plans to replace it.

Most UK government excuse: "The programme undertaken by the Royal Navy and BAE Systems to equip the fleet with a Windows-based command system was completed in just 18 days."

Translated: "You couldn't do better in 18 days, so you don't have a right to worry or criticize. Also, don't ask why this was pushed off until the last 18 days of the project."

I don't understand the title.

It doesn't seem like they are trying to figure out why two copies of outlook are installed, they're trying to figure out why neither is giving them access to their email.

Did they consider scrapping the humans, and just installing co-pilot? heh .. heh.. /s
This talk about off-the-shelf hardware in space makes me wonder, given the clear line of sight, if it would be possible to detect their Wi-Fi access points' beacons from Earth. I'm not a "radio guy" and don't know if this would be impossible, simply on the basis of physics, due to the presumably low radiated power from the APs and the limitations of the size of typical antennas on the ground. (Obviously it's possible with the right equipment. We can communicate with the Voyager probes, but that's not with a "can-tenna" and an off-the-shelf Wi-Fi card...)

Edit: Anybody know how difficult it would be to keep an antenna pointed at them? I have no intuition for how fast their transit would be. I assume, since an orbit is around 90 minutes, pretty damned fast.

Edit 2: Some search-engining and back-of-the-envelope not-very-good-at-trig math says the longest possible transit would be about 5 minutes, moving though about 40 degrees of arc / minute. I'm probably completely talking out my ass, though.

It feels like it would be do-able to keep a directional antenna trained on a target moving at that speed.

As long as the orbit isn't changing, pointing the antenna is not hard and can be done by hand. I've done it with a handheld yagi antenna and the ISS, which has a 90-minute orbit (and an amateur radio repeater). I used a computer program to find the next overhead transit, paying attention to start & end times and start & end azimuth. Then used a watch to know where to point the antenna during the transit: at the horizon at the start, overhead halfway through the transit, at the opposite horizon at the end. Transits were 5-10 minutes so there's plenty of time to move the antenna.
WiFi, no, but if you've got a ham radio license, then you can reach them.
Maybe for emails and calendars, wouldn't want them to arrive and miss the appointment.
Well, I wasn't that worried for the astronauts before, but now that I know they're running windows, I'm not so sure.
Please imagine the luxury of being SO FAR AWAY from all the crap happening on our planet right now, only to be spoiled by some lousy marketing emails from Microslop hawking their latest Copilot incursion.
Someone, somewhere has an unwatched phone waiting for an authorisation code response...
Running Windows in outer space takes some pretty big balls. Gives me a cold sweat just thinking about it.