I couldn't get any of the above solutions to work for me, or any thread I've stumbled across for that matter. But, I did finally get a solution, just from trial and error. Most of the stuff below a combination of other people's suggestions, so thanks to those people who posted.
Itunes: 9.0.2.25
Windows XP
Note: The below steps should only be done with someone that is familiar with computers, otherwise, you may cause more harm than good to your system.
Software needed (free):
WinRar :
http://www.rarlab.com/download.htm
LessMSI :
http://code.google.com/p/lessmsi/
For me, Apple Mobile simply would not install. During the install step it reached a certain point and then started to roll back the install. I needed to see what was going on during the install.
I grabbed the latest itunes.exe file and then opened it with Winrar. I then extracted out just the AppleMobile component and saved the msi file to my desktop. Then, I ran "Run" from the Start Menu and typed cmd to go to the command prompt. I typed: applemobiledevicesupport.msi /l*v C:\log.txt
This creates a log file called log.txt, located in your C:\ drive, and then loads the installer.
After the install fails, I opened the log file. I searched for the word "Fail":
This appeared:
DIFXAPP: ERROR: encountered while installing driver package 'C:\Program Files\Common Files\Apple\Mobile Device Support\Drivers\usbaapl.inf'
DIFXAPP: ERROR: InstallDriverPackages failed with error 0x5
The error 0x5 means it is a access denied error message, and I have no idea why this occurs. I am the admin of this machine.
I decided to uninstall Itunes, and to enter Safe mode and try to install it from there.
To go into safe mode, you'll need to reboot and press F8 on the first startup screen. Select Safe mode from the list that appears.
One thing that windows doesn't like is installing things in Safe mode, so we'll need a workaround. There's some tricks using a program called SafeMSI, but this didn't work for me.
I decided to go another route. I created a temp file on my desktop called "Apple Temp". I opened up the AppleMobileSupport.msi from the desktop with the LessMSI program, and extracted the files into this folder.
Now, we are almost done. We now need to copy the files into the proper locations.
1) In "Apple Temp" go into the folder: SourceDir\Common Files\Apple
and copy the "Mobile Device Support" folder
to: C:\Program Files\Common Files\Apple
2) In "Apple Temp" go into the folder: Windows\system32
and copy the 3 files
to: C:\WINDOWS\system32
3) In Apple Temp" go into the folder: SourceDir\Windows\winsxs\Manifests
and copy the 2 files
to : C:\WINDOWS\WinSxS\Manifests
4) In Apple Temp" go into the folder: SourceDir\Windows\winsxs\Policies\x86
policy.8.0.Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_x-ww77c24773
and copy the 2 files
to : C:\WINDOWS\WinSxS\Policies\x86
policy.8.0.Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_x-ww77c24773
5) In Apple Temp" go into the folder: SourceDir\Windows\winsxs\x86
microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none10b2f55f9bffb8f8
and copy the 5 files
to : C:\WINDOWS\WinSxS\x86
microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none10b2f55f9bffb8f8
6) In Apple Temp" go into the folder: SourceDir\Windows\winsx\x86
Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww6b128700
and copy the 3 files
to : C:\WINDOWS\WinSxS\x86
Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww6b128700
7) In Apple Temp" go into the folder: SourceDir\Windows\winsxs\x86
policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none9193a620671dde41
and copy the 2 files
to : C:\WINDOWS\WinSxS\x86
policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none9193a620671dde41
If any of these folders don't exist in c:\Windows, then just create them.
Once that's done, reboot your PC with your iPhone plugged in and re-install Itunes. Itunes will now install all the correct files, and the Apple Mobile Support application will be loaded, and will now also appear in the Add/Remove items list.
Feel free to now delete the Apple Temp folder and the AppleMobileSupport.msi file from your desktop.
There's probably a better workaround, but I couldn't find one. I haven't had a problem yet.
Message was edited by: BadBrad130
Message was edited by: BadBrad130
