# 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:** 1\
**Showing post:** 3

<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…

---

_[View the full topic](https://discourse.julialang.org/t/juliapro-v1-5-3-1-and-julia-v-1-5-4-quarantined-by-cisco-amp-as-ransomware/57233)._