
Most AnyDesk problems come from a handful of causes: a blocked download, a firewall, missing permissions or a device that has gone to sleep. Work through the sections below in order. Each one starts with the quickest check.
The installer won't open
- Check that the download finished. A partly downloaded
AnyDesk.exewon't run. Download it again from our download section. - Check quarantine. Antivirus software may have moved the file. If the file's digital signature shows AnyDesk Software GmbH, you can restore it and allow it.
- SmartScreen or Smart App Control. On Windows 10 and 11, inspect the file source and signature before proceeding. Keep security protections enabled and ask your administrator to review managed restrictions.
- Older Windows. Unpatched Windows 7 systems may not validate modern signatures. Check the system clock and available updates without disabling signature verification.
The connection doesn't start
- Check that both devices are online and AnyDesk is open on the remote side, or installed with unattended access.
- Check the address. A single wrong digit connects to nobody, or to the wrong device.
- Check firewalls and proxies. The developer's firewall documentation lists the network ports and addresses AnyDesk uses. On company networks, ask your administrator to allow them.
- Restart AnyDesk on both sides, then try again.
The request is never accepted
Someone must be at the remote device to choose Accept, unless unattended access is set up. If you're trying to reach your own PC, check that AnyDesk is installed (not just running as a portable program) and that unattended access is turned on with a password.
Connected, but the screen is black or frozen
- The remote device is asleep or the display is off. Wake it, or change its power settings so it stays awake while plugged in.
- Mac permissions. On macOS, AnyDesk needs Screen Recording permission.
- Display drivers. Updating the remote PC's graphics driver can help with capture problems.
I can see the screen but can't control it
- The person at the remote device may have turned off keyboard and mouse permission in the request window. Ask them to allow it.
- If a Windows administrator prompt (User Account Control) is open, a portable copy of AnyDesk can't interact with it. Install AnyDesk on the remote PC.
- On a Mac, check the Accessibility permission.
- On iPhone and iPad, remote control isn't supported because of Apple's restrictions. You can view, but not control.
The session is slow or choppy
- Choose a setting that favours speed over image quality in the session display settings.
- Lower the remote screen resolution or switch off visual effects.
- Close downloads, streaming or video calls that use bandwidth.
- Use a wired connection if Wi-Fi is weak.
"Commercial use detected"
The free version of AnyDesk is for personal, non-commercial use. If AnyDesk thinks your usage pattern is commercial, it may limit sessions. If you use AnyDesk for work, a commercial licence is the right fix. If your use really is personal, the developer offers a way to request a review.
After an update something changed
Updates can reset permissions, especially on macOS. Check the system permissions again, restart AnyDesk and reconnect. Keeping AnyDesk up to date is still important for security.
Describe the failure before changing settings
Write down what happens and when it happens. Does the installer fail to open, does the application stay offline, or does a session connect without showing a usable desktop? Record the exact message and identify which device displays it. Note whether the issue began after an application update, a network change or a computer restart. These details help separate unrelated symptoms and prevent you from applying a fix intended for a different stage of the connection.
Try one change at a time and repeat the same short test after each change. If you restart the application, change permissions and switch networks together, you may restore access without learning which adjustment mattered. Save any important work before restarting the remote device. Do not make changes to network adapters, security software or system services unless you understand how to recover if the connection disappears. Keep somebody near the remote computer for changes that could cut off access.
Compare the two ends of the connection
Ask the other person what they see locally. A frozen application on the remote desktop may also be frozen for the person sitting at that computer. If the local screen works normally but the remote image does not update, focus on capture, permissions and connectivity. Test ordinary internet use on both devices, then check whether other large transfers are consuming bandwidth. A good connection at your own computer does not establish that the remote side is equally stable.
If permitted, compare a wired connection with Wi-Fi or test another trusted network. Treat the result as evidence rather than a permanent instruction to weaken firewall protection. On managed networks, give the administrator the application name and observed error. Avoid opening broad network access simply because a session failed once. A useful diagnosis identifies which component is blocking or interrupting the connection and changes only the configuration needed for the authorised support workflow.
Separate display problems from input restrictions
A visible desktop with an unresponsive pointer suggests a different issue from a blank screen. Confirm the keyboard and mouse permission first, then check whether a protected system prompt is open. On a Mac, review the relevant privacy approval locally. If the remote computer has several monitors, make sure you are viewing the active display. Ask the owner before changing display settings, and use a harmless application to test typing and clicking.
For a black screen, check whether the computer is awake and whether the display is available locally. Graphics drivers, hardware configuration and application permissions can affect capture. Do not assume that every blank screen means the machine is locked or that reinstalling AnyDesk will necessarily fix it. Read any accompanying error and test the simplest explanation first. If the problem remains, keep a record of what the remote user sees compared with what appears in your session window.
Collect the information a support technician needs
Prepare the operating system version, application version, approximate failure time and steps that reproduce the issue. State whether it affects one remote device or several. Screenshots can help, but hide passwords, personal documents and unrelated identifiers before sharing them. Diagnostic files can contain device or connection details, so send them only through an authorised support process. A clear description is often more useful than a long list of settings changed without a record.
If a temporary adjustment restores access, document it and review whether it should remain. Return unnecessary display or permission changes to their previous state. Test the original task, not merely whether the application opens. For regular unattended access, check a planned reconnect while local help is available. This final test closes the troubleshooting loop and reduces the chance that the same problem returns as soon as you leave the remote computer.
Conclusion
Effective AnyDesk troubleshooting starts by identifying the failing stage and comparing what happens on both devices. Check simple causes first, change one thing at a time and keep a recovery option available. Treat network, display and input issues separately instead of repeatedly reinstalling the application. If you need further assistance, provide the exact error and the tests already completed. A careful record makes diagnosis faster and helps you keep only the changes that actually solve the problem.