Android Studio提示无法检测adb版本，退出值0xc0000135如何解决？

Hey there, I’ve dealt with this exact adb error countless times when connecting Android devices to Studio—total headache, right? Let’s walk through the most reliable fixes step by step, since that exit code 0xc0000135 almost always ties back to missing runtime components or a wonky adb setup.

1. Install/Repair Microsoft Visual C++ Redistributables #

This is the #1 culprit. ADB relies on these runtime libraries to run, and a missing or corrupted installation will trigger this error every time.

• Grab the latest Microsoft Visual C++ Redistributable packages matching your system architecture (x86 or x64). If you already have them installed, go to Programs and Features, find the redistributables, right-click, and select Repair—sometimes a damaged install is the issue.
• After installing/repairing, restart your computer completely before trying to connect your phone again.

2. Refresh Android SDK Platform-Tools #

Often, the adb binary itself is outdated or corrupted within Android Studio’s SDK:

• Open Android Studio, head to Tools > SDK Manager > SDK Tools
• Check if Android SDK Platform-Tools is selected. If it’s already installed, click Show Package Details, pick the latest version to update, or uninstall it first then reinstall (fresh copies fix weird glitches).
• Once done, restart Studio and test adb directly by running adb devices in the built-in terminal (find it via View > Tool Windows > Terminal).

3. Double-Check System PATH Variable #

Your system might not be able to locate adb because the platform-tools path isn’t in your environment variables:

• Open System Properties (right-click This PC > Properties > Advanced system settings), go to the Environment Variables tab.
• Under System Variables, find PATH, click Edit, and confirm the path to your platform-tools folder is present. It’s usually something like C:\Users\<YourUsername>\AppData\Local\Android\Sdk\platform-tools.
• If it’s missing, add it, save changes, and restart your PC. Test adb in a regular Command Prompt (not Studio’s terminal) by running adb version—if it still errors, the issue is system-wide.

4. Temporarily Disable Antivirus/Firewall #

Overzealous antivirus tools often flag adb as suspicious and block it from running:

• Disable your antivirus or firewall temporarily, then connect your phone again. If the error disappears, add an exception for adb.exe (located in the platform-tools folder) to your security software so it doesn’t interfere again.

5. Scan for Corrupted System Files #

Sometimes Windows system files get corrupted and break dependencies adb needs:

• Open Command Prompt as Administrator, run sfc /scannow and let it scan and repair any damaged files.
• If that doesn’t work, follow up with DISM /Online /Cleanup-Image /RestoreHealth to fix deeper system image issues. Restart your PC after both scans.

6. Reinstall Android Studio (Last Resort) #

If all else fails, a clean reinstall of Studio and the SDK usually clears up stubborn issues:

• Backup your projects and Studio settings (you can export settings via File > Manage IDE Settings > Export Settings).
• Uninstall Android Studio completely, then delete leftover folders: C:\Program Files\Android\Android Studio and C:\Users\<YourUsername>\AppData\Local\Android\Sdk.
• Download the latest Studio version and do a fresh install, then set up your SDK again.

内容的提问来源于stack exchange，提问作者Asmar J.