Closed nadrojisk closed 7 months ago
Hi @nadrojisk! Thank you for submitting this issue.
I see that it looks like the script is attempting to connect to an older myget
repo that is no longer being used (https://www.myget.org/F/fireeye/api/v2
) and I wonder if that may be the root of most of these issues.
Would you be able to try and remove that source via chocolatey? It should be something like:
choco source list
- to see the names of the sourceschoco source remove -n=<source name that contains old repo here>
The current myget that is being used is: https://www.myget.org/F/vm-packages/api/v2
https://github.com/mandiant/flare-vm/blob/main/install.ps1#L380
Once that source has been removed, see if you can try the script again, but I will be honest, the best way to update is to usually perform a full fresh FLARE-VM install. There has been quite a bit of changes in the last ~1.5-2 years.
Also note, we are aware of some packages that are currently failing to install, though it shouldn't be as many as you are having. You can see the list of ones with current issues here: https://github.com/mandiant/VM-Packages/wiki/Daily-Failures A current list from today shows:
Thanks for the suggestion @emtuls. I attempted to remove the source and add the new one. However all the old packages are suffixed under .flare
which isn't the case anymore. I'll do a fresh install.
Do you know if moving forward flare will be more "stable" with trying to update the packages and install new ones added? It's nice to be able to just upgrade the VM especially since usually I'll add in plugins and what not.
Hmmm. I wonder if removing those names from your choco cache might alleviate that. At the very least, while it may say failure, if you're using the new script and source, you should have the latest versions them still in the -mostly- same places. The only differences I can think of would likely be if there was a category change.
We definitely try to not change package names (and categories) as much as possible! Though it may happy from time to time. The biggest difference I believe that happened since that time frame may have been the open sourcing of our packages, which had a lot of changes. 😬
I'm sorry for the issues it caused! Thank you for letting us know. 🙂
No worries! I ended up doing a fresh install. Thanks for your help though! :)
What's the problem?
I recently upgraded my existing flare install with the newest version. Most of the tools installed fine however, there were a good handful that did not install. I tried to manually install them with choco post install but I got a ton of errors.
Additionally, I am unsure if the duplicated package names are normal in the log.txt. I wonder if its because I am installing ontop of an existing Flare install?
failed_packages.txt log.txt
Steps to Reproduce
Environment
VMware Workstation
Additional Information
No response