# JuliaPro v1.5.3-1 and Julia v.1.5.4 quarantined by Cisco AMP as ransomware

**URL:** <https://discourse.julialang.org/t/juliapro-v1-5-3-1-and-julia-v-1-5-4-quarantined-by-cisco-amp-as-ransomware/57233>\
**Category:** Tooling\
**Tags:** juliapro\
**Created:** [March 15, 2021, 8:36pm UTC](https://discourse.julialang.org/t/juliapro-v1-5-3-1-and-julia-v-1-5-4-quarantined-by-cisco-amp-as-ransomware/57233 "2021-03-15T20:36:30Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![elbert5770](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/elbert5770/32/18646_2.png) [@elbert5770](https://discourse.julialang.org/u/elbert5770)\
**Post date:** [March 15, 2021, 8:36pm UTC](https://discourse.julialang.org/t/juliapro-v1-5-3-1-and-julia-v-1-5-4-quarantined-by-cisco-amp-as-ransomware/57233/1 "2021-03-15T20:36:30Z")

</div>

Event Type: Threat Detected  
Computer:XXX  
Hostname: XXX  
IP: XXX  
Detection: W32.MAP.Ransomware.rewrite  
File: julia.exe  
File path: \?\C:\Users\XXX\AppData\Local\JuliaPro-1.5.3-1\Julia-1.5.3\bin\julia.exe  
Detection SHA-256: 8faf21bdf85d88a4560b103181f79fc533a379e5882145252ca9715b0c193134  
By Application: JuliaPro-1.5.3-1\_build-319.exe  
Severity: Medium  
Timestamp: 2021-03-15 17:04:52 +0000 UTC

The same thing happens when Julia v1.5.4 is installed and then called by Atom/Juno. While pre-compiling packages, Cisco AMP quarantines julia.exe.

We have reported this to Cisco. Hopefully they will fix this?

This will explain some odd behavior on managed computers, as julia.exe keeps disappearing.

JuliaPro 1.4.1-1 seems okay, but it is possible that a new install of this version would also get flagged.

---

<div class="post-metadata">

**Author:** ![MA\_Laforge](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ma_laforge/32/385_2.png) [@MA\_Laforge](https://discourse.julialang.org/u/MA_Laforge)\
**Post date:** [October 16, 2021, 2:20am UTC](https://discourse.julialang.org/t/juliapro-v1-5-3-1-and-julia-v-1-5-4-quarantined-by-cisco-amp-as-ransomware/57233/2 "2021-10-16T02:20:45Z")

</div>

I believe this issue might have just recently been addressed - but I am unsure if your copy of AMP has the most recent checks installed.

### Suggestion

Try it out Today to see if it works. If not: try again next week.

### More suggestions

Try out Julia v1.6.3 (non-pro) first. That one works for me.

---

<div class="post-metadata">

**Author:** ![MA\_Laforge](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ma_laforge/32/385_2.png) [@MA\_Laforge](https://discourse.julialang.org/u/MA_Laforge)\
**Post date:** [May 18, 2023, 3:37am UTC](https://discourse.julialang.org/t/juliapro-v1-5-3-1-and-julia-v-1-5-4-quarantined-by-cisco-amp-as-ransomware/57233/3 "2023-05-18T03:37:26Z")

</div>

FYI: I found an alternative solution that might just work if you are somewhat comfortable with Linux systems/command line.

(link below)

> [@Very strange problems installing on win10](https://discourse.julialang.org/t/very-strange-problems-installing-on-win10/77416/11):
>
> WSL: A possible Windows “solution”/workaround I recently tried installing Julia-for-Linux-on-Windows (using the Windows Subsystem for Linux). It worked! (Windows 11 / WSL:Debian / Julia 1.9.0 ) — and quite well, I must add: WSL integration is seamless within Windows (though the WSL installation itself is not) As an added benefit: WSL installations create a “.vhdx” virtual disk with an EXT4 partition (at least mine did at the time of writing). I would bet file operations have a real likelih…

---

<div class="post-metadata">

**Author:** ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)\
**Post date:** [September 12, 2023, 4:41pm UTC](https://discourse.julialang.org/t/juliapro-v1-5-3-1-and-julia-v-1-5-4-quarantined-by-cisco-amp-as-ransomware/57233/4 "2023-09-12T16:41:34Z")

</div>