Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsSome links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
KB4013429 is Microsoft’s March 14, 2017 cumulative quality and security update for Windows 10 version 1607 and Windows Server 2016. On an applicable system, it installs build 14393.953. Get it through the Microsoft Update Catalog; the Catalog generates the package download from the matching result rather than providing one permanent direct-download URL. This is a historical update, not the latest patch for version 1607.
Official KB4013429 download and package choices
Use Microsoft’s KB4013429 Catalog search to find the package. Choose the entry matching both the operating system and architecture:
| Target system | Catalog result to select | Approximate first-install package size |
|---|---|---|
| Windows 10 version 1607, 64-bit | Update for Windows 10 Version 1607 for x64-based Systems (KB4013429) | About 1,105 MB, as stated by Microsoft for the first-install package |
| Windows 10 version 1607, 32-bit | Update for Windows 10 Version 1607 (KB4013429) | About 579 MB, as stated by Microsoft for the first-install package |
| Windows Server 2016, 64-bit | Update for Windows Server 2016 for x64-based Systems (KB4013429) | Not stated separately for this Catalog result; package variants and displayed sizes can differ |
The approximate sizes are Microsoft’s stated first-install sizes; check the Catalog entry for the specific package you select. Microsoft identifies applicability to Windows 10 version 1607 editions and Windows Server 2016. Server 2016 uses the x64 package; do not select the Windows 10 x86 result for it. Microsoft’s security bulletin separately lists Windows 10 version 1607 x86, Windows 10 version 1607 x64, and Windows Server 2016 x64 applicability (MS17-018).
Recommended Free Tools
To download, open the Catalog search, locate the matching result, click Download, then click the .msu link in the dialog and save the file. The Catalog may need scripting enabled and permission to open a pop-up. Check that the saved filename identifies KB4013429 and the intended architecture before installing. Microsoft’s support article for KB4013429 describes the update and its original delivery through Windows Update as well as the Catalog option.
#1 Best Overall
Use the Microsoft Catalog rather than an unofficial mirror. Its download dialog supplies the package link, which can be generated dynamically; a copied .msu URL may change or expire. The Catalog search page is the durable route to the official package.
Check the Windows version and architecture first
- Press Windows + R, type
winver, and press Enter. Confirm that the target is Windows 10 version 1607 or that its build belongs to the14393.xfamily. On Server 2016, confirm the server product and build. - Open Settings > System > About and check System type to distinguish a 32-bit (x86) from a 64-bit (x64) Windows installation.
The edition name alone does not establish compatibility: KB4013429 is for version 1607, not every Windows 10 release. An .msu is an update package, not an ISO or a general-purpose way to move a later Windows installation backward to build 14393.953. A later cumulative update may already include its fixes. Microsoft’s Windows Server release information records Server 2016 build 14393.953 with the March 2017 release associated with KB4013429.
What KB4013429 changes
Released March 14, 2017, KB4013429 is a cumulative quality and security update for Windows 10 version 1607, also known as the Anniversary Update, and Windows Server 2016. It raises the operating-system build to 14393.953, adds no major operating-system features, and supersedes the previously released KB4010672, according to Microsoft’s KB4013429 support article.
Microsoft’s fixes span desktop and server scenarios. They include delays in 3D rendering with multiple monitors; Start menu and other interface problems with roaming profiles; Japanese Input Method Editor graphics-resource leaks; Work Folders duplicate-file conflicts; WSUS downloads after Group Policy changes; Sysprep failures; and problems involving clustering, live migration, Storage Spaces Direct, redirected devices in Remote Desktop, and Active Directory Administrative Center crashes while editing user attributes. The article also covers updates across time zones, Internet Explorer, file servers, wireless networking, Maps, IoT upgrades, USB 2.0 removal, multimedia, Direct3D, Edge, Hyper-V, and Credential Guard.
The security changes affect components including Microsoft Edge, Internet Explorer, the Microsoft Graphics Component, IIS, SMB Server, the Windows PDF Library, kernel-mode drivers, Uniscribe, the Windows kernel, DirectShow, the operating system, and Hyper-V. For the complete update description and security details, consult Microsoft’s support article.
Rank #2
- 15.6" diagonal, HD (1366 x 768), micro-edge, BrightView, 220 nits, 45% NTSC.
Do not confuse it with KB4013418
KB4013429 is the cumulative update that produces build 14393.953. KB4013418 is a separate servicing-stack update released on the same date. Servicing-stack updates support the Windows installation and servicing mechanisms; KB4013418 alone is not the cumulative update that changes the operating-system build to 14393.953. Microsoft lists it separately in the KB4013418 Catalog search and its Catalog update details.
Install the downloaded .msu
Interactive installation
- Close open applications and confirm that you selected the package for the correct Windows product and architecture.
- Double-click the downloaded .msu file. Windows Update Standalone Installer checks the package; follow the prompts.
- Restart when requested. If this is a production machine, schedule the restart and validate the update in a suitable maintenance window.
- After restarting, check the resulting build as described below.
Command-line installation
For an interactive install, run this from Command Prompt, substituting the actual file path and filename:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
wusa.exe "C:PathTowindows10.0-kb4013429-x64.msu"
For unattended deployment where prompts should be suppressed and the restart handled separately:
wusa.exe "C:PathTowindows10.0-kb4013429-x64.msu" /quiet /norestart
/quiet suppresses prompts and /norestart prevents an automatic restart; neither removes the need to plan and complete the restart. Test the deployment and schedule reboot handling rather than forcing an unvalidated package onto production systems.
Rank #3
- 10th Generation Intel Core i5-1035G1 processor
- 12GB system memory for full-power multitasking
- 256GB Solid State Drive
- 15.6" Micro-edge touchscreen display
Verify the installed build
Run winver after the restart. For a system that installed KB4013429 and has not moved to a later cumulative update, the expected build is 14393.953.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →You can also check the update record with either command:
wmic qfe | findstr 4013429
Get-HotFix -Id KB4013429
If PowerShell returns no record, check Windows Update history or the Component-Based Servicing log at C:WindowsLogsCBSCBS.log. A later cumulative update can supersede KB4013429, so the original KB may not appear as the active installed update even when its fixes are included in the newer package.
Known issues and later corrections
Microsoft documented several issues associated with KB4013429:
- On Windows Server 2016 systems using Switch Embedded Teaming, changing a physical adapter’s link speed could cause a deadlock or bug check.
- Windows DVD Player and third-party applications using Microsoft MPEG-2 libraries could crash.
- Some Internet Explorer 11 and CRM 2011 forms could render incorrectly.
- Some Microsoft Store applications could fail to update with error
0x80070216.
Microsoft’s later KB4015438 addressed the first two issues and produced build 14393.969; see the KB4015438 support article. Microsoft addressed the IE11/CRM and Store problems in KB4016635. These follow-up fixes are one reason not to stop at KB4013429 unless that exact historical build is required.
Rank #4
- Latitude 7480 Laptop 14"
- Intel Core i7 6th Gen i7-6600U -Core Processor 2.6GHz (3.4GHz With Turbo Boost)
- 256 GB SSD Hard Drive & 16GB Memory
- 1920x1080 FHD resolution Non-Touch with Webcam and an integrated graphics chip
- Wireless Wifi & Bluetooth
Troubleshoot installation problems
“This update is not applicable to your computer”
Check the compatibility points in this order:
- Run
winverand verify the target is Windows 10 version 1607 or Windows Server 2016, not another Windows release. - Check whether the system is x86 or x64 and confirm that the Catalog result matches.
- Verify that the package is for client Windows 10 or Server 2016 as appropriate.
- Check whether KB4013429 is already installed or has been superseded by a later cumulative update.
- Review servicing prerequisites for the specific deployment state; a missing servicing update can matter in some environments, but there is no single prerequisite that should be assumed for every system.
Do not try to force an x86 package onto x64 Windows or the reverse. A component-store problem may also block servicing, but repairing system files cannot fix the wrong version or architecture.
Installation fails or rolls back
If version and architecture are correct, these Windows repair commands may help with some component-store or system-file problems. They are not guaranteed fixes:
DISM /Online /Cleanup-Image /RestoreHealth
Then run:
sfc /scannow
Restart and retry only after checking the system state. For servicing diagnostics, review C:WindowsLogsCBSCBS.log.
The Catalog download dialog does not open
- Allow pop-ups for
catalog.update.microsoft.com. - Enable scripting if the browser blocks the Catalog interface.
- Try another supported browser or an administrative workstation.
- Return to the official Catalog search instead of downloading from an unofficial file host.
- Before deployment, confirm the file identity and digital signature.
Windows Update offers a later update
That is expected for a cumulative update: later applicable packages supersede earlier ones. If the goal is to receive KB4013429’s fixes rather than reproduce its exact build, a later cumulative update is normally the more sensible target.
Quick Recap
Should you install KB4013429 now?
- Exact historical build required: Use KB4013429 when testing compatibility against build 14393.953, restoring an archival environment, or reproducing a specific 2017 baseline. Prefer an isolated or otherwise controlled system for that work.
- Repairing version 1607: Consider a later applicable cumulative update instead, because it includes earlier cumulative fixes and later corrections.
- Seeking a secure, supported system: Do not treat this 2017 package as a current patch baseline for an internet-connected production machine. Microsoft’s Catalog results for Windows 10 version 1607 include later cumulative updates, including 2026 releases. Follow the lifecycle and patch baseline applicable to your organization rather than stopping at 14393.953.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
