How to Fix “adb is not recognized as an internal or external command” on Windows

The error “‘adb’ is not recognized as an internal or external command, operable program or batch file” occurs when you try to run the adb (Android Debug Bridge) command in Windows Command Prompt or PowerShell, but the system cannot find the adb executable. This typically happens because the Android SDK Platform Tools (which includes adb) is either not installed or not properly configured in your system’s PATH environment variable. Below is a comprehensive guide to fixing this issue on Windows 10 or 11, based on the latest available information as of August 15, 2025, and tailored for both beginners and advanced users.

Prerequisites

• Operating System: Windows 10 or 11 (64-bit recommended).
• Permissions: Administrative privileges for modifying environment variables.
• Internet Connection: Required to download SDK Platform Tools.
• Optional: An Android device with USB debugging enabled for testing.

Step-by-Step Fix

Step 1: Verify ADB Installation

The adb command is part of the Android SDK Platform Tools. If it’s not installed, you’ll need to download it.

1. Check if ADB is Installed:

• Open Command Prompt or PowerShell and type:
  cmd adb --version
• If you see version information (e.g., “Android Debug Bridge version 1.0.41”), ADB is installed but not configured correctly. Proceed to Step 3.
• If you get the “not recognized” error, proceed to download ADB.

1. Download Android SDK Platform Tools:

• Visit the official Android developer site: https://developer.android.com/studio/releases/platform-tools.
• Under “Downloads,” click Download SDK Platform-Tools for Windows to get the latest platform-tools_rXX.X.X-windows.zip (e.g., version 35.0.2 as of 2025).
• Save the ZIP file to a convenient location (e.g., C:\Downloads).

1. Extract the Platform Tools:

• Right-click the downloaded ZIP file and select Extract All.
• Choose a destination folder, e.g., C:\platform-tools. This creates a platform-tools folder containing adb.exe and other tools.
• Alternatively, use tools like WinRAR or 7-Zip for extraction.

Step 2: Run ADB from the Platform Tools Folder (Temporary Fix)

If you only need a quick fix without modifying system settings:

1. Open File Explorer and navigate to the extracted platform-tools folder (e.g., C:\platform-tools).
2. Hold Shift, right-click inside the folder, and select Open in Terminal (or Open PowerShell window here).
3. In the terminal, type:

   adb devices

4. If ADB is installed correctly, this should list connected devices or start the ADB server.

Note: For PowerShell, you may need to use:

.\adb devices

This method works only when running commands from the platform-tools folder. For a permanent fix, proceed to Step 3.

Step 3: Add ADB to System PATH (Permanent Fix)

To run adb from any directory in Command Prompt or PowerShell, add the platform-tools folder to your system’s PATH environment variable.

1. Locate the Platform Tools Path:

• Note the full path to the platform-tools folder, e.g., C:\platform-tools.

1. Open Environment Variables Settings:

• Press Windows + R, type sysdm.cpl, and press Enter to open System Properties.
• Go to the Advanced tab and click Environment Variables.

1. Edit the PATH Variable:

• In the System variables section (preferred for all users) or User variables (for your account only), find and select Path, then click Edit.
• Click New and paste the full path to the platform-tools folder (e.g., C:\platform-tools).
• Click OK to close all dialogs.

1. Verify the PATH Update:

• Open a new Command Prompt or PowerShell window (close any open ones first).
• Type:
  cmd echo %PATH%
• Confirm the platform-tools path is listed.

1. Test ADB:

• In the new terminal, run:
  cmd adb --version
• You should see output like:
  Android Debug Bridge version 1.0.41 Version 35.0.2-2025 Installed as C:\platform-tools\adb.exe
• Run:
  cmd adb devices
• If an Android device is connected with USB debugging enabled, it should list the device (e.g., device12345678 device).

Step 4: Enable USB Debugging (If No Devices Appear)

If adb devices shows no devices despite fixing the PATH:

1. On your Android device:

