dasHost.exe is causing udp broadcast flood on 22222 or 10004 ports...

Anonymous
2024-10-16T07:33:40+00:00

Hi i have problem with Device Association Framework Provider Host..

I checked das host is running from right place C:\Windows\System32

Its signed by ms.

How to stop it? It is hundreds broadcast connections per miute..

System is updated, antivirus is working.

Windows for home | Windows 11 | Internet and connectivity

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

61 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2025-03-05T03:36:15+00:00

    When blocking outbound UDP 3289, 10004 and 22222 packets, are there any effects such as printer scanning?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-02-26T17:58:13+00:00

    I'm seeing it on every computer running 24H2, not on the ones running 23H2.

    It makes them pretty much useless until users restart, as they don't have permissions to kill the process.

    dasHost.exe is using 100% of the CPUs on brand new i9s and using all 64Gb of RAM.

    This really needs to be addressed!

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  3. Anonymous
    2025-02-13T12:03:58+00:00

    Does this problem occur on 23H2 and 24H2, and has anyone tried installing the February 2025 cumulative patch? Does it resolve this issue?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-02-06T17:55:19+00:00

    We just noticed this as well. 1000's of broadcast packets sent out to the network from computers. killing dashost.exe stops it, but it just comes back.

    C'mon Microsoft!

    If your going to force a workflow change down our throats, at least make sure it works.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2025-02-04T16:19:19+00:00

    I've tried multiple things from the changing to the "PreferLegacyPrintDialog" to blocking outbound ports in the firewall which I wanted to avoid. When changing over to the legacy print dialog the issue would still arise when printing from edge or chrome. After that failed I tested blocking the outgoing ports 3289, 22222, and 10004 on a couple of devices. This didn't seem to have any negative effects on my users and that is currently what is being deployed via GPO. No issues since. Microsoft seems to be ignoring the issue so until they address it I will have this firewall block in place.

    Was this answer helpful?

    0 comments