Report issues
On this page
This page is for testers and contributors who report bugs in Atlas, Atlas Manager or a test build. It covers what makes a report useful and where to send it.
Collecting diagnostics
Report a problem explains how to send a report privately from Atlas Manager and how to export diagnostics for a public bug report.
Keep the evidence
Export diagnostics before you retry, clear app data or reinstall Windows. Export them as the affected Windows account, because other accounts’ files aren’t collected.
Check unmodified Windows
For a suspected Atlas bug, check whether the same problem happens on unmodified Windows in the same environment. Use a separate PC or virtual machine, so you don’t discard the evidence from the affected installation.
What to include
- The Atlas version, the Atlas Manager version, and the Windows version and build.
- The exact release or test build you used, with the SHA-256 hashes from its release notes if it lists them.
- What you were doing, what you expected and what happened instead.
- The exact error message, roughly when it happened (with your time zone), and whether it happens again.
- Steps to reproduce it, including your choices, your driver choice and whether other accounts use the PC.
- The diagnostics ZIP, and screenshots where they help.
Review the ZIP before you post it publicly. Atlas removes your user name, PC name, email addresses and known passwords or keys, but keeps error details, hardware models and app names.
Where to report
Open an Atlas GitHub issue and complete the issue template. For a test build, use the reporting channel named in its release notes.
For questions about setting up Atlas, use GitHub Discussions or the Atlas Discord community.