• Go to Settings > About phone > Software information.
• Tap Build number 7 times to enable Developer Mode.
• Go back to Settings > Developer options and enable USB debugging.

1. Connect the device via USB (use a data-capable cable, not charge-only).
2. On your PC, run:

   adb devices

4. On the device, allow USB debugging when prompted.

Step 5: Install USB Drivers (If Needed)

Some Android devices require specific USB drivers for ADB to recognize them:

• Visit your device manufacturer’s website (e.g., Samsung, Xiaomi) to download USB drivers.
• Install the drivers and reconnect the device.
• Alternatively, download Google’s USB driver:
• From the Android SDK Platform Tools page, find the driver link or use Android Studio’s SDK Manager.
• Test again with adb devices.

Step 6: Troubleshooting Additional Issues

• Error Persists:
• Verify the platform-tools folder contains adb.exe. If missing, re-download from the official site.
• Ensure the PATH entry is correct (no typos or extra slashes).
• Run Command Prompt as Administrator:
  cmd adb devices
• Device Offline or Unauthorized:
• Re-enable USB debugging on the device.
• Revoke USB debugging authorizations in Developer options and reconnect.
• Try a different USB port or cable.
• ADB Server Issues:
• Restart the ADB server:
  cmd adb kill-server adb start-server
• Antivirus/Firewall Blocking:
• Temporarily disable antivirus or add an exception for adb.exe.
• Ensure TCP port 5037 (used by ADB) is open:
  cmd netstat -a | find "5037"
• PowerShell Syntax:
• In PowerShell, prepend .\ to commands (e.g., .\adb devices).

Step 7: Verify with Android Studio (Optional)

If you use Android Studio:

1. Open File > Settings > Appearance & Behavior > System Settings > Android SDK.
2. Go to the SDK Tools tab and ensure Android SDK Platform-Tools is checked.
3. Note the SDK location (e.g., C:\Users\YourUser\AppData\Local\Android\Sdk).
4. Add the platform-tools subfolder (e.g., C:\Users\YourUser\AppData\Local\Android\Sdk\platform-tools) to PATH as in Step 3.
5. Test adb devices from a terminal.

Step 8: Post-Fix Actions

• Restart Your PC: Ensures PATH changes take effect across all sessions.
• Test Connectivity: Connect your Android device and run:

  adb devices

Expected output: a list of connected devices.

• Common ADB Commands:
• Install an APK: adb install app.apk
• Pull a file: adb pull /sdcard/file.txt
• Access shell: adb shell

Common Pitfalls and Tips

• Case Sensitivity: Ensure the PATH entry matches the exact folder path.
• Old SDK Versions: Avoid outdated Platform Tools; always download the latest from the official site.
• Multiple ADB Instances: Ensure only one ADB server runs (adb kill-server if issues persist).
• Windows Environment Limits: If PATH is too long, prioritize platform-tools or use a shorter path like C:\platform-tools.
• Security: Avoid running adb from untrusted sources; use only Google’s official binaries.

Conclusion

The “adb is not recognized” error is typically resolved by installing Android SDK Platform Tools and adding the platform-tools folder to your system’s PATH. By following the steps above—downloading the tools, configuring PATH, enabling USB debugging, and installing drivers—you can ensure adb works seamlessly. For persistent issues, check Stack Overflow or the Android developer forums. Always use the official source (developer.android.com) to avoid corrupted downloads.

Comprehensive Guide to the net use Command in Windows

The net use command is a powerful Windows command-line tool used to manage network connections, such as mapping network drives, connecting to shared resources (like folders or printers), and managing user credentials for network access. It is commonly used in Windows environments to automate or manually configure access to network resources. This guide provides a comprehensive overview of the net use command, including its syntax, options, practical examples, and troubleshooting tips, tailored for both beginners and advanced users as of August 15, 2025.

What is the net use Command?

The net use command is part of the Windows Command Prompt (cmd.exe) and PowerShell, allowing users to:

