If you have problem installing the drivers,
you can try edit the file android_winusb.inf
and modify the %CompositeAdbInterface% entry in [Google.NTx86] for 32bit systems
or [Google.NTamd64] for 64bit systems (msdn says .NTamd64 is not for itanium processors and you should use .NTia64 in that case).
You have to open the device manager and find the Hardware ID
of the device that windows displays with the question mark
and is related to your phone (in case you have multiple devices with question mark).
It should be something similar to USB\VID_12D1&PID_xxxx&MI_xx.
If you do this, use the new hardware installation wizard and windows will install the drivers without any trouble.
This is the procedure I used for the drivers I posted and will also probably function in future android versions when and if the Hardware Id changes.
I have the latest Aurora version (4.1 update 1a) and I get 5 Android devices in my Win7 x64 Device Manager.
All of them have the hardware ID USB\VID_12D1&PID_9025&REV_0231&MI_0x and the only thing that changes is the MI_0x part, from MI_00 to MI_04.
Can someone who has the drivers correctly installed tell me which MI_0x corresponds to which device name?
They can't be all Android Composite ADB Interface can they? Are they?