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

Running msfupdate on Windows moves Metasploit onto your OS drive #9578

Closed
Reelix opened this issue Feb 18, 2018 · 6 comments
Closed

Running msfupdate on Windows moves Metasploit onto your OS drive #9578

Reelix opened this issue Feb 18, 2018 · 6 comments
Labels
bug Stale Marks an issue as stale, to be closed if no action is taken

Comments

@Reelix
Copy link
Contributor

Reelix commented Feb 18, 2018

Steps to reproduce

How'd you do it?
1.) Acquire a secondary Hard Drive
2.) Install metasploit in a subdirectory on that drive - Eg: R:\Utilities\metasploit-framework
3.) Wait for an update
4.) Run msfupdate.bat

Expected behavior

Metasploit updates, and remains in the location it was installed

Current behavior

Metasploit gets moved to C:\metasploit-framework\

I installed Metasploit with:

https://windows.metasploit.com/metasploitframework-latest.msi

OS

Windows 10 Pro x64

@ibonobo
Copy link

ibonobo commented Jun 26, 2018

same here

@busterb busterb added the bug label Jul 2, 2018
@franferrax
Copy link

Hi, I think this should be reported in the metasploit-omnibus repository. I think this issue shares the root cause with #14071, likely to be reported in rapid7/metasploit-omnibus#115.

@github-actions
Copy link

github-actions bot commented Dec 3, 2020

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

@github-actions github-actions bot added the Stale Marks an issue as stale, to be closed if no action is taken label Dec 3, 2020
@ibonobo
Copy link

ibonobo commented Dec 3, 2020 via email

@github-actions github-actions bot removed the Stale Marks an issue as stale, to be closed if no action is taken label Dec 4, 2020
@github-actions
Copy link

github-actions bot commented Jan 5, 2021

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

@github-actions github-actions bot added the Stale Marks an issue as stale, to be closed if no action is taken label Jan 5, 2021
@dwelch-r7
Copy link
Contributor

This issue is bring tracked here rapid7/metasploit-omnibus#115

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Stale Marks an issue as stale, to be closed if no action is taken
Projects
None yet
Development

No branches or pull requests

5 participants