Forum Discussion

stesch79's avatar
stesch79
Iron Contributor
Apr 16, 2020

Local Profile Remove Issue

In our environment, we only use local profiles in Edge. The default path upon initial configuration on the client is “%LOCALAPPDATA%\Microsoft\Edge Beta\User Data\Default”

 

We noticed that if the profile is removed via settings menu (e.g. for troubleshooting reasons) a new profile is created immediately and a new folder in "User Data" folder called "Profile 1" is created. After a second removal, a folder called "Profile 2" and so on.

 

On this on-prem local profile scenario, I would prefer to delete and recreate "Default" folder instead of creating a new folders.

 

We user UE-V to save some files from Edge, e.g. bookmarks. in the UE-V settings file we added the path to the default profile folder. In this case, we would need to add "Profile 1" up to "Profile 9999".

 

Could this behavior be changed?

16 Replies

  • Henno_Keers's avatar
    Henno_Keers
    Steel Contributor

    stesch79  we ran into the same problem with VMware UEM for profile management solution we use.

    Solution we use at our servicedesk:

    Rename the Profile x directory to Default, then remove the file "Local State" and the let the user start Edge & log on. After that it is fixed.

     

    reg, Henno

      • Henno_Keers's avatar
        Henno_Keers
        Steel Contributor

        Joachim_T I agree. But we are not close to the root cause of the problem we want to see the scale of the problem and involvement of the ServiceDesk on the issue.

        Otherwise one is not fixing the problem but automating a workaround.

         

        reg, Henno 

  • ThiloLangbein's avatar
    ThiloLangbein
    Brass Contributor

    stesch79 We configured https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#configureonpremisesaccountautosignin to make default profile not removeable. But we have  domain-joined computers/users only.

    • stesch79's avatar
      stesch79
      Iron Contributor

      ThiloLangbein Thanks. Yes, if I also change the BrowserSignin from 0 back to 1 (Default) and set ConfigureOnPremisesAccountAutoSignIn the behaviour is as you said, the removal of the profile isn't possible anymore.

       

       

       

       

    • stesch79's avatar
      stesch79
      Iron Contributor

      Joachim_T Thanks for the hint! Just linked to this thread. Maybe the root cause is the same.