1. Microsoft Debug Diagnostic Tool
2. Debugging Tools For Windows Download
3. Microsoft Debugging Tool Windows 7
4. Windbg Debugger Windows 7

-->

X64 Windows Debugging: Practical Foundations. Windows Debugging Notebook: Essential User Space WinDbg Commands. Inside Windows Debugging: A Practical Guide to Debugging and Tracing Strategies in Windows. Advanced Windows Debugging (The Addison-Wesley Microsoft Technology Series) What Makes It Page?: The Windows 7 (x64) Virtual Memory Manager. Jul 14, 2011  The Debug Diagnostic Tool (DebugDiag) is designed to assist in troubleshooting issues such as hangs, slow performance, memory leaks or fragmentation, and crashes in any user-mode process. The tool includes additional debugging scripts focused on Internet Information Services (IIS) applications, web data access components, COM+ and related Microsoft technologies.

Start here for an overview of Debugging Tools for Windows. This tool set includes WinDbg and other debuggers.

Install Debugging Tools for Windows

You can get Debugging Tools for Windows as part of a development kit or as a standalone tool set:

• As part of the WDK

  Debugging Tools for Windows is included in the Windows Driver Kit (WDK). To get the WDK, see Download the Windows Driver Kit (WDK).

• As part of the Windows SDK

  Debugging Tools for Windows is included in the Windows Software Development Kit (SDK). To download the installer or an ISO image, see Windows 10 SDK on Windows Dev Center.

• As a standalone tool set

  You can install the Debugging Tools for Windows alone, without the Windows SDK or WDK, by starting installation of the Windows SDK and then selecting only Debugging Tools for Windows in the list of features to install (and clearing the selection of all other features). To download the installer or an ISO image, see Windows 10 SDK on Windows Dev Center.

Get started with Windows Debugging

Microsoft Debug Diagnostic Tool

To get started with Windows debugging, see Getting Started with Windows Debugging.

To get started with debugging kernel-mode drivers, see Debug Universal Drivers - Step by Step Lab (Echo Kernel-Mode). This is a step-by-step lab that shows how to use WinDbg to debug Echo, a sample driver that uses the Kernel-Mode Driver Framework (KMDF).

Debugging environments

If your computer has Visual Studio and the WDK installed, then you have six available debugging environments. For descriptions of these environments, see Debugging Environments.

All of these debugging environments provide user interfaces for the same underlying debugging engine, which is implemented in the Windows Symbolic Debugger Engine (Dbgeng.dll). This debugging engine is also called the Windows debugger, and the six debugging environments are collectively called the Windows debuggers.

Note

Visual Studio includes its own debugging environment and debugging engine, which together are called the Visual Studio debugger. For information on debugging in Visual Studio, see Debugging in Visual Studio. For debugging managed code, such as C#, using the Visual Studio debugger is often the easiest way to get started.

Windows debuggers

The Windows debuggers can run on x86-based, x64-based, or ARM-based processors, and they can debug code that is running on those same architectures. Sometimes the debugger and the code being debugged run on the same computer, but other times the debugger and the code being debugged run on separate computers. In either case, the computer that is running the debugger is called the host computer, and the computer that is being debugged is called the target computer. The Windows debuggers support the following versions of Windows for both the host and target computers.

• Windows 10 and Windows Server 2016
• Windows 8.1 and Windows Server 2012 R2
• Windows 8 and Windows Server 2012
• Windows 7 and Windows Server 2008 R2

Symbols and symbol files

Symbol files store a variety of data that are not required when running the executable binaries, but symbol files are very useful when debugging code. For more information about creating and using symbol files, see Symbols for Windows debugging (WinDbg, KD, CDB, NTSD).

Blue screens and crash dump files

If Windows stops working and displays a blue screen, the computer has shut down abruptly to protect itself from data loss and displays a bug check code. For more information, see Bug Checks (Blue Screens). You analyze crash dump files that are created when Windows shuts down by using WinDbg and other Windows debuggers. For more information, see Crash dump analysis using the Windows debuggers (WinDbg).

Tools and utilities

In addition to the debuggers, Debugging Tools for Windows includes a set of tools that are useful for debugging. For a full list of the tools, see Tools Included in Debugging Tools for Windows.

