Skip to content
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

I configured the installation path to be "C:\", why is it actually installed to "D:\metasploits-framework" #144

Open
yb123speed opened this issue Dec 2, 2020 · 5 comments

Comments

@yb123speed
Copy link

Such as the title。

@adfoster-r7 adfoster-r7 transferred this issue from rapid7/metasploit-framework Dec 2, 2020
@cannujBarfu0negjiz
Copy link

Como el título。

Como el título。

@AlexHimself
Copy link

I have the same issue except here is more detailed information to help.

Steps to reproduce

How'd you do it?

  1. Use a fully updated Windows 10 computer that has both a C: (primary) drive and a D: (secondary, storage) drive, and uses Windows Defender for AntiVirus.
  2. Make NO changes to Windows Defender and attempt to install with defaults, confirming C:\ drive is default.
  3. Various Defender security errors appear. Add exception for C:\metasploit-framework.
  4. Uninstall/reinstall, confirming C:\ drive is specified location.
  5. More defender errors. Verify no contents in C:\metasploit-framework. Inspect D:\ drive and see file/folders were created there, despite location being specified as C:\ drive.

Alternatively:

  1. Use a fully updated Windows 10 computer that has both a C: (primary) drive and a D: (secondary, storage) drive, and uses Windows Defender for AntiVirus.
  2. Install using defaults, confirming C:\ drive is selected
  3. Files are installed to D:\ drive.

image

image

Expected behavior

Metasploit should install in specified location, not D:\ drive randomly.

Current behavior

Metasploit installs in wrong location.

Metasploit version

Framework: 6.2.37-dev-8368accd5592392a6d8449490f222f4b269e3a3c
Console : 6.2.37-dev-8368accd5592392a6d8449490f222f4b269e3a3c

@gwillcox-r7
Copy link

@AlexHimself Thanks for submitting a more detailed overview, we'll take a look into this and let you know if we are able to replicate this.

@Reelix
Copy link

Reelix commented Feb 16, 2023

Potentially related to #115

@ant0n-0x0000
Copy link

Having the same issue now myself with 6.4.19-20240718103548-1rapid7-1-x64.msi. Used this workaround which seems to of fixed it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants