(1) Download the Windows Installer CleanUp utility installer file (msicuu2.exe) from the following Major Geeks page (use one of the links under the "DOWNLOAD LOCATIONS" thingy on the Major Geeks page):
(2) Doubleclick the msicuu2.exe file and follow the prompts to install the Windows Installer CleanUp utility. (If you're on a Windows Vista or Windows 7 system and you get a Code 800A0046 error message when doubleclicking the msicuu2.exe file, try instead right-clicking on the msicuu2.exe file and selecting "Run as administrator".)
(3) In your Start menu click All Programs and then click Windows Install Clean Up. The Windows Installer CleanUp utility window appears, listing software that is currently installed on your computer.
(4) In the list of programs that appears in CleanUp, select any iTunes entries and click "Remove", as per the following screenshot:
(5) Quit out of CleanUp, restart the PC and try another iTunes install. Does it go through properly this time?
I would like to take a moment to point out that though this is a great little program made by microsoft that they have discontinued the use of this items as in some confirgurartion this can cause issues when uninstalling items ither than MS office products. See this link.
as in some confirgurartion this can cause issues when uninstalling items ither than MS office products.
No, you've gotten that completely the wrong way round. It caused trouble when uninstalling certain models of Office products (especially Office 2007, and possibly 2010). Note carefully that the article does not say it causes trouble when used with programs other than Office. It directs people trying to uninstall/install other products to a different Fixit than the ones listed on that page.
I am not discouraging the use of this software but as a former HP technical support representiative who used this software on a daily basis I can assure in very specific situations this program has cause registry damage while I would agree rare in most situations. When used on hundreds of calls you tend to run into it. I say use it if you feel like, I do, but I would caution people to back up your registry just in case. In all likely hood nothing will happen but really why risk it. I will admit that I was unaware that it affected office products and added that based on the KB article but otherwise the other situations where based on first hand experience. I always caution anyone making any major change in software to make backups.
I am not discouraging the use of this software but as a former HP technical support representiative who used this software on a daily basis I can assure in very specific situations this program has cause registry damage while I would agree rare in most situations. When used on hundreds of calls you tend to run into it.
I have also used this in thousands of circumstances since 2005, on a daily basis. It's easy enough for you to check on the boards here to see that I've done that (although forum software changes mean that some of the various earliest 2005 and 2006 posts are no longer accessible). So if we're getting into a "credentials and competence with usage of CleanUp" debate, I'd suggest that at the very least we're on par in terms of experience, and equally capable of making considered judgment calls.
If you're worried about the UNKNOWN\Components\ complication that appears for some folks after they've tried getting past a problem using Cleanup, you can typically clear up afterwards with the method from the following user tip:
... but note that that issue can occur independently of folks using CleanUp. (My instructions in there are basically variations on other instructions on the web that have been around for a long time, too.)
I will have to admit I was not aware of that particular user tip and would like to thank you for taking the time to further educate me. I think that your experience with this software and iTunes is likely greater than mine as most of my experiences do come from machines that are usally running business applications and likely iTunes would not have been present on these machines. Thanks again have a great day.
I will have to admit I was not aware of that particular user tip and would like to thank you for taking the time to further educate me.
Full disclosure ... for a year or so, I thought the UNKNOWN\Components message was a totally miserable problem. Most treatment methods involved variations on the "Further steps" section ... but it was a low-percentage play at the best of times.
It wasn't until folks reported that adjusting the Ownership (instead of just the permissions) was working, that we suddenly had a high percentage play.
It looks like there's three classes of the error message (and underlying issue):
(1) One that responds to the Ownership change (most common variant)
(2) One that responds to the Permissions change, but not to the Ownership change (rarer)
(3) One that doesn't respond to either Ownership or Permissions changes, but sometimes does respond to the new Microsoft downloadable fixit (rarer)
It's not clear whether 2 is rarer than 3 or 3 is rarer than 2. Number 3 can be tricky to deal with, because the error might be being thrown by other components in the iTunes installer bundle than iTunes (for example, AMDS). It can also be thrown on the uninstall or install phase with any of the components, so which mode of the fixit we use might also have some impact on treating it ... unfortunately, there's more study to be done before we can get a proper handle on 3.