Android Question Windows 10 v.1607: device is not debuggable, but ADB works

[peacemaker]

After latest recent update of Windows 10 up to the Anniversary Update v.1607 - all devices were reset.
Drivers must be re-installed.
One old phone with Android 4.4 is OK, debuggable via USB from IDE is again OK.
But another phone under MIUI 8 (Android 5.0.x) - is not accesible via USB from IDE, app cannot be installed, timed out.
But ADB manually works OK, the device is listed, adb shell works.
B4A WiFi bridge works OK.

How to understand what this is via USB? Seems, something inside the Android, but where to dig ?

 

[Erel]

Are you able to install with "adb install <your apk>" ?

 

[peacemaker]

No :-(

p:\Private\android-sdk\platform-tools>adb install 1.apk
[100%] /data/local/tmp/1.apk
<blinking cursor here forever>

And nothing on the display...

Another Android 4.4 is OK:

p:\Private\android-sdk\platform-tools>adb install 1.apk
[100%] /data/local/tmp/1.apk
        pkg: /data/local/tmp/1.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]

p:\Private\android-sdk\platform-tools>

 

[Erel]

Have you tried to reinstall Android SDK?

 

[peacemaker]

No. Now installed a current weekly FW update, reset the USB debugging - and now works.
Strange, but .... now is OK.
Thanks, Erel.