{"id":11200,"date":"2026-02-12T00:36:08","date_gmt":"2026-02-12T00:36:08","guid":{"rendered":"https:\/\/howtogeek.blog\/ja\/?p=11200"},"modified":"2026-02-12T00:36:08","modified_gmt":"2026-02-12T00:36:08","slug":"how-to-resolve-the-adb-device-not-found-error-on-windows","status":"publish","type":"post","link":"https:\/\/howtogeek.blog\/ja\/how-to-resolve-the-adb-device-not-found-error-on-windows\/","title":{"rendered":"How To Resolve the \u201cADB Device Not Found\u201d Error on Windows"},"content":{"rendered":"

Connecting an Android phone to a PC for ADB debugging is usually straightforward \u2014 plug in the cable, enable USB debugging, and you’re good to go. But sometimes, things just don’t line up. The device might not show up under adb devices<\/strong>, or Windows refuses to recognize it altogether. Frustrating, right? Especially since it can be caused by a mix of simple stuff like bad cables, incorrect settings, or even driver issues. So, here\u2019s a collection of practical fixes that have worked on multiple setups, even if some steps feel a bit overkill or confusing. Hope it gets you closer to that debugging session.<\/p>\n

How to Fix \u201cADB Device Not Found\u201d Problem on Windows<\/h2>\n

Set ADB Path as an Environment Variable<\/h3>\n

If issuing adb devices<\/code> in Command Prompt just results in \u201cnot recognized, \u201d chances are Windows doesn\u2019t know where to find your ADB executable. This is a pretty common hiccup and fixing it is more about making sure the system can find your tools than fixing the connection itself. It\u2019s worth trying because on some computers, just setting this path makes the device show up instantly.<\/p>\n

Here\u2019s why it helps: by adding your platform-tools directory (where adb.exe<\/code> lives) to the environment variables, you can run adb<\/code> commands from anywhere, no matter which folder you\u2019re in. When that\u2019s set, the command prompt can find everything without fuss.<\/p>\n

Steps (roughly):<\/p>\n

    \n
  1. Open File Explorer<\/strong> and find your SDK Platform-Tools folder. Usually, you downloaded it from the Android developer site<\/a>.<\/li>\n
  2. Right-click the platform-tools<\/strong> folder and select Copy as path<\/strong>.<\/li>\n
  3. Press Windows + R<\/strong>, type sysdm.cpl<\/code>, and hit Enter<\/strong>.<\/li>\n
  4. Switch to the Advanced<\/strong> tab and click on Environment Variables\u2026<\/strong><\/li>\n
  5. Under System variables<\/strong>, find Path<\/strong> and click Edit<\/strong>.<\/li>\n
  6. Click New<\/strong>, paste your copied path, like C:\\Users\\YourName\\Downloads\\platform-tools<\/code>, then hit OK<\/strong> all the way out.<\/li>\n
  7. Close all dialogs, restart Command Prompt, and test by typing adb devices<\/code>. If it lists attached devices \u2014 success!<\/li>\n<\/ol>\n

    Sometimes, Windows messes up the path copying or just refuses to update immediately. Try closing and reopening your command line or rebooting the PC if it still doesn’t recognize adb. Strange, but it happens. If you get an \u201cADB not recognized\u2026\u201d message, double-check the path\u2014it\u2019s easy to make typos or forget to include \\<\/p>\n

    Enable USB Debugging on Android<\/h3>\n

    This one\u2019s kinda obvious but often overlooked. Without enabling USB debugging<\/strong>, ADB can\u2019t see or communicate with your device. Usually, it’s under Developer options<\/strong>, which are hidden by default \u2014 so you have to unlock them first. No worries, it\u2019s simple enough, but some folks forget to toggle it back on after updates, or disable it accidentally.<\/p>\n

    Here\u2019s how it\u2019s done:<\/p>\n

      \n
    1. Open Settings<\/strong> on your Android device.<\/li>\n
    2. Scroll down to About phone<\/strong> (or System > About device).<\/li>\n
    3. Find Build number<\/strong> and tap on it 7+ times. On some devices, it might say \u201cYou\u2019re now a developer\u201d or something similar.<\/li>\n
    4. Go back to Settings<\/strong> and find Developer options<\/strong>.<\/li>\n
    5. Scroll down and toggle on USB debugging<\/strong>.<\/li>\n
    6. Replug your device, and at the prompt, tap Allow<\/strong> for debugging permissions. That last part is pretty key\u2014if you don\u2019t do that, ADB won\u2019t recognize the device even if debugging is enabled.<\/li>\n<\/ol>\n

      Note: If debugging was already enabled, try disabling it, reconnecting, and enabling again. Sometimes, Android just needs a kick to refresh permissions.<\/p>\n

      Switch USB Modes \/ Preferences<\/h3>\n

      You know how when you connect your phone, it defaults to charging only? Yeah, that won\u2019t work for ADB because it needs a different mode\u2014MTP or PTP usually).You might have to switch manually to get ADB detected.<\/p>\n

      Here\u2019s what to do:<\/p>\n

        \n
      1. Connect your phone, and pull down the notification shade.<\/li>\n
      2. Tap on the USB for file transfer<\/strong> notification or just USB Preferences<\/strong>.<\/li>\n
      3. Select either File Transfer (MTP)<\/strong>, Photo Transfer (PTP)<\/strong>, or, sometimes, USB debugging<\/strong> modes if available.<\/li>\n<\/ol>\n

        On some phones, choosing the right mode can be trial and error\u2014different Android versions or device brands might require a different setting. Just keep toggling until your device shows up under ADB.<\/p>\n

        Toggle Additional Developer Options<\/h3>\n

        Some Android devices have extra settings that can interfere. For example, Stay Awake<\/strong> under Developer options can sometimes help or hinder your debugging. It keeps the screen on while plugged in, which might help debugging sessions stay active, but on some other setups, turning it off clears some conflicts.<\/p>\n

        Go to Settings > Developer options<\/strong> and toggle Stay awake<\/strong>. Also, consider revoking USB debugging authorizations if you previously allowed the PC, which can mess things up if permissions get stale.<\/p>\n

          \n
        1. In Developer options<\/strong>, find Revoke USB debugging authorizations<\/strong>.<\/li>\n
        2. Tap it, then confirm. Next time you connect, you’ll get a fresh permission prompt.<\/li>\n<\/ol>\n

          This sometimes resets the connection enough for ADB to recognize the device properly.<\/p>\n

          Restart the ADB Server<\/h3>\n

          If all else fails, it might just be that the ADB server went rogue. Restarting it can fix hanging connections or stale sessions. It\u2019s simple:<\/p>\n

            \n
          1. Open Command Prompt<\/strong>, then type: adb kill-server<\/code> and hit Enter.<\/li>\n
          2. Follow it with: adb start-server<\/code>.<\/li>\n
          3. Finally, run adb devices<\/code> again, and see if your device pops up.<\/li>\n<\/ol>\n

            Sometimes, this step alone unsticks things\u2014on one machine it worked straight away, but another time, a PC needed a reboot after restart. Despite sounding basic, ADB servers are temperamental sometimes.<\/p>\n

            Manually Update USB Drivers<\/h3>\n

            Everything above might fall flat if Windows isn\u2019t using the right driver. When you connect your device, Windows tries to auto-install a driver, but it\u2019s not always the best choice, especially with generic or outdated drivers. Installing the correct Google USB driver usually helps.<\/p>\n

            Here\u2019s the rundown:<\/p>\n

              \n
            1. Download the Google USB Driver<\/a> ZIP file, extract it somewhere safe.<\/li>\n
            2. Open Device Manager<\/strong> (`devmgmt.msc`).You can do this via Run<\/strong> (Windows + R<\/kbd>) and type that in.<\/li>\n
            3. In View<\/strong>, select Show hidden devices<\/strong>.<\/li>\n
            4. Find your device\u2014look under categories like Portable Devices<\/strong>, Android Devices<\/strong>, or maybe Other Devices<\/strong>.<\/li>\n
            5. If you see a device with a yellow exclamation point or greyed out, right-click and choose Update driver<\/strong>.<\/li>\n
            6. Select Browse my computer for drivers<\/strong>, then navigate to the folder where you extracted the SDK ZIP.<\/li>\n
            7. Click Next<\/strong>, let Windows do its thing, and confirm if it successfully updates the driver.<\/li>\n<\/ol>\n

              Sometimes Windows installs a generic driver that won’t play nice with ADB, so manually pointing to the Google USB driver can make a big difference.<\/p>\n

              All these methods target different potential issues\u2014from setup, permissions, cable\/connection problems, to driver mismatches. It\u2019s kind of a scavenger hunt, but working through each bit will get your Android device recognized eventually.<\/p>\n","protected":false},"excerpt":{"rendered":"

              Connecting an Android phone to a PC for ADB debugging is usually straightforward \u2014 plug in the cable, enable USB debugging, and you’re good to go. But sometimes, things just don’t line up. The device might not show up under adb devices, or Windows refuses to recognize it altogether. Frustrating, right? Especially since it can […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-11200","post","type-post","status-publish","format-standard","hentry","category-how-to"],"acf":[],"_links":{"self":[{"href":"https:\/\/howtogeek.blog\/ja\/wp-json\/wp\/v2\/posts\/11200","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/howtogeek.blog\/ja\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/howtogeek.blog\/ja\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/howtogeek.blog\/ja\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/howtogeek.blog\/ja\/wp-json\/wp\/v2\/comments?post=11200"}],"version-history":[{"count":1,"href":"https:\/\/howtogeek.blog\/ja\/wp-json\/wp\/v2\/posts\/11200\/revisions"}],"predecessor-version":[{"id":11201,"href":"https:\/\/howtogeek.blog\/ja\/wp-json\/wp\/v2\/posts\/11200\/revisions\/11201"}],"wp:attachment":[{"href":"https:\/\/howtogeek.blog\/ja\/wp-json\/wp\/v2\/media?parent=11200"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/howtogeek.blog\/ja\/wp-json\/wp\/v2\/categories?post=11200"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/howtogeek.blog\/ja\/wp-json\/wp\/v2\/tags?post=11200"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}