This discussion is locked
-
All replies
-
Helpful answers
Previous
Page
2
-
Jan 22, 2010 9:02 PM in response to grimes7by b noir,This all started last week. With the iTunes icon that was on my desktop, I double-clicked it to open it, as I had done thousands of times before, and iTunes would not open. The next day, when I turned my computer on, the iTunes icon was replaced by the iTunes setup icon. When I double-clicked on that, it tried to install iTunes as if I had never had iTunes. This is when the error 2330 began.
Got it! Thank you grimes. That tells us it was an iTunes program file that got damaged. (The iTunes shortcuts are special shortcuts known as advertised shortcuts ... the first thing they do when you click them is check against the installation database in the iTunes.msi to make sure no files and registry entries and whatnot are missing. If it it finds something missing it does a repair install of iTunes.)
So we've got a workaround, although it isn't going to be pretty.
Go "Start > Computer". In Open Local Files C or whatever drive your program files are installed on. Open the Program files folder. Rename the iTunes folder "iTunesOld".
Now go into your start menu again, and launch iTunes from there. That should provoke it to do a repair install of itself again. (Just tested on my XP PC.) Bevause the iTunes folder has been renamed, the installer will not try to remove the files in the old folder ... and it shouldn't get hung up on the file damage this time.
Does the repair install go through properly this time? -
Jan 23, 2010 6:22 AM in response to b noirby grimes7,b noir,
I don't know how to begin to thank you for all of your continued support over the past couple of days. With your help, I am now back into iTunes....and all seems to be working well.
Thanks again!!!!! -
Jan 23, 2010 10:57 AM in response to grimes7by b noir,Excellent news, grimes.
One remaining worry ... I don't like the way there's disk/file damage on the PC that your disk check isn't able to fix. I think it'd be a good idea to back up your data just in case, and keep an eye out for any further symptoms of drive damage. (Fingers crossed, this was just a one-off thing, but the worry is always of an evolving Hard disk problem. So best to be safe rather than sorry.)