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

# Delete-OSDeployBootProfilePreview

Delete an OSDeploy Boot profile and its profile-local content.

`Delete-OSDeployBootProfilePreview` deletes an existing profile directory and every profile-local file beneath it. It does not remove generated boot media, shared Boot-Assets content, or cached content.

## Requirements

Run the command from a PowerShell session with permission to remove the selected profile directory. The exact canonical profile name must identify a directory containing `osdeployboot.json` under `%ProgramData%\OSDeployCore\boot-assets\osdeployboot-profiles`.

The command does not use the shared OSDeploy license gate.

## 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. |
| `-Force`       | `Switch`         | Not enabled | Required to enable deletion. Without it, the command warns and makes no change.                            |
| `-WhatIf`      | Common parameter | Not enabled | With `-Force`, report the recursive profile-directory deletion without removing content.                   |
| `-Confirm`     | Common parameter | Not enabled | With `-Force`, confirm recursive deletion.                                                                 |

## Examples

### Check the force requirement

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

The command locates the profile, warns that `-Force` is required, and leaves it unchanged.

### Delete a profile

```powershell
Delete-OSDeployBootProfilePreview -ProfileName 'Contoso-amd64' -Force
```

### Preview recursive deletion

```powershell
Delete-OSDeployBootProfilePreview -ProfileName 'Contoso-amd64' -Force -WhatIf
```

## Deletion Boundary

Profile lookup occurs before the `-Force` check and before `ShouldProcess`. When `-Force` is present and the operation is approved, the command removes the entire profile directory recursively.

{% hint style="danger" %}
Profile deletion cannot be undone by this command. Review profile-local scripts, drivers, startup content, and wallpaper before approving deletion.
{% endhint %}

Generated content under `%ProgramData%\OSDeployCore\boot`, shared content elsewhere under `boot-assets`, and content under `cache` are not removed.

## Output

The command writes no object to the pipeline.

Create another profile with [New-OSDeployBootProfilePreview](/guide/cmdlets/new-osdeploybootprofilepreview.md), or see the compact [Delete-OSDeployBootProfilePreview command reference](/command-reference/osdeploy/delete-osdeploybootprofilepreview.md).


---

# 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/delete-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.