> For the complete documentation index, see [llms.txt](https://docs.foundryosd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.foundryosd.com/foundry-osd/settings.md).
# Settings
Settings holds the options of the Foundry OSD application itself: language, appearance, configuration sharing, proxy, telemetry and updates. Open it with **Settings** at the bottom of the navigation pane. The sections below follow the cards of the page from top to bottom.
Configuration sharing on a PC that neither publishes nor follows a folder.
Except for **Configuration sharing**, these choices are stored for the PC, so they apply to every Windows account that uses Foundry OSD on it. The proxy username and password are the exception: they are saved in Windows Credential Manager for your Windows account, so another account must type them again.
## General
| Option | What it does |
| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Language** | Changes the language of Foundry OSD at once. It does not change the language of Windows PE or of the deployed Windows. |
| **Export diagnostics** | Shows the log folder, normally `%ProgramData%\Foundry\Logs`, as a link that opens it. **Export…** asks for a destination and creates an archive of the Foundry OSD logs with sensitive values masked. |
| **Advanced: export raw logs…** | Creates the same archive without masking. Use it only when a support contact asks for it: raw logs can contain credentials, identifiers, paths and network names. |
A dialog titled **Diagnostics exported** gives the path of the archive. What the archive contains is described in [Export diagnostics from Foundry OSD](/troubleshooting/logs-and-support.md#export-from-foundry-osd). It does not include the logs of target devices: for those, see [Logs and support information](/troubleshooting/logs-and-support.md).
## Appearance
| Option | Choices |
| ---------------- | ------------------------------------------------------------------------------- |
| **App theme** | **Light**, **Dark**, **System** |
| **Material** | **Mica**, **Mica Alt**, **Acrylic**, **Acrylic Thin** |
| **Accent color** | **Open** opens the color settings of Windows, where the accent color is chosen. |
## Configuration sharing
A configuration is the set of deployment options you chose in Foundry OSD, with their passwords and files. It belongs to your Windows account. This card exports it to an encrypted file, imports one, publishes it to a folder that other PCs follow, or follows the folder of another PC.
All of it is explained in [Configuration sharing](/foundry-osd/configuration-sharing.md).
## Proxy
Use **Proxy** when the PC reaches the Internet through a proxy. These settings apply to Foundry OSD only: they are not written to the media and do not affect Foundry Connect or Foundry Deploy.
1. Choose a **Proxy method**: **Use Windows settings (recommended)**, **Manual proxy** or **No proxy (direct connection)**.
2. For **Manual proxy** only, fill in:
* **Proxy server**: the address, and the **Port** in its own field (default 8080, from 1 to 65535). An address without `http://` or `https://` is treated as `http://`.
* **Bypass local addresses** (on by default) and **Bypass list**, for hosts to reach directly, separated by semicolons.
* **Authentication**: **Use current Windows credentials**, **No authentication** or **Username and password**. With the last one, **Proxy credentials** asks for **Username**, **Password** and **Domain (optional)**, and stores them in Windows Credential Manager.
3. Select **Test connection**. Foundry OSD tries `github.com`, `login.microsoftonline.com` and `graph.microsoft.com`, for up to 15 seconds each.
4. Select **Apply**.
A successful test proves that these three hosts answer, not that every download will. The full list is in [Network endpoints](/reference/network-endpoints.md).
## Enable telemetry and Enable remote diagnostics
Both switches are on by default.
| Switch | Sends | Takes effect |
| ----------------------------- | ----------------------------------------------- | ----------------------------- |
| **Enable telemetry** | Anonymous usage events | After you restart Foundry OSD |
| **Enable remote diagnostics** | Application logs and error reports, kept 7 days | At once |
The choice is also written to the media you create afterwards. Existing media keeps the choice it was created with. Log files on the PC are written whatever you choose. [Telemetry and privacy](/reference/telemetry-and-privacy.md) lists what is sent.
## Update app
Foundry OSD updates itself from the releases of the `foundry-osd/foundry` repository on GitHub. You do not need to download the MSI again.
1. At each start, Foundry OSD checks for a newer release and downloads it in the background.
2. While an update is known, an **Update** item appears at the bottom of the navigation pane. It reads **Downloading: N%**, then **Apply update**.
3. Select **Apply update** to install the update and restart Foundry OSD. If you do nothing, the update is installed when you close the app, which then stays closed.
The **Update app** page shows **Installed version**, the available or latest version, **Last checked** and the **Update source**. **Check for updates** checks at once, **Download update** and **Apply update** do each step by hand, and **Release notes** appears when an update is available.
The installed version, the latest available one and when Foundry OSD last checked.
If you start a media creation while an update is known, a dialog titled **Update Foundry OSD before creating boot media** offers **Apply update** (or **View update** while it is still downloading), **Create anyway** and **Cancel**. Applying first is the safe choice: the media then carries the latest fixes.
Existing media keep running the Foundry applications of the version that created them. After an update, recreate the ISO or the PXE files, or [update the USB drive](/foundry-osd/media/update-usb.md), to give them the new version.
An update is not installed on closing while a second Foundry OSD window is open. See [The update stays on "Apply update"](/troubleshooting/foundry-osd.md#update-stays).
## Related
* [Configuration sharing](/foundry-osd/configuration-sharing.md)
* [Telemetry and privacy](/reference/telemetry-and-privacy.md)
* [Network endpoints](/reference/network-endpoints.md)
* [Foundry OSD application troubleshooting](/troubleshooting/foundry-osd.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://docs.foundryosd.com/foundry-osd/settings.md?ask=&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.
