Fix GitHub Desktop Authentication failed or Bad credentials
What to do first
Troubleshoot GitHub Desktop Authentication failed or Bad credentials by following the official decision path while preserving user data.
This is a general troubleshooting guide, not an announcement of a current outage.
Affected products and symptoms
- Product
- GitHub Desktop
- Versions and conditions
- GitHub Desktop for Windows and macOS
- Error codes and identifiers
- Bad credentials · empty token · Repository not found
Symptoms
- Push or clone authentication fails
- Logs show Bad credentials or empty token
Causes and conditions
Reauthenticate in the browser and use logs to distinguish credential failure from repository permission.
Before you start
- Before changes, record and preserve the day’s GitHub Desktop log, remote URL, and browser access result.
- Change one item at a time and record the original symptom after each stage.
Precautions
- Do not bulk-delete unrelated settings or data.
- Exclude personal data and credentials; share only the necessary parts of the day’s GitHub Desktop log, remote URL, and browser access result.
Step-by-step instructions
Open Help > Show Logs in Explorer/Finder and inspect the log for that date.
Repository not found can mean access loss, rename, or deletion rather than damaged credentials.
Bad credentials and empty token justify re-sign-in; repeating it cannot grant permission for Repository not found.
Use File > Options > Accounts on Windows or GitHub Desktop > Settings > Accounts on macOS.
Uncommitted working-tree changes remain, but save work first.
When the browser asks to return to Desktop, verify the legitimate github.com or Enterprise host.
Choose Sign Into and Continue With Browser, then finish GitHub sign-in and 2FA.
GitHub Desktop does not support direct username/password authentication.
For SAML SSO organizations, finish organization authorization in the browser; account login alone may not grant repository access.
Confirm GitHub.com versus Enterprise and open the repository in the browser.
An SSH remote needs a valid key or a change to HTTPS.
Check Repository > Repository settings > Remote. Desktop HTTPS and SSH-form submodules use different authentication paths.
Check the result
- fetch, push a small commit, and confirm Desktop does not prompt again after restart
- Check adjacent basic functions for side effects from the change.
If the problem continues
- ask the owner about Repository not found access, or follow organization key enrollment for SSH publickey errors
- When continuing with a workaround, preserve original files or account data separately.
Scope of this guide
Troubleshooting guide — Troubleshoot GitHub Desktop Authentication failed or Bad credentials by following the official decision path while preserving user data.
Frequently asked questions
Should I enter a PAT as a Desktop password?
Use Continue With Browser for normal Desktop authentication.
Will re-login fix Repository not found?
Not if access was removed or the repository was renamed; contact its owner.
Official sources and dates
Source publication or resolution date: Not specified. Sources checked: 2026-09-05. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.
Related troubleshooting guides
- Safely resolve a merge conflict in GitHub Desktop
- Fix Acrobat “A running instance has caused an error”
- Fix Firefox “already running” or profile-in-use errors
- Identify the source of Chrome “Managed by your organization”
- Fix OneDrive “Can’t open file” or “Make sure OneDrive is running”
- Fix OneDrive error 0x8007016a