Closed zaqes closed 1 year ago
Hi @zaqes, It looks like you are upgrading from an old FLARE-VM installation, and therefore the windows environment variables are not set properly. There are two options here:
%TOOL_LIST_DIR%
= %ProgramData%\\Microsoft\\Windows\\Start Menu\\Programs\\FLARE
%TOOL_LIST_SHORTCUT%
= %UserProfile%\\Desktop\\FLARE.lnk
Please give those options a shot and let me know if you still have issues. htnhan
Actually I got this FLARE-VM via a FireEye course I attended. Do you mean that I will miss updates for some packages if I don't reinstall it?
Hi @zaqes ,
Yes, unfortunately, you will not be able to get the latest updates unless you reinstall it.
FLARE-VM do not fully support update since we can't control the specific version of libraries and applications using cup
. It is recommended that you perform a complete new install with the latest install.ps1
script on a fresh VM to get the latest tools/versions of the tools.
That being said, Fakenet-NG is quite stable. The project is in maintenance mode right now, so there is likely no major updates other than any major bug fix
Ok, thanks.
I have those environment variables and the update still doesn't work.
vcpython27
is required for fakenet-ng.python.fireeye
to install properly. Unfortunately Microsoft pulled the original installer so the vcpython27
Chocolatey package fails to download the installer, which causes fakenet-ng.python.fireeye
to fail as well.
archive.org has an archived copy of the original installer at https://web.archive.org/web/20210106040222/download.microsoft.com/download/7/9/6/796EF2E4-801B-4FC4-AB28-B59FBF6D907B/VCForPython27.msi. I'd recommend downloading and installing that, then trying another choco install fakenet-ng.python.fireeye
run.
Thank you for your feedback! We've been working on major updates to FLARE VM over the last year. The now revamped FLARE VM has just been released and will make the project more open and maintainable. Please check out our blog post at https://www.mandiant.com/resources/blog/flarevm-open-to-public and give the new installation a try.
If this problem still persists with the new installation, please report:
Please note that we use this message to close all legacy issues in this repository. We look forward to your feedback and support for the next generation of FLARE VM.