Save-DbaKbUpdate

Want to see the source code for this command? Check out Save-DbaKbUpdate on GitHub.
Want to see the Bill Of Health for this command? Check out Save-DbaKbUpdate.

Synopsis

Downloads Microsoft Knowledge Base updates and patches to local storage

Description

Downloads Microsoft KB updates, cumulative updates, and service packs from Microsoft's servers to your local file system. This function handles SQL Server patches as well as any other Microsoft KB updates, making it easy to stage patches for installation across multiple servers. Supports filtering by architecture (x86, x64, ia64) and language, and can download multiple KBs in a single operation. Use this to build a local patch repository or download specific updates for offline installation scenarios.

Syntax

Save-DbaKbUpdate
    [[-Name] <String[]>]
    [[-Path] <String>]
    [[-FilePath] <String>]
    [[-Architecture] <String>]
    [[-Language] <String>]
    [[-InputObject] <Object[]>]
    [-EnableException]
    [<CommonParameters>]

Examples

Example: 1

PS C:\> Save-DbaKbUpdate -Name KB4057119

Downloads KB4057119 to the current directory. This works for SQL Server or any other KB.

Example: 2

PS C:\> Get-DbaKbUpdate -Name KB4057119 -Simple | Out-GridView -Passthru | Save-DbaKbUpdate

Downloads the selected files from KB4057119 to the current directory.

Example: 3

PS C:\> Save-DbaKbUpdate -Name KB4057119, 4057114 -Path C:\temp

Downloads KB4057119 and the x64 version of KB4057114 to C:\temp. This works for SQL Server or any other KB.

Example: 4

PS C:\> Save-DbaKbUpdate -Name KB4057114 -Architecture All -Path C:\temp

Downloads the x64 version of KB4057114 and the x86 version of KB4057114 to C:\temp. This works for SQL Server or any other KB.

Example: 5

PS C:\> Save-DbaKbUpdate -Name KB5003279 -Language enu -Path C:\temp

Downloads only the english version of KB5003279, which is the Service Pack 3 for SQL Server 2016, to C:\temp.

Optional Parameters

-Name

Specifies the Microsoft Knowledge Base article number to download. Accepts KB prefix or just the numeric value (e.g., 'KB4057119' or '4057119').
Use this to target specific patches, cumulative updates, or service packs for SQL Server or other Microsoft products.
Supports multiple KB numbers in a single command for batch downloading.

-Path

Specifies the directory where downloaded KB files will be saved. Defaults to the current working directory.
Use this to organize patches into specific folders or network locations for easier deployment across multiple servers.
The directory will be created if it doesn't exist.

-FilePath

Specifies the exact filename and path for the downloaded file, overriding the server-provided filename.
Use this when you need custom naming conventions or want to save to a specific location with a particular name.
Cannot be used when downloading multiple KBs or when Architecture is set to 'All'.

-Architecture

Specifies the CPU architecture for the downloaded files. Valid values are 'x64', 'x86', 'ia64', or 'All'.
Use 'All' to download files for all available architectures when you need to support mixed environments.
Most modern SQL Server deployments use 'x64', which is the default.

-Language

Filters downloads to a specific language version using three-letter language codes (e.g., 'enu' for English, 'deu' for German).
Primarily useful for SQL Server Service Packs which have separate files per language, unlike Cumulative Updates which are language-neutral.
Only downloads files matching the specified language code when multiple language versions are available.

-InputObject

Accepts pipeline input from Get-DbaKbUpdate, allowing you to filter and select specific files before downloading.
Use this workflow to preview available downloads with Get-DbaKbUpdate, then pipe selected results for download.
Particularly useful when working with KBs that have multiple file options.

-EnableException

By default, when something goes wrong we try to catch it, interpret it and give you a friendly warning message.
This avoids overwhelming you with "sea of red" exceptions, but is inconvenient because it basically disables advanced scripting.
Using this switch turns this "nice by default" feature off and enables you to catch exceptions with your own try/catch.