Closed init5-SF closed 1 year ago
@init5-SF Currently many packages are broken as our team is limited; however, we have plans in the works to help alleviate this. We're aiming for Q1 to release our updates, apologies until then. 🙇
@init5-SF Currently many packages are broken as our team is limited; however, we have plans in the works to help alleviate this. We're aiming for Q1 to release our updates, apologies until then. 🙇
@MalwareMechanic thanks for the fast response! Can I run in the current install script then run the new one in Q1 to fix the missing/broken packages, or the new script will require a fresh install?
@init5-SF The updated script will likely require a fresh install unfortunately
I got a fresh install using the Windows Edge VMs completed today Nov 30, 2021. NOTE the build below 17763 which is 1809. Your issue might be building with 21H2. Recommend you re-try with the older version of Windows 10. Most enterprises will use a licensed Windows version so I recommend you try your license with the old one as that's what I intend to do. Good luck. It also takes a while (5-8 hours) to complete. Some interection may be necessary if it seems like it's stuck on a line.(CTRL + Z)
OS Name Microsoft Windows 10 Enterprise Evaluation Version 10.0.17763 Build 17763 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name MSEDGEWIN10 System Manufacturer VMware, Inc. System Model VMware Virtual Platform System Type x64-based PC
@TheSerialLearner thanks, will try that, I also took a closer look at the log file and it has a lot of 404's, some packages were not found during installation.
Many packages have URLs that are 404'ing or returning content that doesn't match the hard-coded hash (which may be because the URL is dead/old, content is indeed updated, or defender has blocked it). In all cases the package will fail to install. So while your (@TheSerialLearner) install may have completed (it should), you're likely missing lots of packages sadly 😭 We have a solution in mind, but are awaiting some internal roadblocks before we can continue. So fingers-crossed for Q1!
@init5-SF if you tried to set this up at work (behind firewalls/ips) then that may introduce an issue there. You might need less restriction for this.
Thanks @MalwareMechanic. Correct that I was missing a few packages like Burp which I installed manually. Visually observing the csv file I think I got about 60% of the files. Some files were not found, some failes checksum etc
Hey @MalwareMechanic - long time no hear in this topic, I as well encountered many hash mismatch and 404 issues that hopefully would be fixed by your Q1 fixes. Could you give any update? Do you still plan to make an update in Q1 or should we expect it to be postponed? Thanks.
Hey @MalwareMechanic - long time no hear in this topic, I as well encountered many hash mismatch and 404 issues that hopefully would be fixed by your Q1 fixes. Could you give any update? Do you still plan to make an update in Q1 or should we expect it to be postponed? Thanks.
I'd also like to know what the future plans are for this. So leaving this here @MalwareMechanic .
Has there been any progress on this? Really hope it's not being left in the dust...
Has there been any progress on this? Really hope it's not being left in the dust...
Hey @JohnBeres ,I was able to install it on a windows machine. So I imaged it and uploaded it onto vagrant for easier provisioning. Because the installation itself takes a really long time too. You can check out the project here https://github.com/brootware/flarevm-up
Has there been any progress on this? Really hope it's not being left in the dust...
Hey @JohnBeres ,I was able to install it on a windows machine. So I imaged it and uploaded it onto vagrant for easier provisioning. Because the installation itself takes a really long time too. You can check out the project here https://github.com/brootware/flarevm-up
Hello @brootware Thank you for the reply. Unfortunately a pre-built image is not appropriate for our environment. I'm much more interested in how to get around these errors so our build can succeed.
Happy to hear what your solution was to build your virtual box for Vagrant!
Update: He has spoken!
https://twitter.com/MalwareMechanic/status/1562952356576104448?s=20&t=LaqNQnBHyantLSea-eILTA
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.
Very disappointing experience. I am getting this on a fully updated fresh install of Windows 10 Pro 21H2