How to Fix ADB Not Recognized in Windows 11

ADB (Android Debug Bridge) is an essential command-line tool used by developers and advanced users to communicate with Android devices for debugging, file transfer, app installation, and system-level operations. On Windows 11, some users encounter the “adb is not recognized as an internal or external command” error when running ADB commands in Command Prompt or PowerShell.

This issue usually occurs because ADB is not installed correctly, the platform-tools folder is missing from the system PATH, USB drivers are not configured properly, or the command is being run from the wrong directory. In most cases, ADB itself works fine, but Windows cannot locate it.

Fixing ADB not recognized in Windows 11 involves installing the correct tools, configuring environment variables, and verifying device and driver setup. The steps below explain how to resolve the issue completely.

How to Fix ADB Not Recognized in Windows 11

The methods in this section focus on properly installing ADB, setting up environment variables, and confirming USB and command-line configuration. Follow the steps in order and test ADB after each method.

1. Download and Install Android Platform Tools

ADB is included with Android platform tools.

1. Download Android SDK Platform Tools from the official Android developer website.
2. Extract the ZIP file to a permanent location such as C:\platform-tools.
3. Open the extracted folder.
4. Confirm that adb.exe exists inside the folder.

ADB will not work unless platform tools are installed.

2. Run ADB from the Platform-Tools Folder

Testing ADB locally helps confirm installation.

1. Open the platform-tools folder.
2. Click the address bar.
3. Type cmd and press Enter.
4. In the Command Prompt window, type adb devices.
5. Press Enter.

If ADB responds, the tool is installed correctly.

3. Add ADB to System PATH Environment Variable

This allows ADB to run from any directory.

1. Press Windows + S and search for Environment Variables.
2. Select Edit the system environment variables.
3. Click Environment Variables.
4. Under System variables, select Path.
5. Click Edit.
6. Click New.
7. Add the full path to the platform-tools folder.
8. Click OK to save changes.
9. Restart the computer.

After this, Windows can recognize ADB globally.

4. Restart Command Prompt or PowerShell

Environment changes require a restart.

1. Close all open Command Prompt or PowerShell windows.
2. Open a new Command Prompt.
3. Run adb version or adb devices.

ADB should now be recognized.

5. Enable USB Debugging on the Android Device

ADB requires USB debugging permission.

1. Open Settings on the Android device.
2. Go to About phone.
3. Tap Build number seven times to enable Developer Options.
4. Go back to Developer options.
5. Enable USB debugging.
6. Connect the device to the PC using a USB cable.
7. Allow the USB debugging prompt on the device.

Without this, ADB cannot detect devices.

6. Install or Update USB Drivers

Missing drivers can block ADB detection.

1. Connect the Android device to the PC.
2. Open Device Manager.
3. Look for unknown or Android-related devices.
4. Install the correct USB driver for your device brand.
5. Restart the system.

Proper drivers ensure device communication.

7. Check ADB Command Spelling and Terminal Type

Incorrect commands can trigger errors.

1. Ensure you are typing adb, not abd.
2. Use Command Prompt or Windows Terminal.
3. Avoid restricted shells without PATH access.

Simple mistakes can cause recognition errors.

8. Use PowerShell with Correct Syntax

PowerShell may require a different command format.

1. Open PowerShell.
2. Navigate to the platform-tools folder.
3. Run .\adb devices.

This ensures PowerShell executes the local binary.

9. Disable Conflicting ADB Installations

Multiple ADB versions can cause conflicts.

1. Search for existing ADB installations on the system.
2. Remove outdated or conflicting ADB folders.
3. Keep only one platform-tools installation.
4. Update PATH to point to the correct folder.

Conflicts can prevent Windows from detecting ADB properly.

10. Restart ADB Server

Restarting the server can fix detection issues.

1. Open Command Prompt.
2. Run adb kill-server.
3. Then run adb start-server.
4. Run adb devices again.

This refreshes the ADB service.

Final Thoughts

The ADB not recognized error in Windows 11 is almost always caused by missing platform tools or incorrect PATH configuration rather than a problem with ADB itself. Once platform-tools are installed correctly and added to the system PATH, ADB works reliably across Command Prompt and PowerShell.