Reputation: 284
After upgrade to Windows 10, I can't get the F12 Developer Tools to show / work under MS Edge.
IE 11 developer tools do still work, but I can see rendering differences on my websites I am working on between them, so could do with getting them working under Edge.
I am presuming they are available??
Have already tried the re-register packages fix, as well as reset Internet Options, but nothing works.
Upvotes: 19
Views: 39820
Reputation: 11
three dots
in the upper-right corner of the window.Settings
from the drop-down menu.System
section.Open the Developer Tools
when F12 key is pressed to the On
positionUpvotes: 1
Reputation: 33
I don't know if this will help anyone. But I use edge a lot and after one update my F12 didn't work, I searched and found out that the update turned off the F12 on edge settings. Open the Settings find for F12 and mine was disabled. That simple, and never thought about it.
Upvotes: 1
Reputation: 152
I have this problem today!
I debugged yesterday, no problem, then ran the latest big microsoft update last night and today I have this problem.
You have to close the tab and reopen it and then everything is ok!
Upvotes: -1
Reputation: 146450
Absolutely nothing worked for me, except this:
Using Administrator permissions, delete the following files and restart Developer Tools:
The folder is %windir%\SystemApps\Microsoft.MicrosoftEdgeDevToolsClient_8wekyb3d8bbwe\microsoft.system.package.metadata\Autogen\
and the exact file depends on system arch:
JSByteCodeCache_64
JSByteCodeCache_32
Upvotes: 0
Reputation: 184
The following issue page contains a solution for this in the comments, which worked for me: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/18153935/
If you are allowed to use powershell, execute the following command as your user to fix the dev tool:
Add-AppxPackage -register "C:\windows\SystemApps\Microsoft.MicrosoftEdgeDevToolsClient_8wekyb3d8bbwe\AppxManifest.xml" -DisableDevelopmentMode -Confirm:$false
Upvotes: 12
Reputation: 37
The "developer tools blank" phenomenon is a known issue, as you can see here: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/15458103/
The solution is yet unknown. I have the same effect here on my computer with one account, but I can see the tools page with a different user account on the same machine. So I think this might be an issue connected to the user profile.
Upvotes: 2
Reputation: 268344
I work on the Microsoft Edge team, and have not personally heard of any issues regarding the developer tools not working. As pointed out in another answer here, the tools will only be available via menu and F12 when you navigate to a document. The tools don't work for things like the New Tab Page.
If you continue to experience issues with the Developer Tools, please share additional information about your build of Windows 10 (run winver
from Run), and Microsoft Edge (version number available in Settings). I'll gladly file an issue for further investigation.
In the meantime, you could try another utility on Windows 10 called the F12 Chooser. You'll find this under C:\Windows\System32\F12\F12Chooser.exe
. This will identify all possible debug targets presently opened on your machine. You should see an instance of Edge enumerated.
Upvotes: 7
Reputation: 141492
If you open Edge without having gone to a website first, then the F12 Developer Tools will not be available. For instance, if you just open a new tab, then you will not have the tools. Once you actually go to a website, the tools will again be enabled.
Upvotes: 3