A developer prepares a secure Windows software package for x64, x86, and ARM64 systems in a server room.
Microsoft has refreshed the Defender package for offline Windows installation images. If your organisation still deploys from a WIM it built months ago, this is the update for that "golden" image.

The package is documented in KB4568292, "Microsoft Defender update for Windows operating system installation images." It now lists Defender package version 1.463.217.0, which updates the antimalware client, engine and signatures inside OS installation images. Neowin covered the release under a headline calling it the "most updated Defender ever" for Windows 11 and 10 ISOs. The version numbers are real. The superlative, and some of the timing claims around it, are less solid. Here's what Microsoft's documentation actually supports and how to use the package.

A developer prepares a secure Windows software package for x64, x86, and ARM64 systems in a server room. What changed in KB4568292​

Microsoft's change log for KB4568292 has an entry dated November 12, 2026. That entry says Microsoft updated the Defender package, platform, engine and security intelligence version numbers, plus the download sizes for each architecture. The page now lists:

ComponentVersion
Defender package1.463.217.0
Platform4.18.26100.4
Engine1.1.26100.4
Security intelligence1.463.217.0

Approximate download sizes are 146 MB for ARM64, 228 MB for x86 and 252 MB for x64. The page also says Microsoft is currently not aware of any issues with the update.

This is the second refresh in about a month. The change log shows an earlier version bump on October 20, 2026, and Neowin reported that package on November 2. Before that, the page was updated on August 13. WindowsForum noted at the time that the August refresh had a mismatch: the "Defender package version" line still displayed 1.447.236.0, while the same page's August 13 change log said the version information had been refreshed. This time the package version and the security intelligence version both read 1.463.217.0, so that problem appears to be fixed.

Section summary: Microsoft's image-servicing kit now carries platform 4.18.26100.4, engine 1.1.26100.4 and security intelligence 1.463.217.0. The page was updated on November 12, 2026, and lists no known issues.

Checking the headline claims​

Neowin says the package came out "just a day before" the November Patch Tuesday update. On that basis, it calls this probably the most up-to-date Defender package for Windows ISOs ever, or at least in recent memory. Microsoft's documentation doesn't back that up:

  • Patch Tuesday: KB5132061, the Windows 11 security update for versions 26H2, 25H2 and 24H2, is dated November 10, 2026 (OS builds 26300.9974, 26200.9974 and 26100.9974).
  • Defender kit: The KB4568292 change entry is dated November 12, two days later. A page-edit date isn't necessarily the date the files went live. Still, nothing Microsoft has published shows the package arriving the day before Patch Tuesday.
  • Freshness: Neowin says security intelligence 1.463.217.0 came out toward the end of October. It also says the newest intelligence update was 1.463.359.0 when it wrote the story. If both are right, the image kit was already a few weeks behind the live definitions on release day. That's normal for this kit, and it doesn't fit well with "most updated ever."

There's also the ISO question. Neowin suggests that downloading the latest Windows 11 media with the Media Creation Tool should get you these definitions. KB4568292 doesn't say that. Microsoft documents this package as something administrators apply to WIM and VHD files themselves. It doesn't promise that consumer ISOs are rebuilt with it. Treat "my fresh ISO already has 1.463.217.0" as something to check, not something to assume. Verification steps are below.

Section summary: The version numbers check out. The "day before Patch Tuesday" timing and the "most updated ever" label aren't supported by Microsoft's documentation, and the Media Creation Tool claim is unconfirmed.

Why a stale image matters​

Microsoft says OS installation images may contain outdated antimalware software binaries. A newly deployed machine can therefore spend its first hours with weaker Defender protection until it pulls its first antimalware update. Think of a building whose alarm codes are from last spring: it probably works, but you wouldn't bet on it.

According to Microsoft:

  • The package includes monthly platform and engine fixes and the latest security intelligence available when it was released.
  • Defender updates also carry performance fixes. Microsoft says devices using another security product can still benefit.
  • Microsoft recommends servicing images every three months. In its words, "We recommend that you regularly service OS installation images to update Microsoft Defender binaries and minimize this protection gap in new deployments."
  • You can apply the latest cumulative update (LCU) and this Defender package in either order.

Supported installation images:

  • Windows 11
  • Windows 10 ESU
  • Windows 10 Enterprise LTSC 2021
  • Windows 10 Enterprise LTSC 2019
  • Windows 10 Enterprise LTSB 2016
  • Windows Server 2022
  • Windows Server 2019
  • Windows Server 2016

