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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2025-04-11T13:40:51+00:00

    Was scanning my site network (Wireshark) yesterday and located a subject PC that was generating multiple packets on port 22222/10004. It had the KB5055523 2025-04 patch installed, so MS either haven't fixed or it is something else connected with printer discovery. I applied the registry key

    [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Print\UnifiedPrintDialog] "PreferLegacyPrintDialog"=dword:00000001

    Re-started PC and all went quiet. I do not have any idea what triggers this. I see small bursts of UDP 22222 from various machines but that is all. Something appears to get stuck in a loop when the flood is happening - I can see 75 or more UDP packets to 22222 and 10004 from a PC in 1 second.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-04-11T13:57:57+00:00

    We've continued testing on behalf of Microsoft and have found the issue: When a limited user selects print, the window that opens begins searching for printers on the network, and this is when the flooding occurs indefinitely.

    This is the same that happens when you select add a printer in settings, except that the user hasn't selected add a printer, only print.

    Therefore, we were able to stop the flooding by creating a GPO that doesn't allow limited users to install printers.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2025-04-14T09:05:37+00:00

    Interesting. However, our users are all local administrators and the problem seems to happen randomly. The registry entry only affects the print dialog from within Edge/Chrome and as most of our users are printing from Edge I see a great reduction in the chatter on 22222. However, as another admin posted, the problem happens when users print from apps, like Excel, Acrobat. It therefore has to be something to do with the new print selector. As you point out, they aren't trying to install a printer, it must be the print dialog that is searching..

    By far the biggest broadcasters are those that don't have the registry entry set, It would appear that this entry only affects printing from the browser and doesn't revert the print selection window to the old version in Excel or other apps.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-04-15T10:11:40+00:00

    Hi All,

    Thanks for your helpful post. It's worked for me.

    • Add reg and restart comp, It's Done.
      [HKEY_CURRENT_USER\Software\Microsoft\Print\UnifiedPrintDialog]
      DWORD 32-bit named "PreferLegacyPrintDialog"1

    No more UDP BC Flood.

    Kind Regards.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2025-04-23T14:31:57+00:00

    What if we do not see that path with in the regedit the farthest i have seen is *HKEY_CURRENT_USER\Software\Microsoft*

    I do not see a Print folder.

    Was this answer helpful?

    0 comments