> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/troubleshooting-articles/black-screen-with-an-ard-session.md).

# Black screen with an ARD session

Diagnose a black screen in an Apple Remote Desktop session by enabling ARD logging on macOS to capture details for support.

You get a black screen appear after connecting with an Apple Remote Desktop session entry.

### Solution

Activating logging on the mac may help our customer support team or the engineering department resolving this issue. To activate the logging server side, execute the following command in Terminal:

***sudo defaults write /Library/Preferences/com.apple.RemoteManagement ARDCollectLogs -bool YES***.

Once this is done, you can try to connect normally using Remote Dekstop Manager. The log will then be located in ***/tmp*** folder on the Mac computer. Simply send them to <service@devolutions.net> with details of your issue.

To turn off logging, execute this command:

***sudo defaults write /Library/Preferences/com.apple.RemoteManagement ARDCollectLogs -bool NOTBD***


---

# 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.devolutions.net/rdm/knowledge-base/troubleshooting-articles/black-screen-with-an-ard-session.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.