Microsoft also has a support policy for older packages. Once a new package version ships, the previous two versions get technical support only, and anything older is no longer supported. An image serviced with a kit from early 2026 is therefore out of support.

How to apply the update to an offline image​

This is for IT administrators who maintain deployment images. Home users updating a running PC don't need it, because Windows Update and Defender's own update channel already handle that.

Prerequisites​

  • A 64-bit Windows 10 or later environment to run the tool
  • PowerShell 5.1 or later
  • The Microsoft.Powershell.Security and DISM modules installed
  • An elevated PowerShell session (Run as administrator)
  • A backup copy of the image. The tool can remove the update, but Microsoft still recommends keeping a backup.

Steps​

  1. Download the kit that matches your image's architecture. Microsoft notes that different update packages are required for different Windows OS image architectures. The downloads are named defender-update-kit-[x86|x64|arm].zip.
  2. Extract the ZIP. You'll get the defender-dism-[x86|x64|arm].cab package and the DefenderUpdateWinImage.ps1 helper script.
  3. Find the right image index. A single install.wim often holds several editions. Run:
    Dism /get-imageinfo /imagefile:<path_to_OS_Image>
    Note the index for the edition you deploy. Microsoft's example shows Windows 11 Enterprise at index 3, but the index varies from one install.wim to another.
  4. Apply the update:
    DefenderUpdateWinImage.ps1 -WorkingDirectory <path> -ImageIndex ImageIndexNumber -Action AddUpdate -ImagePath <path_to_Os_Image> -Package
  5. Confirm it worked by listing the installed update details:
    DefenderUpdateWinImage.ps1 -WorkingDirectory <path> -Action ShowUpdate -ImagePath <path_to_Os_Image>
    This is also the way to check what a downloaded image actually contains before you rely on it.
  6. Roll back if needed:
    DefenderUpdateWinImage.ps1 -WorkingDirectory <path> -Action RemoveUpdate -ImagePath <path_to_Os_Image>

Common pitfalls​

  • Wrong architecture: Using the x64 kit on an ARM64 image won't work. Pick the kit that matches the image, not the PC you're running the tool on.
  • Wrong index: If you patch index 1 but deploy index 3, the image you actually ship is still out of date.
  • Live images: Microsoft warns that you should not use this package to update live images because it can damage the Windows installation that Is running inside the virtual machine. The package is for offline images only.
  • 32-bit host: The tool needs a 64-bit Windows environment, even when you're servicing an x86 image.

Where this fits with the November updates​

Neowin tied the Defender kit to the rough start of KB5132061. Microsoft's KB5132061 page did list a known issue where the November security update might fail to install, with error codes 0x80070306, 0x800f0989 or 0x800f0993. Microsoft says the fix ran automatically through Windows Update starting November 11 and marked the issue resolved on November 16.

The same update fixes a printing problem: adding an Active Directory-published printer through Settings could fail with error 87. Microsoft says the October 2026 update introduced that bug. On November 17, Microsoft also added a new known issue on servers: SQL Server linked server connections might stay open.

If you're rebuilding images anyway, Microsoft's KB5132061 deployment notes add one more step. When you add dynamic updates to an existing image, make sure the installation media includes a boot.stl that matches the image. Without it, devices may fail to boot from the media with error 0xc0430001. That's worth checking during the same maintenance window as the Defender refresh.

The bottom line​

The headline oversells it, but the update itself is useful. KB4568292 now delivers Defender platform 4.18.26100.4, engine 1.1.26100.4 and security intelligence 1.463.217.0 for offline Windows 11, Windows 10 ESU, LTSC/LTSB and Windows Server 2016–2022 images. If you maintain deployment images, add this to your quarterly servicing routine along with the latest cumulative update, in whichever order suits you. Check the image with -Action ShowUpdate rather than assuming a freshly downloaded ISO already includes it. The new machine won't stay on these definitions for long, since Defender starts updating once it's online, but this keeps it from starting out months behind.

 

References

  1. Microsoft released most updated Defender ever for Windows 11/10 ISO images Neowin 2026-11-18T16:42:01+00:00
  2. November 10, 2026—KB5132061 (OS Builds 26300.9974, 26200.9974 and 26100.9974) | Microsoft Support support.microsoft.com
  3. Microsoft Defender update for Windows operating system installation images | Microsoft Support support.microsoft.com