Share via

how to remove joined address from loopback pseudo interface 1 windows 10

Tuna Ayyıldız 0 Reputation points
2024-05-29T16:37:58.2+00:00

I have a routing setting defined on my computer and its priority is set to 1.

User's image

Although the address I expect from the multicast group is in my routing mask, it joins the loopback interface.

User's image

When I try another ip address that may be in the same group, it comes through without any problem. I can't figure out how to remove 239.0.12.1 address from the loopback interface and joined to interface 15.

Thanks in advance for your help

Windows for business | Windows Client for IT Pros | Networking | Network connectivity and file sharing
0 comments No comments

1 answer

Sort by: Most helpful
  1. Chen Tran 9,090 Reputation points Independent Advisor
    2026-03-30T17:27:53.03+00:00

    Hello Tuna,

    Thank you for posting question on Microsoft Windows Forum!

    Based on your query of removing 239.0.12.1 address from the loopback interface and joined to interface 15. Well! The fact of the matter is that you cannot manually "delete or remove" a joined multicast address from an interface while it is active. Multicast joins are dynamic and tied directly to open network sockets created by applications. As long as the application is running and asking for that group, the OS is going to keep that join alive on whatever interface it originally picked. Windows chooses which interface to use based on its routing table and metrics at the exact moment the application joins the group.

    Based on the above scenario, you can consider lowering the interface metric of interface 15. Since Windows calculates the total cost of a route by adding the Route Metric + Interface Metric. Loopback adapters often have extremely low default metrics, making them win the priority battle. You can try to give Interface 15 the highest priority on your system by forcing the interface metric of Interface 15 to be 1 (the highest priority possible). To make sure the Loopback adapter is not still competing with a metric of 1, you can check all your interface metrics by running this command netsh interface ipv4 show interfaces

    You can refer to the following articles for more information regarding your concerns.

    Hope the above information is helpful! If it is. Free feel to hit "Accepted" for benefitting others in community having the same issue too.


Your answer

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