If you are looking for the (April 2017, en-US), you need:
Note that Microsoft shifted the purpose of Nano Server during this lifecycle. If you deployed Nano Server in 2017 as a host OS, it must be migrated to Core or GUI versions, as Nano became strictly a container base image. Looking Forward: Extended Support and Beyond
The evolution of modern enterprise infrastructure relies heavily on stable, long-term operating system updates. Windows Server 2016, built on the robust codebase, represents a major milestone in Microsoft's server history . Specifically, the progression from the April 2017 updates up through the final lifecycles in 2021 highlights a critical era of security hardening and stability for enterprise IT administrators.
: en-US indicates the standard English (United States) language pack distribution.
| Feature | Details | | :--- | :--- | | | KB4016635 | | Associated Build Number | 14393.970 | | Target OS | Windows Server 2016, Windows 10 Version 1607 | | Language | English (United States) / en-us / 多语言 | | Release Date | March 22, 2017 | | Update Type | Cumulative (Quality Update) | | Update Size (x64) | ~1062.7 MB (up to 1.06 GB) | | Prerequisite | No specific prerequisite, but supersedes KB4015438 | windows server 2016 build 14393970 enus april 2017 2021
– Build 14393.970 broke docker login to private registries using basic auth. Fixed in May 2017’s KB4019472.
How to find the build and OS version of Windows 10 and Server
As of 2021, Windows Server 2016 is still a widely used and supported server operating system. Although Microsoft has released newer versions, such as Windows Server 2019 and Windows Server 2022, the April 2017 update remains relevant for organizations that continue to rely on Windows Server 2016.
If you had the original MSDN media from April 2017: If you are looking for the (April 2017,
For any Windows Server administrator tracing legacy infrastructure, from April 2017 represents the first comprehensive security refresh after Server 2016’s RTM. It fixed critical Hyper-V, S2D, and LSASS issues while modernizing the servicing stack for future updates.
April 11, 2017
Are you planning a away from Windows Server 2016? Share public link
: Addressed bugs in the servicing stack and provided pre-installed updates to streamline new installations. Windows Server 2016, built on the robust codebase,
Between 2017 and 2021, many SSUs were released to improve the update process itself, often necessary before applying monthly cumulative updates.
Fixed an issue where CredentialGuard-enabled computers would submit two bad logon attempts for every single bad password provided, causing premature account lockouts.
Ensuring seamless connectivity with Azure Arc and hybrid cloud management tools. Deployment Best Practices for "EN-US" ISOs
: A system reboot is required after installing this cumulative update.