search

rapid7 / metasploit-omnibus

Packaging metasploit-framework with omnibus
248 stars 205 forks source link

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

Open yb123speed opened 3 years ago

yb123speed commented 3 years ago

Such as the title。

cannujBarfu0negjiz commented 3 years ago

Como el título。

Como el título。

AlexHimself commented 1 year ago

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 commented 1 year ago

@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 commented 1 year ago

Potentially related to https://github.com/rapid7/metasploit-omnibus/issues/115

ant0n-0x0000 commented 3 months ago

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