Happy to know that
LOL No I didn't, for some reason the app I use to create the installer of Droid Manager didn't use the latest version of AndroidLib (it's the library my app uses to communicate with the device), while testing version 6.2 before releasing it I included few debugging stuff that will write to text files on partition D, so all I did was use the latest modification of AndroidLib the one that has debugging stuff disabled.
In the end I'm happy everything went well, and I guess it's time to update to 6.2.1 for those who are having the same issue >_>
Wait what! You are still getting those files on your D partition (when it's available)
I rechecked the code and as I expected, no logging was enabled, so I rebuilt the Library again and uploaded it for you, just replace it with the one in Droid Manager's installation folder and you should be good to go
Download Link: AndroidLib
Edit: @chewdaniel Reading your comment again, you mentioned it worked on Windows 7, and was wondering windows 8.1 support, so does this mean your Windows 8.1 doesn't work anymore and the app is only working on Windows 7, I'm a bit lost :P lol
Why do I receive the "This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package." error?
This error can occur when an .EXE installation package is launched under the SYSTEM account. This happens because the bootstrapper doesn't extract its contents in the correct location when a per-user extract location is used.
|android, android explorer, android manager, droid manager, manager|
|Thread Tools||Search this Thread|