Cannot attach to default Edge with DevTools Protocol but Chrome can

Huy Nguyen 21 Reputation points
2022-12-09T08:46:53.727+00:00

I was trying to use DevTools Protocol with Edge following this guide. I ran MicrosoftEdge.exe --remote-debugging-port=9222 (made sure no other instance of Chrome or Edge are opening) then navigate to localhost:9222/json using Firefox, however no connection was made.

I tried again with Chrome chrome.exe -remote-debugging-port=9222 then navigate to localhost:9222/json and it worked.

What went wrong in Edge?

Microsoft Edge Microsoft Edge development
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2022-12-12T03:13:42.433+00:00

    Hi @Huy Nguyen ,

    I have successfully reproduced this issue. What I've found out is, you might have some Edge processes remain, so that --remote-debugging-port=9222 is not recognized when you inspect at edge://version/. You can simply kill all the existing msedge.exe processes to resolve the problem. Please use the following command:
    taskkill /f /im msedge.exe

    After that, you should be able to enable the remote debugging feature.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Best Regards,
    Shijie Li

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.