> 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-osdeploybootprofilepreview.md).

# Update-OSDeployBootProfilePreview

Update the selections and settings of an existing OSDeploy Boot profile.

`Update-OSDeployBootProfilePreview` updates an existing profile without building media. It preserves omitted regional settings and options, while rerunning the shared content selectors, including WinpeStartup Core folders, and wallpaper.

## Requirements

Run the command from an elevated PowerShell 7.6 or later session with write access to the selected profile directory. The exact canonical profile name must identify a directory containing `osdeployboot.json` under `%ProgramData%\OSDeployCore\boot-assets\osdeployboot-profiles`.

A valid Recast Software Community License is required when the command is called directly. The command displays registration guidance and returns when no valid license is available.

## Parameters

| Parameter         | Type             | Default        | Accepted values and behavior                                                                                                 |
| ----------------- | ---------------- | -------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| `-ProfileName`    | `String`         | None           | Required. Specify the exact canonical profile name. Values tab-complete from readable profile directories.                   |
| `-Languages`      | `String[]`       | Existing value | Replace the saved ADK languages. Use `*` for all additional languages during a later build.                                  |
| `-SetAllIntl`     | `String`         | Existing value | Replace the saved WinPE international-settings value.                                                                        |
| `-SetInputLocale` | `String`         | Existing value | Replace the saved WinPE input locale.                                                                                        |
| `-SetTimeZone`    | `String`         | Existing value | Replace the saved timezone with a value accepted by `tzutil /l`.                                                             |
| `-Options`        | `String[]`       | Existing value | Replace saved options with `pwsh`, `dart`, or both.                                                                          |
| `-WhatIf`         | Common parameter | Not enabled    | Validate the license and locate the profile, then report the update without displaying content selectors or modifying files. |
| `-Confirm`        | Common parameter | Not enabled    | Confirm the profile update before initialization and content selection.                                                      |

## Examples

### Reselect shared content

```powershell
Update-OSDeployBootProfilePreview -ProfileName 'Contoso-amd64'
```

Regional settings and options remain unchanged. Shared content selections are replaced.

### Replace saved options

```powershell
Update-OSDeployBootProfilePreview -ProfileName 'Contoso-amd64' -Options 'pwsh'
```

### Preview an update

```powershell
Update-OSDeployBootProfilePreview -ProfileName 'Contoso-amd64' -WhatIf
```

## Selection and Preservation

The profile architecture is read from `osdeployboot.json` and must be `amd64` or `arm64`. The command reselects shared drivers, WinPE scripts, media scripts, WinpeStartup Core folders, WinpeStartup profiles, and wallpaper.

Canceling the driver, script, media-script, WinpeStartup Core, or startup-profile selector clears the corresponding saved value. Canceling wallpaper selection preserves the current profile-root `wallpaper.jpg`.

Omitted `Languages`, `SetAllIntl`, `SetInputLocale`, `SetTimeZone`, and `Options` values are read from the existing profile. Explicit values replace them. Paths beneath OSDeployCore are stored with the portable `${{ OSDeployCore }}` token.

Core initialization can migrate legacy Boot-Assets content and profile paths before the final profile is reloaded. Existing Boot-Assets content takes precedence during general `repository` and `OSDRepo` migration; unresolved conflicts remain at the legacy source with a warning.

## WhatIf and Confirmation

The license check and initial profile lookup occur before `ShouldProcess`. The shared selectors and profile write occur only after the update operation is approved. `-WhatIf` and a declined confirmation do not modify the profile.

## Output

The command writes no object to the pipeline.

Build the updated profile with [Build-OSDeployBoot](/guide/cmdlets/build-osdeployboot.md). See the compact [Update-OSDeployBootProfilePreview command reference](/command-reference/osdeploy/update-osdeploybootprofilepreview.md) for syntax lookup.


---

# 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-osdeploybootprofilepreview.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.