Daniel Silverstone

What's odd is that there's no red in the rustup output at that point. So I wonder what we've done to the terminal that is causing that.

What error is it showing at that point? can you attach a screenshot?

Oh interesting, I wonder if the control+C managed to give it some input before it killed it.

That is extremely odd.

I guess possibly. I'm not entirely sure how the input loop behaves on Windows.

the src/ tree *is* rustup and rustup-init - it's all open source. the code in question will be in src/cli/self_update.rs most likely

I'm not able to reproduce this, which is also odd. Are you able to investigate at all @Vbbab ?

If you can reliably reproduce this then we stand a chance of diagnosing it, yes please @chansuke

I don't think we're going to get to a stable-compatible solution to this problem in the 1.24.0 cycle so I'm going to defer this particular piece of work for 1.25.0...