IssueTracker

Thank you for this feedback. The team may reach out for more information on triaging or reproducing this issue.

pallavi@ - Have we done any testing on Win7? Looks like this issue should be easily reproducible.

a.sworowska: could you click the "view problem details" button and send us what that shows?

zyy: is there any other useful information about a crash on Windows that's easily available?

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    adb.exe
  Application Version:    0.0.0.0
  Application Timestamp:    34f534d5
  Fault Module Name:    adb.exe
  Fault Module Version:    0.0.0.0
  Fault Module Timestamp:    34f534d5
  Exception Code:    40000015
  Exception Offset:    00016717
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1033
  Additional Information 1:    7763
  Additional Information 2:    7763cd91f17ba1394e15130ad28436a8
  Additional Information 3:    622c
  Additional Information 4:    622c3aed538ac58f09882fe423edc57a


Also there's a console output: (for adb devices)
List of devices attached
* daemon not running. starting it now at tcp:5037 *
error: cannot open transport registration socketpair: Input/output error

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

We have the same problem at my workplace (computers running with the same configuration).
Changing the port (5037) didn't solve.
We were thinking about a conflict with the company's proxy but we gave up to find a solution as soon as we downgrade to 25.0.3 and understood that the update was responsible of the crash.

>zyy: is there any other useful information about a crash on Windows that's easily available?

One can generate a minidump file on crash, here's instructions (WER part): https://blogs.msdn.microsoft.com/chaun/2013/11/12/steps-to-catch-a-simple-crash-dump-of-a-crashing-process/

Other option would be to integrate Breakpad (https://chromium.googlesource.com/breakpad/breakpad/); it will take much longer but would allow for automatic / user-initiated crash information submission

I did the WER method and generate a dmp file (2 in fact because of the DumpCount set to 2... Should I set it higher ?)
But it is a 40MB file which I can't upload. Any suggestion ?