Disabling F12 Developer Tools in Edge Group Policy (RS1)

Not reproducible Issue #13283043

Open new issue

Browse all tracked issues

Details

Author
Minesh P.
Created
Aug 16, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
14.14393
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Hi

Is there anyway to disable “F12 Developer Tools” in Edge (38.14393.1066.0) on Windows 10 1607 (OS build - 14393.1358)?

Current I have tried both the user & computer based GPO & Local Policy settings and can see the REG_DWORD has been created, however the option within Edge is still available.

Thanks

Minesh

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      James M. Aug 18, 2017 2017-08-18T18:32:56.547Z

      Changed Assigned To to “James M.”

    • James M. Aug 18, 2017 2017-08-18T18:42:35.58Z Microsoft Edge Team

      Hello,

      Thank you for providing this information about the issue. We are best suited to test and correct broken features for future releases of MS Edge. I hope this link will help: https://answers.microsoft.com/en-us/windows/forum/windows_10-other_settings/f12-developer-tools/1f50a845-b573-475d-9984-29ba3bbd427e?auth=1

      If you want a new feature, please feel welcome to submit your request at http://uservoice.microsoftedge.com where other developers can up-vote your suggestion.

      Best Wishes,
      The MS Edge Team

    • Microsoft Edge Team

      Jacob R. Aug 22, 2017 2017-08-22T20:40:20.913Z

      Changed Title from “Disabling F12 Developer Tools in Edge” to “Disabling F12 Developer Tools in Edge Group Policy (RS1)”

      James M. Aug 22, 2017 2017-08-22T20:41:02.557Z

      Changed Status to “Won’t fix”

      James M. Sep 20, 2017 2017-09-20T21:48:39.12Z

      Changed Status from “Won’t fix” to “Not reproducible”

    • James M. Sep 20, 2017 2017-09-20T21:48:39.12Z Microsoft Edge Team

      Hello,

      Thank you for providing this information about the issue. After recent testing, we are unable to reproduce this problem in new builds of Edge. Please test this behavior in our latest insider build 16291.

      Best Wishes,
      The MS Edge Team

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

    Sign in