Metasploit installs to incorrect Hard Drive

[Reelix]

Steps to reproduce

How'd you do it?

1. Download https://windows.metasploit.com/metasploitframework-latest.msi
2. Attempt to install Metasploit to R:\Utilities\

Were you following a specific guide/tutorial or reading documentation?

No

Expected behavior

Metasploit gets installed under R:\Utilities\

Current behavior

Metasploit gets installed in the root directory of M:\

System stuff

Metasploit version

Framework: 6.0.4-dev-760aba0ace4cd3ce88c65af154fb70df57d09ea1
Console : 6.0.4-dev-760aba0ace4cd3ce88c65af154fb70df57d09ea1

I installed Metasploit with:

• Kali package via apt
• Omnibus installer (nightly)
• Commercial/Community installer (from http://www.rapid7.com/products/metasploit/download.jsp)
• Source install (please specify ruby version)

OS

Windows 10

Additional Information

I have 4 Hard Drives: C:\ - Local Disk, G:\ - 'Reelix - Games', M:\ - 'Reelix - Media' and R:\ - 'Reelix - Misc' (That contains a Utilities folder at R:\Utilities\

This issue has persisted in an identical fashion between attempted reinstallations making sure that the correct location was chosen during installation.

[GetRektBoy724]

it was hard tho to know the problem from an omnibus installer....
if you keep getting this problem...
try to install a kali vm

[franferrax]

Hi, I think this should be reported in the metasploit-omnibus repository. Even more, it seems to be actually reported in rapid7/metasploit-omnibus#115.

[github-actions]

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]

Hi again!

It’s been 60 days since anything happened on this issue, so we are going to close it.
Please keep in mind that I’m only a robot, so if I’ve closed this issue in error please feel free to reopen this issue or create a new one if you need anything else.

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

[David-OConnor]

Same! Please re-open. Not fixed.

[Muriel-Gasparini]

Same here.