Why is the behavior so even when I added the adb folder to the path variable? And how can I run the command successfully universally?ĭuring my search, I found an application which provides PowerShell ADB & Fastboot GUI - PoshADB (just wanted to share). Now, when I open PowerShell in the same folder where I've installed platform-tools and run the adb command, I get this and it's successful.\adb devicesīut when I open PowerShell elsewhere and run the command, it's not successful. I've read some articles and am familiar with registry hacks to add "Open Command Prompt Here" and remove "Open PowerShell window here", but that's not something I would want to do, considering PowerShell is a lot more advanced than CMD. So even the menu shows an option to "Open PowerShell window here". I did some research, and found that Windows is slowly shifting to PowerShell (which is good) and (I guess) will omit the legacy CMD eventually. I installed adb and fastboot files (platform-tools) for Windows, and added the folder in the path variable so that I can access adb universally.
0 kommentar(er)
