Issues like these are pretty common with antivirus software and thus, while using one, you need to make sure that it isn’t triggering a false positive on the files that you are working with. In addition to that, your project settings can also cause this error message to pop up. To understand and establish a better understanding of the error message in question, let us discuss the different reasons the issue may arise in more detail. However, do remember that the causes include but are not limited to the ones mentioned down below.Third-Party Antivirus - Antivirus softwares are known to cause several issues where they remove a file from your system due to a false positive.If this is applicable, you will have to restore the file from there and everything should be good.Īvast antivirus has been known to cause this a lot with ADB where it locks the file in the virus chest. Project Settings - As it turns out, in some cases, the error message may arise due to your project settings.However, keep in mind that it may not only be limited to Avast if you are using a different third-party antivirus, but it could also likely be causing the issue and thus you should look at the files that have been quarantined by the application. The Android SDK by default does not give projects a default SDK. In such a scenario, you will have to go to the project settings and give the project an SDK which by default is set to No SDK. Corrupted Platform Tools - In addition to the aforementioned reasons, if your platform tools are damaged or corrupted, that might result in the error message as well.

If this scenario is applicable, Windows Defender or any third-party software likely quarantines it, and as a result, you no longer have the adb.exe file in the platform-tools folder.

Unable to locate adb android studio