> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/troubleshooting-and-faq/troubleshooting/package-installation-issues.md).
# Package Installation Issues
Troubleshooting Guide for failed software package installations
This guide will focus on troubleshooting failed RealmJoin software package installations.
{% hint style="info" %}
This guide is only valid for software deployment using the RealmJoin client (not intunewin).
Especially the convenient way of collecting the required logfiles, directly on the client as well as remotely using the RealmJoin portal, only works with the RealmJoin tray application rolled out to your clients.
When using intunewin deployment, the logfiles will need to be collected manually from the clients, the most relevant folder being `C:\WINDOWS\Logs\RealmJoin`.
{% endhint %}
## Required log files
Without log files a failed software package installation cannot be properly troubleshooted.\
The required log files needed for troubleshooting failed installations reside in several location on the local client:
* `C:\WINDOWS\Logs\realmjoin*.log`
* `C:\WINDOWS\Logs\RealmJoin`
* `%LOCALAPPDATA%\RealmJoin\tray*.log`
* `%LOCALAPPDATA%\RealmJoin\Logs`
* `C:\ProgramData\chocolatey\logs\`
{% hint style="warning" %}
**Please always provide the ZIP file containing the logs with any service request raised to the RealmJoin support.**
{% endhint %}
File structure of a RealmJoin exported logs ZIP file
\
The following chapters will explain how to obtain the logs, how to analyze them, and will explain some common issues and fixes for these common issues.
---
# 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.realmjoin.com/troubleshooting-and-faq/troubleshooting/package-installation-issues.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.
