I found a reproducible issue with ADB Explorer 0.9.26.030 on Windows 10.
Environment
Windows 10 21H2 (19044)
ADB Explorer 0.9.26.030 (bundled ADB 37.0.0)
Separate Android Platform Tools: ADB 36.0.0
Huawei VOG-L29 connected via USB debugging
Problem
If ADB 36.0.0 has already started the ADB server, ADB Explorer detects the phone correctly, but after clicking Browse it keeps loading indefinitely. Refresh and other controls are disabled and no error message is displayed.
ADB itself works correctly in this state:
adb devices -l
DUM0219A29000819 device product:VOG-L29EEA model:VOG_L29 device:HWVOG
adb shell
HWVOG:/ $
Access to /storage/emulated/0 also works normally.
Reproducible workaround
Close ADB Explorer.
Run adb kill-server using the separate ADB 36.0.0.
Do NOT start ADB manually again.
Start ADB Explorer.
The device is detected and Browse works immediately.
This suggests a compatibility/problem-handling issue when ADB Explorer 0.9.26.030 encounters an already running ADB server from another ADB version.
It would be helpful if ADB Explorer could detect this situation and either reuse a compatible running server or display a warning. A timeout/error code would also be preferable to indefinite loading.
Additional note: I previously tried the newer 1.x release on the same Windows 10 PC. After installing the required newer .NET runtime (I believe .NET 9), the application did not start or show any visible error. I therefore returned to 0.9.26.030. I can provide more details separately if useful.
I found a reproducible issue with ADB Explorer 0.9.26.030 on Windows 10.
Environment
Windows 10 21H2 (19044)
ADB Explorer 0.9.26.030 (bundled ADB 37.0.0)
Separate Android Platform Tools: ADB 36.0.0
Huawei VOG-L29 connected via USB debugging
Problem
If ADB 36.0.0 has already started the ADB server, ADB Explorer detects the phone correctly, but after clicking Browse it keeps loading indefinitely. Refresh and other controls are disabled and no error message is displayed.
ADB itself works correctly in this state:
adb devices -l
DUM0219A29000819 device product:VOG-L29EEA model:VOG_L29 device:HWVOG
adb shell
HWVOG:/ $
Access to /storage/emulated/0 also works normally.
Reproducible workaround
Close ADB Explorer.
Run adb kill-server using the separate ADB 36.0.0.
Do NOT start ADB manually again.
Start ADB Explorer.
The device is detected and Browse works immediately.
This suggests a compatibility/problem-handling issue when ADB Explorer 0.9.26.030 encounters an already running ADB server from another ADB version.
It would be helpful if ADB Explorer could detect this situation and either reuse a compatible running server or display a warning. A timeout/error code would also be preferable to indefinite loading.
Additional note: I previously tried the newer 1.x release on the same Windows 10 PC. After installing the required newer .NET runtime (I believe .NET 9), the application did not start or show any visible error. I therefore returned to 0.9.26.030. I can provide more details separately if useful.