Microsoft Edge Breaks if Favorites Folder Symlinked

Issue #3911763


Aug 5, 2015
This issue is public.
Reported by 0 people

Sign in to watch or report this issue.

Steps to reproduce


Repro Steps:

  1. open c:\user<username>\AppData\Local\packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\AC\MicrosoftEdge\User\Default\Favorites

  2. Copy Favorites folder to a new folder located off the root ex: c:\testing\Favorites

  3. now rename the default Favorites folder under c:\user<username>\AppData\Local\packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\AC\MicrosoftEdge\User\Default\Favorites to anything other than Favorites

  4. create the symbolic link from a command prompt
    Example: mklink /j “c:\user<username>\AppData\Local\packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\AC\MicrosoftEdge\User\Default\Favorites” “C:\testing\favorites”

If the symlink was successful you will see the following message
Junction created for c:\user<username>\Favorites <<==>> C:\testing\favorites

  1. Attempt to open Edge

Go to the hidden folder where Edge keeps its favorites.
Delete the Favorites folder
Create a Symlink named “Favorites” to your existing Favorites folder elsewhere (for synching purposes, for example).
Restarte Edge

Expected Results:

Expected Result: Edge uses the symlinked folder as the favorites folder.

Actual Results:

Dev Channel specific:



0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Kamen M.”

      Changed Assigned To to “Dave B.”

      Changed Assigned To from “Dave B.” to “Vasu P.”

      Changed Assigned To from “Vasu P.” to “Meg Q.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Meg Q.” to “IE S.”

      Changed Status from “Confirmed” to “Won’t fix”

      Changed Assigned To from “IE S.” to “Meg Q.”

      Changed Status from “Won’t fix”

      Changed Status to “Confirmed”

      Changed Assigned To from “Meg Q.” to “IE S.”

      Changed Status from “Confirmed”

    • Hello,

      Thank you for providing this information about the issue. We confirmed the problem, and implemented a solution on a later build of Edge. We are resolving this issue as a duplicate of an existing internal bug report. We look forward to additional feedback you may have on how we can improve Microsoft Edge.

      Best Wishes,
      The MS Edge Team

    You need to sign in to your Microsoft account to add a comment.

    Sign in