Windows Server 2016 Build 14393970 Enus April 2017 2021

By 2021, to secure this build you would need hundreds of subsequent cumulative updates. Running 14393.970 in 2021 would leave the server vulnerable to:

Your string includes “2021.” If this image was created or modified in 2021, that means one of two things:

Do not use a pure April 2017 build (14393.970) on any network-connected system in 2025. It is missing: windows server 2016 build 14393970 enus april 2017 2021

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.

  • Fixes for:

    • 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. By 2021, to secure this build you would

    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.

    You wrote:
    windows server 2016 build 14393970 enus april 2017 2021 Your string includes “2021

    However, build 14393970 does not exist in official Microsoft documentation.
    The correct Windows Server 2016 RTM build number is 14393.
    It seems like there might be a typo – possibly 14393.970 or a similar cumulative update number.

    # 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