Setup Cannot Copy the file: shell32.dll

[Dale Gore]

Just curious if anyone has run across this setup problem:

I have an ASUS A7N266 with PC133 memory, 256mb. A 48X
CDROM, 40GB HD. The machine came up with a virus and
nothing would work. So I first fdisked the machine and
began the XP PRO install all over.

Goes like clockwork until it begins copying files. At 2%
the message Setup Cannot Copy the file: shell32.dll pops
up. I've changed CDROM drives, the memory, the hard
drive, removed all cards except the video, updated the
BIOS.

Any suggestions would be helpful.

Thanks,
Dale

 

[Dale Gore]

The solution to this problem is:

After many hours of tinkering, it's memory!!! Hardware
problem. I replaced the memory, and bingo no more
problems.

Always pays to go with Kingston. Free replacement if
it's bad.

Hope this helps anyone else if they have this same
problem.

 

[Guest]

My MB is an Abit BP6 with Dual 466Mhz Celerons, 768 MB RAM, pair of WD 160GB
HD running W2K3 Server Ent Ed since Beta 1 for two years. I have had the
final realease running for the past 8 months. I come home one day and find
my server saying it can find shell32.dll. I was getting BSODs after several
reboots. I tried the ASR several time without luck at recovering the system.

I hope is is just a matter of replacing the memory. I will follow up very
soon if it is so. I hope I can just pop out the bad chip and recover the ASR
files and have my server back.

 

[Guest]

Dale, you were right! I found one of my modules was not inserted all the
way. I press it to click in, but I still had a problem. So I removed it and
Windows was able to complete its startup installation.

I had a 128MB module laying around, so I installed that in place of the
256MB and I am in the process of using the ASR to recover my installation.

I am very happy that you shared your experience with us. It saved me from
scratching a hole in my head. Funny how the error message didn't mention
anything about it could be a bad memory module?