Network Tool is broken in F12

Issue #10003404


Michael D.
Nov 30, 2016
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 3 people

Sign in to watch or report this issue.

Steps to reproduce

Just open Dev Tools with F12 and switch to Network tab. Requests are not listed properly and the following message gets into Application log:

Fault bucket 127351599079, type 5
Event Name: IENonFatalError
Response: Not available
Cab Id: 0

Problem signature:
P1: microsoftedgecp.exe
P2: 11.0.14393.82
P3: 57a55786
P4: Network Tool
P5: 11.0.14393.206
P6: 57dacd54
P7: res://c:\windows\system32\f12\f12script2.dll/23/Common/CommonMerged.js
P8: 1
P9: Unexpected call to method or property access.
P10: F12

Attached files:

These files may be available here:

Analysis symbol:
Rechecking for solution: 0
Report Id: ab82fde4-b6b0-11e6-bf4f-74e54320c980
Report Status: 0
Hashed bucket: 4a9655190887899bce7fcb151411e96f


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

      Changed Assigned To to “Leo L.”

      Changed Assigned To from “Leo L.” to “Manoj P.”

      Changed Status to “Not reproducible”

    • OK, I understand that this might be related to some update that went wrong. Any suggestions regarding how I can troubleshoot it?

    • Changed Status from “Not reproducible”

    • Happens on both my desktop and laptop!

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

    • I’ve found the root of my problem.

      See my question on MSDN Forums.

      It’s OK to close this issue

    • Microsoft Edge Team

      Changed Assigned To from “Brad E.” to “Paolo S.”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed” to “In progress”

      Changed Title from “Network Tool is broken” to “Network Tool is broken in F12”

      Changed Assigned To to “Ivan P.”

      Changed Assigned To from “Ivan P.” to “Sorin O.”

      Changed Status from “In progress”

    • Hello,

      Thank you for sharing your problem and solution. Please reopen this case if you have new information about this specific issue for us to investigate.

      Best Wishes,

      The MS Edge Team

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

    Sign in