I will first clarify the technical background, then present a structured essay on its significance, updates, and role in enterprise IT.
By 2021, Windows Server 2016 was five years into its 10-year LTSC lifecycle (mainstream support ended January 2022). Build 14393.3970 had long been replaced by dozens of later builds (e.g., 14393.4283, 14393.4585). However, the build number resurfaced in compliance audits and upgrade testing. Organizations migrating to Windows Server 2019 or 2022 would often test against a known stable build—like .3970—to ensure backward compatibility. Additionally, some industries (e.g., healthcare, manufacturing) with change control boards would freeze on a specific build like 14393.3970 for months, only moving to newer builds after extensive validation.
Thus, in 2021, mentioning build 14393.3970 signaled an environment that prioritized stability over freshness—a hallmark of LTSC philosophy. It also highlighted the burden of patch management: skipping too many cumulative updates meant missing critical security fixes, but applying every build introduced regression risks.
If you had the original MSDN media from April 2017:
en_windows_server_2016_x64_dvd_9327740.iso
But the actual build number inside would be 14393.970.
Windows Server 2016 was released to manufacturing (RTM) on September 26, 2016, with build 14393.0. The versioning follows the pattern:
14393 = core RTM branch, .970 = cumulative update revision.
A quick heads-up: There’s a typo in your build string (14393970 should be 14393.970). Below, we break down what this specific version represents and why the “2021” mention matters.
| Aspect | Verdict | |--------|---------| | Build 14393.970 (April 2017) | ✅ Historical reference only | | Using it in production (2025) | ❌ Extremely high risk | | Using it in an offline lab | ⚠️ Possible, but update immediately | | The “2021” label | Likely a repack date – check file hashes |
Bottom line: Unless you are researching a legacy bug from 2017, skip this build. Download a current, patched Server 2016 ISO instead. windows server 2016 build 14393970 enus april 2017 2021
Have an old ISO you need help identifying? Leave the file name in the comments.
Windows Server 2016 Build 14393.970 refers to a specific system state achieved after applying the March 22, 2017 cumulative update ( The references you found likely point to a custom "Gen2" ISO release
or an "all-in-one" (AIO) installer created by third-party collectors (such as Generation2). These versions often bundle the original 2016 installation media with cumulative updates released through 2021 to ensure a more secure deployment out of the box. Key Technical Details Original Build: Windows Server 2016 was released in 2016 with base build Build 14393.970:
Specifically indicates the server has been patched with the March/April 2017 updates. 2021 Context:
While the build version is from 2017, the "2021" tag in file names usually signifies that the installer includes additional security patches or administrative tools updated as late as 2021. Editions Typically Included:
These ISOs often contain Standard, Standard Core, Datacenter, and Datacenter Core editions. Life Cycle & Support Mainstream Support: January 11, 2022 Extended Support: Remains active until January 12, 2027 Maintenance:
Beyond build 14393.970, many subsequent cumulative updates have been released. For example, by late 2024, the stable build version had reached 14393.7428. Important Considerations for Deployment
Deploy Storage Spaces Direct on Windows Server - Microsoft Learn I will first clarify the technical background, then
Windows Server 2016 Build 14393.970 refers to a specific stable milestone reached through the March 22, 2017 cumulative update (KB4016635). This build is a part of the Windows Server 2016 (Version 1607) lifecycle, which serves as a critical foundation for modern hybrid-cloud environments. Build Overview and Core Specifications
This specific release (Build 14393.970) was a key update leading into the April 2017 patch cycle. It addressed critical security vulnerabilities and functional bugs that were discovered following the initial Release to Manufacturing (RTM) of Windows Server 2016 in late 2016. OS Version: Windows Server 2016 (Version 1607). Build Number: 14393.970. Release Date: March 22, 2017. Architecture: 64-bit (x64). Language: English (en-US). Key Features and Improvements
By April 2017, this build had matured to support intensive "Software-Defined Datacenter" (SDDC) initiatives. The primary enhancements in this version include:
Security Patches: Critical updates were delivered for the Windows Kernel, Internet Explorer, and the Scripting Engine to mitigate emerging threats.
Networking Stability: Significant improvements were made to the Host Network Service (HNS), which is vital for container networking and software-defined networking stacks.
Identity & Access: Enhancements to Active Directory Federation Services (AD FS) allowed for smoother authentication across diverse directories.
Nano Server Support: Continued refinements for the Nano Server installation option, including better recovery console tools and image building modules. Lifecycle and Support Milestones
Windows Server 2016 follows a long-term servicing model. While this specific build was a stepping stone, the broader 1607 version has a defined lifespan: KB4016635 (OS Build 14393.970) Relevance in 2021: Long-Term Servicing Reality By 2021,
22 Mar 2017 — KB4016635 (OS Build 14393.970) - Microsoft Support. Microsoft Support Windows 10 and Windows Server 2016 update history
The Lifecycle of Stability: Windows Server 2016 Build 14393.970
Windows Server 2016 represented a transformative shift for Microsoft, bridging the gap between traditional on-premises infrastructure and modern cloud-native architectures. Within its long history, Build 14393.970, released in March 2017 via KB4016635, stands as a critical checkpoint in the operating system's early maturity phase. A Foundation of Hybrid Innovation
At its core, Windows Server 2016 was built upon the same kernel as the Windows 10 Anniversary Update (Version 1607). It introduced several groundbreaking features that redefined server management: Windows Server 2016 | Центр оценки - Microsoft
It is important to clarify at the outset: Windows Server 2016 build 14393.970 (not 14393970) is the correct version string for the April 2017 cumulative update for the Windows Server 2016 Long-Term Servicing Branch (LTSB). The number “2021” in your keyword likely refers to a later search date or a misconception—Microsoft did not release a build with that exact 8-digit sequence. This article will provide a comprehensive technical deep dive into the genuine KB4015217 (build 14393.970) from April 2017, its implications for enterprise environments, and why it remains relevant to administrators researching legacy builds for 2021 patching cycles.
If your vulnerability scanner (Nessus, Qualys, SCCM) in 2021 flagged the absence of patches from 2017, you had to install KB4015217 before addressing more recent CVEs like CVE-2021-36942 (PetitPotam NTLM relay) or CVE-2021-26414 (DCOM RPC).
Skipping straight to a June 2021 update would fail because the update’s manifest required at least build 14393.970.
# From elevated PowerShell
wusa.exe "C:\updates\windows10.0-kb4015217-x64.msu" /quiet /norestart
# Check success
Get-HotFix -Id KB4015217
For offline servicing of a WIM or VHD:
dism /Mount-Image /ImageFile:C:\mount\install.wim /Index:1 /MountDir:C:\offline
dism /Image:C:\offline /Add-Package /PackagePath:C:\updates\kb4015217.msu
dism /Unmount-Image /MountDir:C:\offline /Commit