Sometimes cables/ports go bad, and maybe there isn't enough "juice" flowing through the cable for Winblows to recognize it as an iPhone? I'm just guessing here.
Originally Posted By: PChaterosx
And I forgot to mention it worked last week and I never said it didn't work at all. The computer knows its plugged in, it just doesn't see it as an iPhone. If I go to device manager and plug it in it says iPhone for a split second then goes to mtp USB device.
Who said that it didn't work at all? Not me either....
So you were able to sync last week...any update to Windows or anything since then that might have changed something?
Which version of Windows and which service pack? Not knowing Windows at all, and reading what you said about it saying it is an iPhone then switching over to USB device, it sounds like something has changed with your windows. Something new installed or deleted...don't know.
I'll leave this here for just a bit longer to see if we can rule out iTunes, but I'm really thinking this is a Windows/Hardware (PC) issue, not an iPhone one.
1. open add/remove programs from the control panel and make sure apple mobile device is installed. 1A. If not uninstall apple software update, itunes, and quicktime. Then reinstall itunes. 2. with the iphone connected, open computer management, look under services and make sure apple mobile device support is started. 2A. if you try to start it and it stops with a message that some services stop because there is not a task to perform, then you have software loaded on your computer that is blocking that service. This link from the apple support website might help out. http://docs.info.apple.com/article.html?artnum=302538 3. If previous fails and windows only wants to load the camera driver for the iphone then open device manager right click on the iphone that shows up under imaging devices and uninstall. 3A. disconnect the iphone and reconnect. When windows detects new hardware, do not let it automatically install the driver. try to force windows to load the driver from c:\windows\system32\drivestore\usbaapl_*
Try manually installing the driver by doing the following: *Right-click "My Computer" and select Manage *Select Device Manager *In the right-hand pane, expand Imaging Devices and select the iPhone (camera) *Right-click the iPhone camera and select Properties *Click the Driver tab *Click "Update Driver..." *When asked if you should connect to the internet, select No, not this time *Select Install from a list or specific location (Advanced) *Check "Include this location in the search" and point it to: C:\WINDOWS\system32\DRVSTORE\usbaapl_4351B7DAFF62FD33510D77DFAE3CF8CC82517571
Click Next
The driver should install, and now when you open iTunes you will see your iPhone.
#564986 - 09/26/1111:00 AMRe: Computer not detecting my iPhone
[Re: John Rougeux]
GAHeroine
The Greatest American Heroine
Registered: 09/15/09
Posts: 2384
Loc: Time traveling in 1980
Hm, I tried the troubleshooting assistant, but not the other stuff. I'll have to get on my computer and do that. The funny thing is the iPhone shows it's charging.. I'll keep this updated
Try manually installing the driver by doing the following: *Right-click "My Computer" and select Manage *Select Device Manager *In the right-hand pane, expand Imaging Devices and select the iPhone (camera) *Right-click the iPhone camera and select Properties *Click the Driver tab *Click "Update Driver..." *When asked if you should connect to the internet, select No, not this time *Select Install from a list or specific location (Advanced) *Check "Include this location in the search" and point it to: C:\WINDOWS\system32\DRVSTORE\usbaapl_4351B7DAFF62FD33510D77DFAE3CF8CC82517571 ...
was in a thread I posted. You said you did all of that. Hmmm.... help us help you.
Manually reinstalling the driver was the part I thought would help you and was going to post just that... but thought that if it didn't work then maybe something else in the thread would be beneficial.
I'm inclined to think that it isn't your cable if it's the same cable that worked on your Dads machine. And remembering my Windows experiences.. I'm betting faulty driver.