Microsoft Support will require updating the server to the latest cumulative update before troubleshooting core OS instabilities.
Microsoft later issued out-of-band hotfixes, but no official re-release occurred.
In the lifecycle of Microsoft’s server operating systems, few builds encapsulate the transition from traditional on-premises infrastructure to hybrid cloud readiness as clearly as . Released initially around April 2017 as a cumulative update for the RTM version (build 14393), this specific build number reappeared in enterprise patch management discussions in 2021 due to its long-term servicing channel (LTSC) nature. Far from being a random version string, “14393.3970” represents a snapshot of Microsoft’s disciplined update cadence, security hardening, and stability improvements during a period when server administrators were grappling with Nano Server, Containers, and Shielded VMs.
Are you trying to for this build?
As a cumulative update, Build 14393.970 focused on reliability and bug fixes rather than major new OS features:
Microsoft supports an in-place upgrade from Windows Server 2016 directly to newer versions like Windows Server 2022 or 2025. Maintenance Best Practices
Article last updated: March 2025 (to reflect historical research for legacy systems). windows server 2016 build 14393970 enus april 2017 2021
dism /Image:C:\Mount\Dist /Add-Package /PackagePath:C:\Updates\Windows10.0-KB4015217-x64.msu Long-Term Maintenance Risks
The Milestone: April 2017 Update (Cumulative Update KB4015217)
When booting from an ISO of this generation, engineers can choose between two main structural configurations: Microsoft Support will require updating the server to
In 2021, Windows Server 2016 mainstream support ended on (extended support runs to January 2027). However, many air-gapped or compliance-bound servers (finance, healthcare, defense) were still on builds from 2017–2018.
My plan is to structure the article by first introducing Windows Server 2016, then detailing the build 14393.970 and its associated KB4016635 update, including the fixes it provided. Next, I will cover the upcoming April 2017 security update (KB4015217) and the critical MS17-010 (EternalBlue) vulnerability. The article will then explain the significance of the "2021" reference, discuss the supersession of this old build by later cumulative updates, and provide guidance for administrators. It will conclude with the support lifecycle for the operating system. I will cite the relevant sources, such as the Softpedia article for the fixes in KB4016635, the Microsoft Q&A discussion for the supersession note, and the update history for KB4015217.
Windows Server 2016 Mainstream Support ended on January 11, 2022. Leading up to 2021, administrators utilized the stable 14393 branch to maintain compliance while preparing migration paths to Windows Server 2019 or Windows Server 2022. Installation and Deployment Best Practices Released initially around April 2017 as a cumulative