• Connect to or disconnect from shared network resources (e.g., drives, printers).
• Map network shares to local drive letters for easy access.
• Manage authentication credentials for accessing network resources.
• View active network connections.

It is widely used in enterprise environments for scripting, automation, and managing file shares on Windows Server or client machines.

Prerequisites

• Operating System: Windows (e.g., Windows 10, 11, Windows Server 2019, 2022).
• Permissions: Administrative privileges may be required for certain operations (e.g., connecting to restricted shares).
• Network Access: Access to a network share (e.g., SMB share on a server) and valid credentials if required.
• Command Prompt or PowerShell: Run net use in either Command Prompt or PowerShell with appropriate permissions.

Syntax of the net use Command

The general syntax of the net use command is:

net use [devicename | *] [\\computername\sharename[\volume]] [password | *] [/user:[domainname\]username] [/user:[dotted domain name\]username] [/user:[username@dotted domain name] [/savecred] [/smartcard] [{/delete | /persistent:{yes | no}}]

Key Components

• devicename: The local drive letter (e.g., Z:) or printer port (e.g., LPT1:) to assign to the network resource. Use * to automatically assign the next available drive letter.
• \\computername\sharename: The UNC path to the network resource (e.g., \\Server1\SharedFolder).
• [password | *]: The password for the user account. Use * to prompt for the password interactively.
• /user:[domainname\]username: Specifies the username and domain (if applicable) for authentication (e.g., /user:MYDOMAIN\user1).
• /savecred: Stores the provided credentials for future use (not recommended for security reasons unless necessary).
• /smartcard: Uses smart card credentials for authentication.
• /delete: Disconnects the specified network connection.
• /persistent:{yes | no}: Controls whether the connection persists after a reboot (yes makes it permanent, no makes it temporary).
• volume: Specifies a volume for NetWare servers (rarely used today).

Additional usage:

• net use (without parameters): Lists all active network connections.
• net use /?: Displays the help menu with detailed options.

Common Use Cases and Examples

Below are practical examples of the net use command, covering common scenarios.

1. List All Active Network Connections

To view all mapped drives and connected resources:

net use

Output (example):

New connections will be remembered.

Status       Local     Remote                    Network
-------------------------------------------------------------------------------
OK           Z:        \\Server1\SharedFolder    Microsoft Windows Network
The command completed successfully.

2. Map a Network Drive

To map a network share to a local drive letter (e.g., Z:):

net use Z: \\Server1\SharedFolder

If authentication is required:

net use Z: \\Server1\SharedFolder /user:MYDOMAIN\user1 mypassword

To prompt for a password (safer):

net use Z: \\Server1\SharedFolder /user:MYDOMAIN\user1 *

Notes:

• Replace Server1 with the actual server name or IP address (e.g., \\192.168.1.10\SharedFolder).
• If the share is on the same domain, you may omit MYDOMAIN.

3. Map a Drive with Persistent Connection

To make the mapped drive persist after a reboot:

net use Z: \\Server1\SharedFolder /persistent:yes

To make it temporary (clears on reboot):

net use Z: \\Server1\SharedFolder /persistent:no

4. Disconnect a Mapped Drive

To remove a mapped drive:

net use Z: /delete

To disconnect all network connections:

net use * /delete

Note: Use /delete with caution, as it terminates active connections.

5. Connect to a Printer

To connect to a shared network printer:

net use LPT1: \\PrintServer\PrinterName

Replace PrintServer and PrinterName with the appropriate server and printer share names.

6. Save Credentials for Future Use

To store credentials for automatic reconnection (use cautiously):

net use Z: \\Server1\SharedFolder /user:MYDOMAIN\user1 mypassword /savecred

Warning: Storing credentials can pose a security risk if the system is compromised.

7. Connect Using a Different User

To access a share using credentials from a different domain or user:

net use Z: \\Server1\SharedFolder /user:OTHERDOMAIN\user2 *

This prompts for the password for user2 in OTHERDOMAIN.

8. Connect to a Hidden Share

Hidden shares (ending with $, e.g., \\Server1\HiddenShare$) can be accessed similarly:

net use Z: \\Server1\HiddenShare$ /user:MYDOMAIN\user1 *

9. Connect to an IP Address

If the server is identified by an IP address:

net use Z: \\192.168.1.10\SharedFolder /user:user1 *

10. Automate in a Batch Script

To map a drive in a batch file (e.g., mapdrive.bat):

@echo off
net use Z: \\Server1\SharedFolder /user:MYDOMAIN\user1 mypassword /persistent:yes
if %ERRORLEVEL%==0 (
    echo Drive mapped successfully!
) else (
    echo Failed to map drive.
)

Run the script as an administrator if needed.

Advanced Options and Tips

• Error Handling: Check the %ERRORLEVEL% variable in scripts to handle failures (0 = success, non-zero = error).
• Multiple Connections: You can map multiple shares to different drive letters (e.g., X:, Y:, Z:).
• PowerShell Alternative: In PowerShell, you can use New-PSDrive for similar functionality, but net use is still widely used for compatibility.

  New-PSDrive -Name Z -PSProvider FileSystem -Root "\\Server1\SharedFolder" -Credential (Get-Credential)

• Credentials Management: Avoid hardcoding passwords in scripts. Use * to prompt or store credentials securely in Windows Credential Manager.
• Firewall Considerations: Ensure SMB ports (TCP 445) are open for network shares. Check firewall rules with:

  netsh advfirewall show rule name=all

Troubleshooting Common Issues

• “System error 53 has occurred” (Network path not found):
• Verify the UNC path (\\computername\sharename) is correct.
• Ensure the server is reachable (ping Server1).
• Check if the share exists and is accessible.
• “System error 5 has occurred” (Access denied):
• Confirm the username and password are correct.
• Ensure the user has permissions to the share.
• Run Command Prompt as Administrator (Run as administrator).
• “System error 67 has occurred”:
• Indicates a network name issue. Verify the server name or IP.
• Drive Not Available After Reboot:
• Ensure /persistent:yes was used, or re-run the command.
• Multiple Connections to the Same Server:
• Windows may block connections with different credentials to the same server. Disconnect existing sessions first:
  cmd net use \\Server1 /delete
• Slow Connection:
• Check network connectivity and latency.
• Verify DNS resolution for the server name.

For detailed logs, use:

net use /verbose

Security Considerations

• Avoid Storing Credentials: Using /savecred stores credentials in plain text, which can be exploited. Prefer interactive prompts (*).
• Use Strong Passwords: Ensure network share credentials are secure.
• Limit Share Permissions: Configure shares to allow access only to necessary users or groups.
• Encrypt Network Traffic: Use SMB 3.0 or higher for encrypted connections (supported in modern Windows versions).
• Audit Connections: Regularly review active connections with net use to detect unauthorized access.

Alternatives to net use

While net use is powerful, consider these alternatives for specific scenarios:

• PowerShell Cmdlets: New-PSDrive, Remove-PSDrive for modern scripting.
• GUI Tools: Use File Explorer to map drives (Right-click “This PC” > “Map network drive”).
• Third-Party Tools: Tools like FreeFileSync or enterprise solutions for advanced share management.

Conclusion

The net use command is a versatile and essential tool for managing network resources in Windows. Whether mapping drives, connecting to printers, or automating network access in scripts, it provides a robust solution for both administrators and end-users. By mastering its options—such as persistent connections, credential management, and disconnection—you can streamline network operations efficiently.

For further exploration, refer to Microsoft’s official documentation (net use /?) or experiment with the command in a test environment. If issues persist, community forums like Stack Overflow or Microsoft Learn are excellent resources.

Note: This guide is based on Windows 10/11 and Windows Server 2022 as of August 15, 2025. Always verify syntax and compatibility with your specific Windows version.