In this comprehensive tutorial, we will show you the steps to fix the “adb server version doesn’t match this client; killing…” error. As far as the xx in the above error is concerned, well it depends on the ‘two’ ADB versions currently installed on your PC. With that said, I have usually seen these numbers lying between 30-40, keeping a few buffer margins at hand. Among all the ADB and Fastboot issues that we have covered here, this seems to have infuriated the maximum number of users.
The reason for the same is the fact that its fixes are a little bit more on the complicated side (for the newcomers). Keeping that in mind, we have listed out the instructions in the simplest of manners without incorporating any technical terms. As usual, with each fix, comes its associated screenshots as well that will aid you in rectifying this issue. So without further ado, let’s start off with the guide to fix the “adb server version doesn’t match this client; killing…” error.
- How to fix ADB Device not found [List of Devices Attached is blank]
- Detailed Steps to Fix adb is not recognized Error
- How to Fix Unauthorized Device with ADB Commands [3 methods]
- How to Fix FAILED (remote: Command not allowed)
Fix adb server version doesn’t match this client; killing…
There isn’t any universal fix for this issue, so you might have to try out all the below mentioned fixes until you achieve success. So without further ado, let’s get started.
Fix 1: Killing the alternate ADB Servers
It might be the case that there are two or more instances of ADB already running on your PC. This conflicting nature will surely lead to a few issues. It doesn’t matter if you have only one CMD/PowerShell window opened that isn’t the general yardstick of identifying the total number of ADB servers.
- So then how to stop the other ADB servers running in the background? Well, with the help of a single command! Just head over to the Command Prompt window that you have opened inside the platform-tools folder and type in the below two commands:
adb kill-server adb start-server
- The first command will kill off all the running ADB servers whereas the second one will restart only the required server. So once you have executed the above commands, see if it fixes the “adb server version doesn’t match this client; killing…” error.
Fix 2: Manually Stopping the ADB Server
If the above method didn’t manage to fix the issue, then you may also take the manual approach towards the same.
- To begin with, execute the below command in the CMD window:
- adb version
- You will now get two different versions of ADB as the output. It should be something along the following lines:
Android Debug Bridge version 1.0.41 Version 29.0.1-5644136 Installed as C:\Users...\AppData\Local\Android\Sdk\platform-tools\adb.exe Android Debug Bridge version 1.0.41 Version 30.0.4-6686687 Installed as C:\Users...\AppData\Local\Android\Sdk\platform-tools\adb.exe
- These two versions will be the same numbers as depicted in the error message! So your aim is to kill one of the servers (the third-party ADB tools) while keeping the other one (Google’s platform-tools) up and running.
- So head over to the non-Google ADB binaries that you have installed and type in CMD in its address bar. This will launch the Command Prompt window.
- Now type in the below code to kill its server:
- Once that is done, it is also recommended that you delete that third-party ADB Tool.
- Then head over to the platform-tools folder, and open the CMD window there.
- Now type in the following command to start the ADB server in this directory:
- Once the server has started there, it should have fixed the “adb server version doesn’t match this client; killing…” error. To verify the same, you may again execute the adb version command and this time, you will only get a single ADB version, as shown below. [I have deleted older ADB Version 29.0.1-5644136, so I only have the newer ADB version 30.0.4-6686687] However, if you are still getting this issue, then here are some other methods that deserve your attention.
- How to Execute Android ADB Fastboot Commands Wirelessly
- Run ADB Fastboot Commands directly on Android without Root
- How to Use ADB and Fastboot Commands on Android Without PC
- How to Create and Port TWRP Recovery for any Android Device
Fix 3: Uninstall the Conflicting ADB Software or Change its ADB Source
This is among the most common reason for this issue. So here is what really happens. If you have any ADB or Fastboot Tools/Software or installed or have any app that uses these binaries, then they instruct the PATH environment variable to point to their directory rather than the one belonging to the platform-tools. Dell PC Suite and HTC Sync are two perfect examples of the same.
So there are three different approaches to deal with this issue. The first one is to simply uninstall these type of softwares from your PC. This will then fix the “adb server version doesn’t match this client; killing…” error. While this is definitely a shorter route to fix this issue, but it isn’t a viable approach. This is because some of you might actually be needing this software for other related tasks.
On the other hand, the second approach is to change the ADB settings from within the app itself. The plus side is that it will fix the issue in no time whatsoever. But on the flip side, not every all has this functionality. The best way to check for the same is to go to the app’s Settings page and check out the ADB section. If they are using their own ADB binaries, then make it switch to the platform-tools ADB.
As an example, many users have reported facing this issue while using the Genymotion for a virtual device. So if you are among those set of users, then launch the app and go to its Settings tab. Then head over to the ADB section and you would notice that by default it is using the Genymotion ADB Tools. Now select Use custom Android SDK Tools. Then click Browse and navigate to the platform-tools folder and select it. Once this is done, kill and restart the ADB server (adb kill-server and adb start-server) via the instructions given in the first fix.
That’s it. The second method to fix the “adb server version doesn’t match this client; killing…” error. stands complete. Let’s check out the third one. The third and final method is to manually change the ADB PATH environment variable and make it point to the platform-tools binary rather than to any other app or software. Since it is a slightly longer fix, I have mentioned it in the below section. Follow along.
Fix 4: Add/Change/Delete the ADB PATH Environment Variable
This section will deal with two instances. In the first one, we will show you the steps to change the ADB Path Variables and make them point to the platform-tools folder. This will come in handy if your tool or software doesn’t have a native option to change the ADB directory, such as the one that Genymotion had.
On the other hand, as far as deleting the ADB PATH Environment Variable is concerned, it will come in handy if your system is pointing to two different ADB locations. This usually happens if you have more than one ADB binaries installed. For example, if you have both Google’s Android SDK Platform Tools and Minimal ADB and Fastboot installed. This ends up creating two instances of the ADB in your variables path which in turn confuses the tool which one to ultimately go for.
In that case, the best route is to delete the second ADB path. And it goes without saying that it is recommended to delete the ADB path of third-party tools and keep Google’s platform-tools intact. But what if the ADB directory is missing from the Environment Variable? Well, there is a pretty easy way to add the platform-tools as well. So without further ado, let’s check out all these methods (change/delete ADB path) to fix the “adb server version doesn’t match this client; killing…” error.
- How to Enable gpedit.msc Local Group Policy Editor in Windows 10 Home
- Unlock Hardware and Devices Troubleshooter in Windows 10
- Fix: pip is not recognized as an internal or external command
- How to Run Linux Commands in Windows 10 [without Virtual Machine]
Instructions to Add/Change or Delete the ADB PATH Environment Variable
- To begin with, head over to the Start menu and search for View Advanced System Settings.
- Then go to the Advanced tab and click on the Environmental Variables button.
- You should now see two sections: User Variables and System variables. We will have to keep our focus on the latter one.
- So select the Path field from the System Variables section and click on Edit.
- It will bring up the Edit environment variable option. Now if you see two different ADB variables added to this list, select the one that belongs to a third-party ADB Tool. In other words, select the one that isn’t Google’s platform-tools.
- Once you have made the selection, hit the Delete button. With that, you should now only have the single ADB directory inside the Environment Variable, and that should be the platform-tools one. However, if you don’t have any platform-tools folder, then move directly to STEP 8.
- Likewise, the path will also be visible in System variables under Environment Variables, as shown in the below image. Click OK to close this dialog box as well. That’s it. Your error now stands rectified.
- Since you have come to this point, it’s just because you don’t see any platform-tools variable. Fret not, the fix is pretty easy. All you need to do is click on the Add button from the right menu bar.
- After this, browse to the location where you have the platform-tools folder, select it, and hit OK.
- That’s it. These were the steps to add, delete, or change the ADB PATH Environment Variable. With this, you would have fixed the adb server and client mismatch error as well.
So with this, we conclude the guide on how to fix the “adb server version doesn’t match this client; killing…” error. We have shared four different methods to rectify this issue. Do let us know in the comments which one spelled success in your case. Likewise, if you have any issues concerning the aforementioned instructions or any issue related to ADB or Fastboot, do let us know in the comments. We will get back to you with a solution at the earliest.
- How to Pass Magisk SafetyNet on Rooted Android 11
- Root Android 11 via Magisk Patched boot.img (without TWRP)
- Fix Magisk patched boot.img issue while Rooting Android 11
- How to Boot any (Bricked/Unbricked) Android Device to EDL Mode