MC1188937 Low
WINS removal: Moving forward with modern name resolution
Summary AI-generated
WINS will be removed from Windows Server after 2025; migrate to DNS-based name resolution before Windows Server 2025 support ends in November 2034.
Suggested actions AI-generated
- Audit NetBIOS dependencies
- Migrate to DNS solutions
- Update or retire legacy apps using WINS
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1478819 Windows Deployment Services (WDS) deprecation in the next Windows Server release
- MC1227478 Advancing Windows security: Disabling NTLM by default
- MC1388721 30-Day Reminder: Final deployment phase for Kerberos RC4 hardening begins with the July 2026 Windows security update
- MC1462813 Prepare for the removal of WMIC from Windows 11
Original post from Microsoft
If you manage Windows Servers, plan for removal of Windows Internet Name Service (WINS). WINS was officially deprecated since Windows Server 2022 and will be removed from all Windows Server releases following Windows Server 2025. Standard support will continue through the lifecycle of Windows Server 2025, until November 2034. We encourage you to migrate to modern Domain Name System (DNS)-based name resolution solutions before then.
When will this happen:
- WINS deprecation was announced in Windows Server 2022. Deprecation means the feature remains supported and maintained, but there is no further active development or new functionality planned.
- November 2034 is the end of the lifecycle for Windows Server 2025, which also marks the end of support for WINS.
How this will affect your organization:
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
Please prepare, evaluate, and migrate to modern Domain Name System (DNS)-based name resolution solutions.
What you need to do to prepare:
Take proactive 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.
Consult additional resources for compete details and guidance.
Additional information: