rbtcollins
commented
4 years ago Hi, we've found in the past that while we have consistent problems with anti virus it is often not the thing that people think it is and we need to drill into the specifics of the failure to identify the exact cause.
Additionally different AV products interrupt IO in different ways at different times depending on configuration, policy and so forth and this can interact with rustup as well.
Can you please provide: the actual error you are experiencing - what rustup is outputting to the console.
What specific anti-virus you are encountering this with.
It may be helpful, though I can't say if it is needed yet, to also provide a trace of the IO that rustup is going - e.g. with sysinternals process monitor or windows event tracing), configured to trace both rustup, Defender, and whatever AV and anti-malware products present on your system. I find the easiest way to do this is to filter for all file operations within ~/.rustup from any process.
mdtro
Problem My corporate system has some strict antivirus policies. When running
rustup updateit will usually fail at theinfo: installing component 'rust-docs'part because of the mass renaming of files (I assume). The security policies profile this as ransomware and begin implementing defenses against it.Steps (this one might be hard to reproduce outside of my case)
rustup updatePossible Solution(s) My current solution is to:
rustup update.A more permanent solution might be to sign
rustupwith a valid certificate as most AV's will trust this and allow behavior that would typically be considered suspicious if the binary was not signed.Notes System OS = Windows 10
Output of
rustup --version: rustup 1.21.1 (7832b2ebe 2019-12-20) Output ofrustup show: