> 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/troubleshooting/logs-and-support.md).

# Logs and support information

Collect evidence before rebooting, recreating media, or starting another deployment.

## Information to record

* Foundry application and media version.
* Device manufacturer and model.
* Current application: Foundry OSD, Foundry Connect, or Foundry Deploy.
* Current or failed workflow stage.
* Complete error message.
* Network state and connection type.
* Selected Windows release, edition, language, and architecture.
* Selected driver pack.
* Autopilot method, without credentials or tenant secrets.

## Windows PE log location

Foundry Connect and Foundry Deploy initially write logs under:

```
X:\Foundry\Logs
```

## Applied Windows log location

After Foundry prepares the target Windows installation, deployment logs are rebound to:

```
<target-drive>:\Windows\Temp\Foundry\Logs
```

After the deployed operating system starts, this is normally:

```
C:\Windows\Temp\Foundry\Logs
```

Relevant subdirectories include:

```
PreOobe
AutopilotHash
AutopilotRegistration
```

If the first-boot runner does not start, also collect:

```
C:\Windows\Panther\UnattendGC\Setupact.log
```

{% hint style="warning" %}
Review collected files before sharing them. Remove credentials, tokens, certificates, hardware hashes, tenant identifiers, network secrets, and other sensitive information.
{% endhint %}

## Open a support issue

Provide reproduction steps, expected result, actual result, failed stage, sanitized logs, and whether the problem reproduces on newly created media.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.foundryosd.com/troubleshooting/logs-and-support.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.