Edge showing blank developer toolbar

As per the original post, I experience the same issues with the F12 developer tools. Essentially, after enabling the F12 developer tools, the “inspect element” option becomes available within the right-click context menu, but utilising it (or the F12 keyboard shortcut) splits the window vertically, but the right-side window is blank/empty.

I have repaired and reset the application through the “apps and features” interface, and have forcefully purged and reinstalled it via the PowerShell, but the issue persists. Version numbers are identical to the original post: Windows 10 Pro 1803 17134.137, Edge 42.17134.1.0, and EdgeHTML 17.17134. A virtual machine with the following version numbers does not experience the issue: Windows 10 Pro 1709 16299.522, Edge 41.16299.522.0, and EdgeHTML 16.16299).

Anyway, this is the final straw for me with Microsoft Edge. In addition to the lack of functional developer tools, the real-world performance (i.e. not cherry-picked synthetic benchmarks) is atrocious.

Same here:
Windows 10 Pro 1803 (Build 17134.165)
Edge 42.17134.1.0
EdgeHTML 17.17134

Hello all,

Is everyone still experiencing this issue?  As mentioned in the previous ticket, I am guessing that creating a new user/account on the same machine does not have this issue?

This issue was fixed, however, it appears that one some machines and for some upgrade paths that this issue persists.

Some options:

1. Use a new user account
2. Run the “Reset this PC” and select to keep your personal files.
3. Try running the health and DISM commands from the following link.  I am guessing that the powershell "reset edge"/appx remove and reinstall might be similar.

Wish I had better an easier solution.  I would like to know if a recent update has corrected this issue for anyone.

Steve

For me it is not possible to create a new user account since i’m a user using server 2012 with active directories where user data (home dir/profile etc) are located.

Since the tool can be run outside the browser window, is there a way (cmd line etc) to launch it separately and try if that works?

Reset, repair and reinstalling Edge did not help.

Creating a new user is not an option. Tested with my personal account and also local Administrator account (which had not used Edge before).

Resetting PC is also not possible.

What is causing this issue?

Same here,
Did a Dism which found no issues, then removed the edge dir in /user/…/packages/
Rebooted machine reinstalled edge via powershell command etc.

Still an empty development panel.

I also forced the Allow Developer Tool in the group policy for the local machine and on the Remote group policy for the clients on the server. regretfully this also did not made any difference.

This is occurring across the computers of the organization I work for. We are many web developers who need access to the development panel. It wouldn’t be realistic for everyone in the organization to reset their computers or use new profiles.

I have this issue and I can no longer do my work with your browser.

I have a brand new, fresh, unmodified install of Windows 10 with Edge and no extensions. I work for a company with a fairly serious data policy.

Microsoft Edge 42.17134.1.0
Microsoft EdgeHTML 17.17134

When will this issue be resolved?

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

I can confirm that the Powershell fix from Daniel N. worked immediately without any problems.

Thank you Daniel.

Confirming that the Powershell fix works on my PC.

Thanks Daniel.

Thanks Daniel, not all heroes wear capes.

Indeed, it worked for me as well. Thank you.

What is the powershell command? Can I just say what we’re all thinking right now? Microsoft please stop with the web browsers. It’s quite clear you do not have the time or correct people to write a proper one. For years you have disappointed users and developers alike. At what point does one just give in and let others do it? There’s really no point in creating one. Is there?

Fix worked for me as well.

Hi the powershell command worked for me .

Add-AppxPackage -register “C:\windows\SystemApps\Microsoft.MicrosoftEdgeDevToolsClient_8wekyb3d8bbwe\AppxManifest.xml” -DisableDevelopmentMode -Confirm:$false

I’d like to add my gratitude to Daniel for his powershell fix.
Developer tools working again.

I can confirm Daniel N’s referenced powershell command fixed my issue. Dev Tools works again for me. Thank you!

I can also confirm that Daniel N’s solution resolves the issue. Thank you!

Too bad you cannot upvote comments here. I would upvote solution from Daniel N.
How come this does not come from edge team? Why edge team always suggest to reinstall OS (reset is essentially same) to troubleshoot console not opening in browser?

It’s work for me too good! Thank you Daniel!

Thank You Daniel. I killed a morning trying to fix this and your solution worked immediately.

It is amazing that MS cannot seem to figure out the cause or solution. Perhaps this will push them to a real solution.

OMG, Daniel; thank you. This problem is such a stupid problem. I CANNOT believe the team over to Microsoft Edge couldn’t solve this. Such a straightforward answer that did not require a reinstall of Windows as the MSE staff was telling people to do.

Thanks, Why does Microsoft not fix this ASAP?

+1 for Daniel N 's command. Thank you Daniel
-1 for Microsoft support

PS I am not a Microsoft hater, I love vscode for example :)

This really saved my day. We had this problem on some of our company computers. Thank you Daniel.

Daniel N. thanks for fix worked for me as well.

Powershell command worked for me.
Now if Microsoft can fix the right-click copy delay in address bar I will be really happy.

it didn’t work for me. I am still unable to open developer tools. any suggestions?

Me too, still happening even after I ran the command and repair and restore the Edge. I am unable to use it.

