This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello,
I have been using this guide (Microsoft Edge DevTools Protocol Update - Microsoft Edge Development | Microsoft Docs) to launch Edge with the remote debugging port open to access the HTTP endpoints. However, with the latest update, it seems as if this approach is not working anymore, as the port is not open and I cannot access any endpoints. I have done this successfully many times in the past, and I have made sure to close all open versions of Edge before I run the command. I have tried with running the command with PowerShell and command line, and I have tried adding the flag --remote-debugging-port=9222 to the target of the Edge shortcut. None of these solutions worked. The same commands work on Google Chrome and I am successfully able to access the DevTools Protocol API. Am I doing anything wrong here? Did the newest update break the DevTools protocol or was this an intentional change?
Thank you.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I can reproduce the exact same issue as OP. I am using Windows 10 enterprise and version of 94.0.992.47 of Microsoft Edge. Is there something else that can be interfering with the devtools protocol?