[HTC One X] Amishrabbit:
Hey, I just wanted to chime in on this thread because I'm having precisely the same problem as Qubica.

I'm using Windows 7/64 and I've been using this laptop to manage/root/ADB several Android devices for as long as I've owned it.

I noticed last Friday that I could no longer mount my T-Mobile G2 either as a USB mass-storage device nor could I connect to it using ADB. This was the day after Windows Update installed a bunch of patches, and I had also installed the updated chipset drivers for my laptop a few days earlier.

I took a look at the device manager and this is what I saw:

(android_devmgmt.png)

Now, that's weird because I mount the storage card at least two times a month to move files around. So I did what seemed like the reasonable thing and Uninstalled the device altogether, and then installed the HTC Sync app to reinstall the drivers, as I had done originally. Unfortunately, the "Android Phone" non-detection of the device has persisted.

The installation logs from the HTC Sync app also indicates that the drivers were successfully installed, but the installer seems to quit about halfway through the process, so it's not at all clear that the installation logs are accurate.

Here's what the properties sheet of that device looks like:

(android_devmgmt_properties.png)

I've been following the advice I've read here and elsewhere: I've attempted to download several different versions of the HTC drivers from various locations and manually point Device Manager at the folders containing those drivers. I've extracted and executed the HTCDriver.exe installer separately from the HTC Sync installer. I've attempted to install generic ADB drivers from a number of locations, including Google and the Clockworkmod Universal ADB drivers.

Here's the result when I try to install the drivers (by pointing Windows at the correct location for the driver files) or if I allow Windows Update to search for the drivers:

(cant-find-android-driver.png)

So, this morning I tried the more drastic step of uninstalling all of the USB Root Hub devices and rebooting the laptop. When the computer came back, it did not automagically reload those generic drivers, but fortunately I was able to manually choose the generic (Standard USB Host Controller) -> USB Root Hub device from the list of options, and it worked---for getting the USB ports to function, but not the Android device.

I've also checked to make sure there were no software restriction policies in place in gpedit.msc that affected the installation of the drivers, and found none. I also poked around in the Registry in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles path and found no problems there with either permissions or settings.

I'm basically at my wit's end here; Windows is behaving like the driver installation is subject to a software restriction policy -- seemingly, actively preventing the driver from being installed -- but nothing shows up in the logs that would indicate that a policy is in place. The laptop can't mount the device, and I'm kind of stuck.

I guess I'll follow the thread for a while and see if anyone else has any suggestions. Thanks in advance to all that offer their help.