Long list of files that Windows XP Setup "can't find"

[LuckMan212]

OK I installed XP OEM version on top (in-place upgrade) of my normal retail version by accident (that's a whole other story). Of course I couldn't activate, so I did a re-install of my original XP over the OEM version.

During the re-install, I got errors from Setup saying it needed XYZ file, for about 30 different files. I had to click "Cancel" for all of them, even though they were sitting right there on the CD (I clicked Browse... and the files were all right there!) -- for some reason Setup didn't "like" those versions, maybe it was looking for an OEM version or something?

Anyway here's the list of files it asked for, in the order they were asked for:

MIGREGDB.EX_
ICWCONN1.EX_
ICWCONN2.EX_
INETWIZ.EX_
ICWHELP.DL_
ICWCONN.DL_
ICWUTIL.DL_
ICWRMIND.EX_
ICWDL.DL_
ICWX25A.DU_
ICWX25B.DU_
ICWX25C.DU_
ICWIP.DU_
PHONE.IC_
PHONE.VE_
STATE.IC_
MSICW.IS_
MSN.IS_
SUPPORT.IC_
MSOBSHEL.HT_
ISIGNUP.EX_
ICWTUTOR.EX_
ICWRES.DL_
TRIALOC.DL_
OOBEINFO.IN_
OEMLOGO.GI_
MOUSE.HT_
ISP.HT_
OEMPRIV.HT_

Does anyone know what these are or if they are important? My XP seems to be OK but it sure is annoying to have to click "cancel" 100 times during a setup of XP and I would like to fix the problem somehow.
thanks!!

 

[KGB]

Luck,

Try cleaning the disk the same way you would a music CD.
If that doesn't work, try a different optical drive.
If neither one works, try testing your RAM with Memtest86.

Incidently, never opt to "skip" a file during an install since it can frequently result in an unbootable or borked OS.
It's always better to exit the install, fix the problem and resume installing.

 

[LuckMan212]

Thanks KGB,
I did try cleaning the disk, in fact it was a mint-condition disc straight from my MS Action Pack subscription. I think this problem has more to do with some sort of registry problem than a problem with the media itself, since I was able to verify (CRC-32) all of those files and they all read fine and compare 100% to the original files.

Somehow there is a registry hive or some install document/script that has become damaged by putting on the OEM version. I am just trying to figure out how to fix that without having to scrap my whole installation (which has all my programs and settings just how I want them) which would take weeks to get back.

I agree with you in general about "skipping" files, however I was left with absolutely no choice. By that point in the install, there was no "going back" option.

 

[orion23]

You should not skip any files, and I'm actually surprised that the installation went through.
I've had similar issues while installing windows and have resolved them by using multiple copies of the same disc, (just replace it everytime it fails) or by using a different CD-Rom.
Hope that helps!

 

[tami]

surprisingly, that may be a RAM issue, but don't be too certain. try another stick of RAM in place of the current ones to see if the installation brings up any errors.

it may be ideal for you just to back up essential files and to do a clean reformat/reinstall.

 

[lenjack]

i've seen on the MS knowledge base something like this. the recommendations were fuzzy, but here's some of them. If you have 2 cdrom's disconnect one of them. the installation may be confused as to which cdrom to read. Only use 1 stick of RAm. Try without overclocking.

I had this problem...the above advice worked.