Starting with Windows ADK 10.1.26100.2454 (December 2024), Microsoft now publishes ADK patches for both feature updates and bug fixes. Rather than a full uninstall/install, you can simply apply a patch file to your existing setup and keep it updated. When updates are issued, Microsoft releases them on the Windows ADK Servicing Updates page.
Downloading and Installing the Windows ADK Patches
As of August 2025, there has been only one update package, targeting the App-V Sequencer component. But Microsoft may release more updates.
Note #1: Avoid the sample Batch script provided on the Windows ADK Servicing Updates page; it has zero error handling/filtering, and, well, it's a Batch script, which should be avoided in general 🙂
Note #2: The Windows ADK updates will fail unless the original feature/component is installed. I added some logic in the PowerShell script below to detect that.
To install the current update package, download the ZIP file from https://aka.ms/WindowsADK10.1.26100.2454UpdateKB5053656.zip and then run the following PowerShell script:
# This script will install the ADK updates for Windows ADK for Windows 11 24H2 (December 2024)
# In this example, the updates were downloaded to C:\Temp and update logs created in C:\Temp\adkupdatelogs
# Update the temp folder location to match your environment
$TempFolder = "C:\Temp"
$ADKUpdateZIP = "$TempFolder\Windows ADK 10.1.26100.2454 Update KB5053656.zip"
$Architecture = $env:PROCESSOR_ARCHITECTURE
# Extract the package
$ADKupdatePath = New-Item -Path "$TempFolder\adkupdate" -ItemType Directory -Force
Expand-Archive -Path $ADKUpdateZIP -DestinationPath $ADKupdatePath -Force
# Install the updates (filter on Architecture)
$ADKUpdateLogsPath = New-Item -Path "$TempFolder\adkupdatelogs" -ItemType Directory -Force
$MSPFiles = Get-ChildItem -Path $ADKupdatePath -Filter *.msp | Where-Object { $_.Name -like "*$Architecture*" }
foreach ($File in $MSPFiles) {
$log = "$ADKUpdateLogsPath\$($File.BaseName)$($File.Extension).log"
$Result = Start-Process msiexec.exe -ArgumentList "/l* `"$log`" /qn /p `"$($File.FullName)`"" -Wait -PassThru
If ($Result.ExitCode -eq 0){
Write-Host "Installation successful"
}
Else {
Write-Warning "Installation failed with exit code: $($Result.ExitCode)"
If ($Result.ExitCode -eq 1642){
Write-Host "NOTE: Exit code 1642 means the system does not have the software installed that you are trying to update" -ForegroundColor Yellow
}
}
}
Thanks for this the MS Batch File is bad and the documentation worse 🙁
Suspect AI strikes again 🙁
Thanks, I'm not sure why they are still releasing batch files…
there is an new adk version 26200.6584:
Hi Avi,
Thanks for sharing. This seems to be an ADK version targeted for Windows 11 25H2 (hence the same version number as the RTM), but I have not yet seen any official communication about this version. Usually, Microsoft doesn't release a new version when the servicing stack is the same, which is the case between Windows 11 24H2 and Windows 11 25H2. Do you know what's updated in this version compared to 26100.2454?
sorry i dont
i just saw a few days ago a new version of adk for the upcoming 26H1:
Thanks for the update! I haven't had a chance to test that one yet, but I noticed it was added to the main ADK download page too: https://learn.microsoft.com/en-us/windows-hardware/get-started/adk-install
Thanks Johan. Appreciated 🙂