Additional documentation

For additional information related to Debugging Tools for Windows, see Debugging Resources. For information on what's new in Windows 10, see Debugging Tools for Windows: New for Windows 10.

I am using Windows 7 64bit and I am trying to get my computer to detect my HTC Desire, but it's not picking it up. I have everything available installed through the Android Updater and I have got my phone running through Ubuntu, so it is definitely a problem with Windows. Does anyone know what's wrong or how to get it working or both?

• I am using Windows 7 64 bit

• I have a HTC Desire running Stock 2.2 (Froyo) that works with USB Debugging on my Ubuntu machine

• Windows does detect that my phone is plugged in. It shows as a mass storage device.

• I have all the available things installed via the Android Updater.

EJoshuaSNotACleverManNotACleverMan

6 Answers

I went through a huge hassle with this last night (took me 4-6 hours), but finally got it working. Based off of what you have said you already accomplished, complete these steps:

1. Reboot your computer (really, it couldn't hurt and who knows what residuals are chilling there that can screw this all up).
2. Connect your phone
3. In Device Manager, right-click any unknown devices related to your phone and update drivers. Manually point to the usb_drivers directory from your Android SDK.
4. At this point you should only have one undetected device (ADB), Windows will not be able to find drivers for it.
5. Download USBDeview, run as Administrator (requires right-click) and uninstall your phone and any ADB drivers it lists (your phone should still be connected).
6. Disconnect your phone.
7. Download HTCSync and install it.
8. Connect your phone, Windows should now attempt to install drivers and do so no problem.
9. Open a command window and type adb devices to confirm everything is running correctly (that is, if you placed the AndroidSDK's tools directory in your PATH variable).

Michael WalesMichael Wales

Have you already checked out the article on USB drivers for Windows? I'm not quite sure if you are supposed to install the drivers via the Android Updater.

Debugging Tools For Windows Download

Octavian DamieanOctavian Damiean

Had this problem on Windows 7 x64 and uninstalling in device manager then selecting manual install gave an error (something like: ensure driver is 64-bit compatible). Resolved as follows:

1. Connect phone
2. Run USBDeview as Administrator
3. Sort by Serial Number
4. Select all devices with Serial Number starting HT
5. Uninstall selected devices
6. Disconnect/reconnect phone
7. Windows will try, and fail, to install device, ignore that and...
8. Install driver via Device Manager:
   1. Open Device Manager (Start->My Computer, right click->Manage->Device Manager)
   2. Under Other, you should see a device with a yellow warning called ADB or Android Phone; right click ->Update driver software...
   3. Click Browse my computer for driver software
   4. Click Let me pick from a list of device drivers on my computer
   5. Select Show all devices, click Next
   6. Click Have disk...
   7. Browse to android sdk install directory and find the usb_driver directory (mine is in extrasgoogle)
   8. Select android_winusb.inf and click OK
   9. Select Android Composite ADB Interface and click Next
   10. When the Update Driver Warning appears click Yes

(Props to craigcrawford1988 on http://android.modaco.com/topic/309154-adb-device-driver-installation-failed-on-window-7-x64/)

Mike TunnicliffeMike Tunnicliffe

I got mine working in XP by editing the drivers .inf file. It seems the Desire is not listed in it.

Edit android_winusb.inf in the adtandroid-sdk-windowsusb_driver folder.

I added the following lines to the relevant NTx86 or NTamd64 section.

;HTC Desire%SingleAdbInterface% = USB_Install, USBVID_0BB4&PID_0C87&MI_01%CompositeAdbInterface% = USB_Install, USBVID_0BB4&PID_0C87&REV_0100&MI_01

This worked great for me.

Microsoft Debugging Tool Windows 7

Here is a very helpful link I followed for setting up my HTC Droid Incredible.

If you do not modify android_winusb.inf the USB debugging won't work.

AakashAakash

I had a similar problem of not being able to launch the Android app from Eclipse on real phone and not in AVD. Once I installed HTC Sync, it did the magic and I was able to use real phone.

Windbg Debugger Windows 7

Cheers,

Madhu

Not the answer you're looking for? Browse other questions tagged androidwindowsdebuggingusb or ask your own question.