Jul 24 2019 11:58 AM - edited Jul 24 2019 02:19 PM
I had put 2 of the enterprise group policies into the C:\Windows\PolicyDefinitions. those were:
msedge.admx & msedge.adml
msedgeupdate.admx & msedgeupdate.adml
after deleting all of them, Edge canary still says that "Your browser is managed by your organization". I can't update the browser, it downloads the update then i click on restart and after it restarts it stays on the old version and the restart button is still there.
there is no policy set that is related to the Edge.
Jul 24 2019 12:36 PM
Jul 24 2019 02:17 PM
SolutionOkay found the fix myself after watching lots of Youtube vids about the same problem in google chrome. the process is basically the same, just in a different registry branch.
so basically for some unknown reason Edge canary made this registry key automatically. I don't know why, I hope Edge team sees this and look into it.
here's the troublesome reg key.
Again I've never touched Registry before for Microsoft Edge. but to fix the problem I just deleted that reg key.
Aug 26 2019 12:20 AM
When you apply policies through GPO, the appropriate reg keys are automatically created. This ensures that the policies are still applied even when you are not connected to your corporate network.
I agree this is not very clear, and I hope the Edge team can add an option to the Uninstaller to detect the keys and delete them if required.
Aug 26 2019 12:27 AM
Aug 26 2019 12:40 AM
This is known as registry tattooing. I'm not an expert on it myself, but you can read these articles and watch some Youtube films for more info.
As this is a GP Policy, the reg keys should normally be removed when the policy is no longer applied, as they are not tattoo. I hope somebody from the Edge team can confirm this.
https://sdmsoftware.com/gpoguy/whitepapers/understanding-policy-tattooing/
Aug 26 2019 12:58 AM
After reading your initial question again, it sounds like you copied the ADMX files directly to the C drive of a computer, instead of configuring them through Group Policy. Is that correct?
If you are working in an environment without Group Policy, you can always create the reg keys manually on a computer. See the help file here for examples - https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies
Aug 26 2019 01:09 AM
Jul 24 2019 02:17 PM
SolutionOkay found the fix myself after watching lots of Youtube vids about the same problem in google chrome. the process is basically the same, just in a different registry branch.
so basically for some unknown reason Edge canary made this registry key automatically. I don't know why, I hope Edge team sees this and look into it.
here's the troublesome reg key.
Again I've never touched Registry before for Microsoft Edge. but to fix the problem I just deleted that reg key.