Copied from bug 1727878:
A profile path initially looks like:
C:\Users\agash\AppData\Roaming\Mozilla\Profiles\usjl8hcn.default-beta
If that's only a virtual path, and the profile is actually in a package's private location, this resolves to a final form like:
C:\Users\agash\AppData\Local\Packages\Mozilla.Firefox.Beta_gmpnhwe7bv608\LocalCache\Roaming\Mozilla\Firefox\Profiles\usjl8hcn.default-beta
<snip>
[1] Note that this doesn't happen if the package creates its profile after an unpackaged Firefox had already run. If the top level AppData\Roaming\Mozilla path already existed on the real filesystem, then that will be used instead of the package's private location, so the final path would be the same (up to shortnames).
In other words, if there is only a single MSIX installation and no other Firefox install from Mozilla, then the "real" profile folder would be in the \AppData\Local\Packages\... location, as reported in the support forum post ("C:\Users\xxx\AppData\Local\Packages\Mozilla.Firefox_n80bbvh6b1yt2\LocalCache\Roaming\Mozilla\Firefox")
That being so, I would think that the user would still be able to use "about:support" to open the profile folder. However, the user reported what looks like a bug: (quote)
Hi I put "about:support" in the URL field. The pressed "Open folder" button on the profile folder section on the troubleshooting page, then I got an error: "Location is not available." I looked for the folder, but I could not. "about:support" describes the location "C:\Users\xxx\AppData\Roaming\Mozilla\Firefox\Profiles\forv3n79.default-release but the Roamig folder does not contain "Mozzilla" folder and the subdirectories."
Copied from [https://bugzilla.mozilla.org/show_bug.cgi?id=1727878 bug 1727878]:
----
A profile path initially looks like:
C:\Users\agash\AppData\Roaming\Mozilla\Profiles\usjl8hcn.default-beta
If that's only a virtual path, and the profile is actually in a package's private location, this resolves to a final form like:
C:\Users\agash\AppData\Local\Packages\Mozilla.Firefox.Beta_gmpnhwe7bv608\LocalCache\Roaming\Mozilla\Firefox\Profiles\usjl8hcn.default-beta
<snip>
[1] Note that this doesn't happen if the package creates its profile after an unpackaged Firefox had already run. If the top level AppData\Roaming\Mozilla path already existed on the real filesystem, then that will be used instead of the package's private location, so the final path would be the same (up to shortnames).
----
In other words, if there is only a single MSIX installation and no other Firefox install from Mozilla, then the "real" profile folder would be in the \AppData\Local\Packages\... location, as reported in the support forum post ("C:\Users\xxx\AppData\Local\Packages\Mozilla.Firefox_n80bbvh6b1yt2\LocalCache\Roaming\Mozilla\Firefox")
That being so, I would think that the user would still be able to use "about:support" to open the profile folder. However, the user reported what looks like a bug: (quote)
''Hi I put "about:support" in the URL field. The pressed "Open folder" button on the profile folder section on the troubleshooting page, then I got an error: "Location is not available." I looked for the folder, but I could not. "about:support" describes the location "C:\Users\xxx\AppData\Roaming\Mozilla\Firefox\Profiles\forv3n79.default-release but the Roamig folder does not contain "Mozzilla" folder and the subdirectories."
