F12 IEChooser - Network collection agent failed to start

Anonymous
2024-10-24T16:35:32+00:00

Hello !

I am trying to use IEChooser (F12) to track requests for a website in IE mode. This does not work on my computer : I can select the tab, navigate/edit the DOM, but the network tab itself is not working, I get an error "the network collection agent failed to start"

I also have an error that appears in the event viewer with the following message "Échec du démarrage de la session « DiagHubEtwSession.user_paged » avec l’erreur suivante : 0xC000009A". If I translate to english : "failed to start DiagHubEtwSession session with the following error : 0xC000009A"

I tried the following things (according to google searches) :

  • Using both 32 bit and 64 bit versions
  • Run the tool as both admin and normal user
  • Enable the diagnostic hub service
  • sfc /scannow
  • Probably some other things that I forgot to note

Can anyone help me ?
Thanks !

*** Moved from Microsoft Edge / All other issues / Windows 10 ***

Windows for business | Windows Client for IT Pros | Networking | Other

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.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Anonymous
    2025-01-27T04:17:05+00:00

    Hey guys,

    Just encountered this after upgrading to Windows 11, the service above doesn't exist so command did not work?

    Just letting you know.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-10-25T13:28:44+00:00

    Hello,

    Based on the information you provided, I suggest you try the following method to see if it can solve the problem that the network collection proxy cannot be started in the browser developer mode:

    1. Open cmd as an administrator and run the following command.

    sc config diagnosticshub.standardcollector.service start=demand

    1. Close the browser and restart it

    Best Regards

    Zunhui

    Was this answer helpful?

    0 comments No comments