WINS removal: Moving forward with modern name resolution

Summary

This article provides essential information about the deprecation and planned removal of Windows Internet Name Service (WINS) from future Windows Server releases. Microsoft has announced that WINS will be removed from all Windows Server releases following Windows Server 2025, with full support continuing through November 2034. Organizations using WINS are strongly encouraged to migrate to modern DNS-based name resolution solutions.

Deprecation: A consistent and transparent process

Following a well-defined process for deprecating and removing features, we will ensure organizations have plenty of time to plan transitions and minimize disruption.

WINS was officially announced as deprecated in Windows Server 2022. Deprecation means the feature remains supported and maintained, but there is no further active development or new functionality planned. Customers with active WINS deployments are encouraged to start evaluating DNS-based name resolution for the future.

Note: For details on WINS deprecation and our broader approach, see Features removed or no longer developed in Windows Server.

Looking ahead: The WINS removal timeline

The next step after deprecation is removal. Windows Server 2025 will be the final Long-Term Servicing Channel (LTSC) release to include and support WINS. The feature will be removed from all Windows Server releases following Windows Server 2025.

Since LTSC releases arrive every 2–3 years, we are sharing this roadmap now, years in advance, so organizations have ample notice and planning runway. This approach aligns with giving IT teams time to prepare, evaluate, and migrate at their own pace.

Supporting WINS in Windows Server 2025

WINS is available in Windows Server 2025 and will receive full support—including security and quality updates—through the entire Windows Server 2025 lifecycle, extending until November 2034. Organizations have close to a decade from general availability of Windows Server 2025 to complete migrations from WINS to DNS-based name resolution solutions.

Key facts:

WINS is present and fully supported in Windows Server 2025 through November 2034.
The full Windows Server 2025 lifecycle policy is available here: Windows Server 2025 - Microsoft Lifecycle.
Now is the time to review dependencies, evaluate DNS migration plans, and make informed decisions.

What does this change mean?

Once removal takes effect, the following components will no longer be part of Windows Server:

WINS Server role and associated binaries
WINS Microsoft Management Console (MMC) snap-in
WINS automation APIs and related management interfaces

Important: Administrators should not expect WINS to be available in future Windows Server releases. Organizations relying on WINS for NetBIOS name resolution are strongly encouraged to begin migration planning immediately to avoid disruptions.

Why Microsoft is removing WINS

DNS is the modern standard: DNS offers a distributed, hierarchical namespace compliant with RFC 1034 and RFC 1035 and provides far superior scalability.
WINS centralized replication model: For technical reference, see [MS-WPO]: Windows Name Resolution.
Security improvements with DNSSEC: DNSSEC safeguards against spoofing and cache poisoning attacks that are not mitigated by WINS/NetBIOS. For more information, see Domain Name System (DNS) in Windows and Windows Server.
Modern applications are built for DNS: Key Microsoft services such as Active Directory, cloud platforms, and Windows APIs rely on DNS for name resolution. WINS has been deprecated in Microsoft's documentation for several years. For more information, see Windows Internet Name Service (WINS).
Lifecycle and deprecation policies: WINS is listed among deprecated Windows features and is progressing toward full removal. For more information, see Deprecated features in the Windows client.

Preparing for the transition

Organizations still dependent on WINS should proactively take steps now to ensure a smooth migration:

Audit dependencies: Inventory applications and services that rely on NetBIOS name resolution to understand impact.
Migrate to DNS: Implement conditional forwarders, split-brain DNS, or search suffix lists to replace WINS functionality with scalable, modern DNS solutions.
Update applications: Modernize or retire legacy applications that depend on WINS to avoid future compatibility issues.
Avoid temporary workarounds: Solutions like static host files do not scale and are not sustainable for long-term environments.

A decade to plan

Our goal is to make planning and migrations as predictable and low-stress as possible. With advanced notice and a full support runway, organizations can confidently modernize their environments at their own pace.

Take action

If your environment still uses WINS, now would be a great time to start evaluating options and engaging with Microsoft resources. We are committed to partnering with you on this journey—ensuring secure, robust, and future-ready name resolution across your infrastructure.

References

Third-party information disclaimer

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. We make no warranty, implied or otherwise, about the performance or reliability of these products.

We provide third-party contact information to help you find technical support. This contact information may change without notice. We do not guarantee the accuracy of this third-party contact information.