WSL: Granted reads Edge Local State from Linux path instead of Windows path, breaking profile detection #938
Unanswered
RajasGujarathi
asked this question in
Issue Triage
Replies: 1 comment
|
@shwethaumashanker Is this something that you can help with ? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Issue Description
When running
assume -cfrom WSL with Edge as the default browser, Granted looks for Edge'sLocal Statefile at the Linux path (~/.config/microsoft-edge/Local State) instead of the Windows path (/mnt/c/Users/<user>/AppData/Local/Microsoft/Edge/User Data/Local State).Since that file doesn't exist on the Linux side, Granted can't discover existing browser profiles. It still launches Edge on the Windows side with the correct
--profile-directory=Workflag, but because it couldn't readLocal State, it appears to fall back to creating a new profile rather than reusing the existing one. Since my Edge installation is org-managed (Edge for Business), profile creation is locked via Group Policy — so this fails.In short: Granted resolves the Edge binary path correctly for WSL (Windows side) but resolves the profile config path incorrectly (Linux side).
Expected Behavior
When running under WSL, Granted should resolve the Edge
Local Statefile from the Windows user data path, not the Linux config path.Actual Behavior
Granted reads from
~/.config/microsoft-edge/Local State(doesn't exist), fails silently, and falls back to creating a new profile — which fails under org-managed Edge.Reproduction Steps
granted browser set→ select Edgeassume my-profile -c --browser-profile "Work"Local Statefrom the Linux path, can't detect existing profilesGranted Logs
Granted Version
OS Version Information
WSL (Linux) → opening Edge on Windows host
Minimal Granted & AWS Config Configuration
Additional Relevant Configuration
No response
I acknowledge that:
```) on separate lines.All reactions