Resolved Getting copy errors with Windows Component Wizard

When I did a repair install I got many copy errors but I did another one with a freshly burned disc and this time only got one error to copy ICWCONN1.EX_ or ICWCONN2.EX_, one of the two.

I have many components missing so I try to install via appwiz.cpl to install accessories and utilities which are missing but it keeps reporting file copy errors of various, random files on the CD. I copied I386 from the CD to a folder on the HDD but it still refused to accept them. What is going on? The files are not corrupted.

 

Dirty or failing optical drive?

 

I tried using files from the ISO on the HDD and that failed as well. As I said the files are not corrupted. Nothing is wrong with them. I have no idea why windows refuses to accept them.

 

Might want to run RAM and HD diags first.

The Ultimate Boot CD (UBCD) has both (plus much more). Simply boot your computer from this CD and select the utility you want to run.

Note: If you aren't sure who made the hard drive in your computer, use Seagate's Seatools as it will work with most any make of drive.​

The following instructions may prove helpful for burning the UBCD .iso file to disc: How can I write (burn) ISO files to CD or DVD?​

If it passes those two tests, run CHKDSK /R and then a SFC /SCANNOW.

 

I have already done 2 passes of memtest86+ and BurnIn test as well as sfc /scannow. No errors. I get no copy errors on Windows XP inside a VM. I assure you the files are NOT corrupted, the md5sums match the ISO perfectly and nothing is wrong with my HDD. I already did chkdsk /f/r

 

If it's passing hardware diagnostics and Windows' files are perfect, the problem may be due to some type of malware (malicious software). Recommend starting with these instructions and then posting the requested log(s) in our Malware and Virus Removal forum.

After your computer has been given a clean bill of health by one of our malware experts, if you are still having the same issue then please return to THIS thread and we will pursue other options to help solve the problem.

 

Just to update you guys, I've copied my system partition to a VM and tried a repair install there and it's exhibiting the exact same copy error behavior as my physical machine. This proves it's not a hardware problem.

 

If the problem was XP, more than likely there would have been others having the same problem.

 

Believe me I've searched and most of them either got no response or had faulty RAM that needed replacing upon which the problem ceased.

 

Windows XP is, and has been running perfectly on gadzillions of machines.

??? VM or not, it's still the same underlying hardware. And if the hardware isn't 100% perfect, there is no way the software can ever be. Software cannot fix broken hardware.

 

No, there were no copy errors on a fresh install on a VM.

 

. . .

 

My system partition =/= fresh install.

 

And you're still seeing copy errors?

If so, how about in Safe mode?

If so, what about after booting a different OS?

 

On my system partition yes, whether it's here or on a VM. A fresh install doesn't get copy errors however, on a VM anyway but I haven't tried a physical fresh install yet.
Right now I'm following broni's instructions in another thread to check for malware that might be causing it. Yes I think I get the copy errors in safe mode as well but my memory's not clear. I'll try again sometime.

 

Thanks for the update.

 

YES, I was hoping this would give me a clue.

Another update: the problem is with one of the many folders inside C:\WINDOWS but not system or system32. I deleted all folders except those two inside WINDOWS and did a repair install and this time it went smoothly without copy errors.

I'll be rinsing and repeating this until I find the hindering culprit. Because this is a copy inside a VM I can always undo any changes. I'm so relieved that this isn't a problem in the registry or it would've taken forever to fish out.

Stay tuned...

 

Once you get it running right, create a Restore Point and then do a backup.

 

Well I did get it running right but I deleted a huge chunk of WINDOWS to do it and who knows how many necessary drivers, DLLs and system files that all my installed programs might depend on are now gone, so I can't stop here. I went back to the snapshot taken before I did this. This time I'll be removing half the folders I removed the first time. I wanna find out exactly where the culprit is so we'll have a concrete answer to this mystery that's always ignored when it's not a hardware issue.

For once I'll actually contribute to the world of unsolved troubleshooting. Yeehaw.

 

Sounds like a plan.