Nome do aplicativo com falha: MicrosoftEdgeCP.exe, versão: 11.0.17134.376, carimbo de data/hora: 0x5bcc2819
Nome do módulo com falha: F12AppFrame2.dll, versão: 11.0.17134.376, carimbo de data/hora: 0x82a43996
Código de exceção: 0xc0000409
Deslocamento da falha: 0x0000000000013dbc
ID do processo com falha: 0x4488
Hora de início do aplicativo com falha: 0x01d476091eeb0b44
Caminho do aplicativo com falha: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe
Caminho do módulo com falha: C:\WINDOWS\SYSTEM32\F12\F12AppFrame2.dll
ID do Relatório: dd2967fa-0a1e-43ad-ac5e-b961d1c1b3ac
Nome completo do pacote com falha: Microsoft.MicrosoftEdge_42.17134.1.0_neutral__8wekyb3d8bbwe
ID do aplicativo relativo ao pacote com falha: F12

Fonte
Microsoft Edge Content Process

Resumo
Parou de funcionar

Data
‎06/‎11/‎2018 17:44

Status
Relatório enviado

Descrição
Caminho do Aplicativo com Falha: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe

Assinatura do problema
Nome de Evento de Problema: MoBEX
Nome Completo do Pacote: Microsoft.MicrosoftEdge_42.17134.1.0_neutral__8wekyb3d8bbwe
Nome do Aplicativo: praid:F12
Versão do Aplicativo: 11.0.17134.376
Carimbo de Data/Hora do Aplicativo: 5bcc2819
Nome do Módulo de Falhas: F12AppFrame2.dll
Versão do Módulo de Falhas: 11.0.17134.376
Carimbo de Data/Hora do Módulo de Falhas: 82a43996
Deslocamento de Exceção: 0000000000013dbc
Código de Exceção: c0000409
Dados de Exceção: 0000000000000007
Versão do sistema operacional: 10.0.17134.2.0.0.256.48
Identificação da Localidade: 1046
Informações Adicionais 1: ffb3
Informações Adicionais 2: ffb37e78b27b350fe8b0e3e173685bb4
Informações Adicionais 3: 6367
Informações Adicionais 4: 6367211e4cc97d8d07fe4ceb39786629

Informações adicionais sobre o problema
ID de Compartimento de Memória: 3b5ece1c9e08e30c17e6390d1a803d12 (1722126635957763346)

That are the logs from the events

Daniel N’s suggestion did work, but for me, Edge had to be running. The first time I tried it, it was closed, and didn’t resolve the issue. Running the command with Edge open fixed the issue immediately.

Jason P. That was the case for me too.

Fix worked for me as well.

Gracias ;)

I still have the same issues. I tried the Powershell command above multiple times, with and without Edge open.

Microsoft Edge 42.17134.1.0
Microsoft EdgeHTML 17.17134

The proces crashes when I press F12 and the page reloads, after a few times hitting F12 Edge simply exits silently.
Event log:

Faulting application name: MicrosoftEdgeCP.exe, version: 11.0.17134.376, time stamp: 0x5bcc2819
Faulting module name: F12AppFrame2.dll, version: 11.0.17134.376, time stamp: 0x82a43996
Exception code: 0xc0000409
Fault offset: 0x0000000000013dbc
Faulting process ID: 0x4814
Faulting application start time: 0x01d47b84c33367a0
Faulting application path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe
Faulting module path: C:\Windows\SYSTEM32\F12\F12AppFrame2.dll
Report ID: 45aa2063-e594-400c-85d0-39e7311b23f2
Faulting package full name: Microsoft.MicrosoftEdge_42.17134.1.0_neutral__8wekyb3d8bbwe
Faulting package-relative application ID: F12

Same here, same issues. I also tried the Powershell command above multiple times, with and without Edge open - did not work. Strange to see that these issues are being marked as fixed without comments or tips from the Edge team. :/

Because of this bug, I was stopped dead debugging an Edge-specific issue in my product today. When run with Edge open, Daniel N’s powershell fix worked for me. Does anybody have any explanation of what it does or why it is necessary?

Microsoft, any comments? The first report was July, the problem is still cropping up as of November, and it was closed as “fixed” without any comment on the fix from Microsoft.

Many times on this tracker, I’ve seen Microsoft close a bug as "fixed", and leave no information about the fix or when to expect it. Then the actual fix comes out sometimes much later in a Windows update. In my public bug tracker, I don’t close a bug as “fixed” until the fix is actually available to users in some form.

The PowerShell command what I wrote is for re-registering the Edge dev tool UWP app package. The edge dev tool is basically a separated app.

Who still experiencing issues, like crash on F12, they could try to re-register Edge itself as well with the following command (close the Edge first):

Add-AppxPackage -register “C:\windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\AppxManifest.xml” -DisableDevelopmentMode -Confirm:$false

And for the dev tool the command once again:

Add-AppxPackage -register “C:\windows\SystemApps\Microsoft.MicrosoftEdgeDevToolsClient_8wekyb3d8bbwe\AppxManifest.xml” -DisableDevelopmentMode -Confirm:$false

Also you could try the following:

“Press Win + I to Open Settings Then Select Apps. Next, on Apps & features tab, find the name of the missing app. Click the app and select Advanced options. You will found The Repair and Reset option. First Try to repair the App while may fix the errors, And Restart windows to take effect the changes.”

Thank you for your reply and ideas. Unfortunately after attempting all 4 methods my dev-tools still are blank and Edge is still crashing while attempting to open them.

Same as Nick H above. I tried all the suggested fixes but developer tools on edge 42.17134.1.0 crash. Very frustrating as I have been using inspect element for quite a while. Now I have reverted to using IE. Any more ideas on how to fix this problem?

The latest Windows 10 1803 update “KB4467702” seems to have fixed this for me. Don’t know why but there you are.

Same to me.
I confirm that is fixed after the Windows 10 1803 cumulative update KB4467702. To everyone that couldn’t solve it by the solutions here, the update fixed it.

The latest windows update, fix the issue for me. Thanks!

Yes, the update fixed it! 🎉