[pnako]

>Microsoft Windows 10 sends all new unique binaries for further analysis to Microsoft by default.

Wait, what? Let's say you write code that you compile using MSVC or MinGW or whatever to an .exe file.

Surely there is no way this gets automatically sent to MS?

[unionpivo]

That is exactly what happens. And it happens with any new executable. I noticed it when i was trying out how well rust works on windows.

[ufmace]

Seems bizarre. If I build 30 .NET binaries a day while building and testing a new feature, I guess all 30 get uploaded to MS and tested. And the same for all of the other developers doing the same sort of thing around the world. I wonder how often their test cluster goes down in flames while some C++ developer somewhere is trying to fix a memory access bug.

[fortran77]

I couldn't even get Rust to install on Windows!

[unionpivo]

rustup is your friend. install that, and then rust with rustup.

Edit: forgot link: https://rustup.rs/

[steveklabnik]

What did you run into? Did you file a bug? That’d be helpful! I use Rust on Windows every day, though that means I’m not often re-installing it...

[vortico]

Yes, you can test this yourself. Compile a 50MB binary and watch your bandwidth for a bit after attempting to run it.

I believe MacOS 10.15 also does this because there's a massive delay the first time I run a binary compiled with clang.