-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows installer installs to different path than specified even starting from escalated cmd prompt. #115
Comments
(didn't actually work, see end) had a similar issue, but it tried using Z:, a network drive, to store some 700MB of temp files... what ended up working for me is i unmounted Z:, put the installer on D: (the only other drive i had mounted), and did some observations:
EDIT alright, looks like i was a bit quick to celebrate. the first command finished without errors, but it doesn't look like it installed anything -- it just created a second metasploitframework-latest.msi, (~1MB) and metasploit-framework.zip (~750MB) in C:/ ... i'm confused |
This looks to be related to how |
Also in environment variable in Win 10, it is actually adding the following system Path:
Although even after selecting |
On windows 10 v10.0.18362.657 I am running the installer and at first I thought it was just not working. I did have antivirus off and I found #96, #102 and the workaround that says to use an escalated cmd prompt to execute the installation. The issue is it still won't install to C: even if I manually specify C: or a folder on C: and start the MSI from an escalated cmd prompt it is placing the zip on F: then creating the metasploit-framework folder there. Ejected my F: drive now it does it on B: can recreate this issue consistently over and over.
The text was updated successfully, but these errors were encountered: