Installing an old version is a mistake.
I wasn't able to reproduce this false positive detection after installing all updates.
If the installer is blocked then you can right click on the executable file and choose Unblock.
Thank you, Erel, for your response and clarification.
I understand your position regarding the risks of installing older versions, and I agree that reverting should not be the first solution. However, in my case—and apparently in Adrian’s as well—the latest installer was completely blocked by Windows Defender, and the IDE failed to launch even after forcing the installation.
I suspect the reason this issue only affects a few users is due to the staggered nature of Windows Defender database updates. Not all systems receive the same definitions at the same time, which might explain why some installations succeed while others are flagged.
To better understand the situation, I ran the installer through several independent scanners. While VirusTotal shows no detections, Hybrid Analysis flagged it as
Backdoor.Agent.mytozz.lgzu, and ScanWith reports that McAfee identified it as
Malware.TR/AD.RiskWareTool.a. These results are not conclusive, but they do suggest that certain engines are reacting to something in the executable.
I’m sharing this not to challenge the integrity of the software, but to help clarify why some users might be experiencing unexpected blocks.
Thanks again for your continued support and development.