> For the complete documentation index, see [llms.txt](https://www.osdeploy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.osdeploy.com/guide/cmdlets/update-osdeploycorecatalogos.md).

# Update-OSDeployCoreCatalogOS

Acquire, validate, publish, and cache the current Windows 11 operating system catalog.

`Update-OSDeployCoreCatalogOS` downloads the current Windows 11 products catalog from Microsoft, validates it, publishes it in the OSDeploy module, and synchronizes the OSDeploy Core catalog cache.

## Requirements

Run the command from an elevated PowerShell 7.6 or later session on Windows 11 25H2 build 26200 or Windows 11 26H2 build 26300. Install ADK `10.1.26100.2454` or `10.1.26100.9457`. Internet access, `expand.exe`, writable temporary storage, and write access to the module and Core cache are also required.

The host build and installed ADK limit the catalog release. ADK `10.1.26100.2454` selects Windows 11 25H2; ADK `10.1.26100.9457` selects Windows 11 26H2 only when the host is also 26H2. Unsupported Windows or ADK versions stop the command before its Microsoft request.

## Parameters

| Parameter           | Type             | Default     | Accepted values and behavior                                                                              |
| ------------------- | ---------------- | ----------- | --------------------------------------------------------------------------------------------------------- |
| `-MinimumItemCount` | `Int32`          | `50`        | Accepts `1` through `100000`. Rejects a catalog with fewer ESD records.                                   |
| `-WhatIf`           | Common parameter | Not enabled | Still acquires, extracts, and validates the catalog; previews only publication and cache synchronization. |
| `-Confirm`          | Common parameter | Not enabled | Prompts before publication and cache synchronization.                                                     |

## Examples

### Update the catalog

```powershell
Update-OSDeployCoreCatalogOS
```

### Validate without publishing

```powershell
Update-OSDeployCoreCatalogOS -WhatIf
```

## Validation and Output

The command verifies the Microsoft CAB size and SHA256 digest, validates required catalog properties, and requires en-US Enterprise x64 and ARM64 records. It names the catalog from the embedded build and release identity, such as `26300.9457.260913-1737.xml`.

After successful validation, it returns a `System.Management.Automation.PSCustomObject` with `Build`, `ModuleCatalogPath`, `CacheCatalogPath`, `Published`, `Cached`, `ItemCount`, and `Sha256`. Failures produce warnings and no object.

Continue with [Update-OSDeployCoreESD](/guide/cmdlets/update-osdeploycoreesd.md), or run [Update-OSDeployCore](/guide/cmdlets/update-osdeploycore.md) for the complete refresh.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.osdeploy.com/guide/cmdlets/update-osdeploycorecatalogos.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.