Member Avatar for nydana8

shell32.dll possibly corrupt error

--------------------------------------------------------------------------------

I have just performed a clean reinstall of Windows XP Pro service pack 2 and am getting the following error:

C0000221 {Bad Image Checksum}
The image shell32.dll is possibly corrupt.
The header checksum does not match the computed checksum.

I used a Dell reinstallation CD and I just realized that my PC is probably not a Dell. I do not know if this has anything to do with it.

What do I have to do?

Thanks a lot for a lifesaver help!

P.S. Before I had XP Home service pack 2.
P.P.S. I have a few PC's in a network, so I can use the others to copy files or whatever.....

  • 3 Contributors
  • 2 Replies
  • 395 Views
  • 7 Months Discussion Span
  • Latest Post Latest Post by maddogPC

Dani AI

Generated

The C0000221 "Bad Image Checksum" for shell32.dll means Windows detected that the stored header checksum does not match the file as it exists on disk. That points to a damaged or mismatched system DLL rather than a simple configuration issue. Common root causes are corrupted install media, using OEM recovery media that doesn't match the machine, disk or RAM errors that corrupt files, or an incorrect replacement DLL from a different build.

Start with the least-destructive checks and work outward. Confirm the installation source exactly matches the installed Windows edition, service pack, language and CPU architecture (OEM recovery discs are often customized; a Dell restore image can carry vendor-specific binaries that may not be compatible on non‑Dell hardware). Run Windows’ offline repair/restore routine from recovery media to attempt automatic replacement of bad system files. If manual replacement is tried — as did — make sure the replacement DLL is an exact build match; replace the file from an offline/recovery environment (not from a running Windows session) and keep a backup of the original.

Also rule out hardware: run a full disk surface check and a memory test; transient corruption from failing RAM or a dying drive can repeatedly recreate checksum errors even after replacing the DLL. Because suggested using install media, that is the right direction — use media that exactly matches the OS on the machine rather than a mismatched vendor CD.

If repair attempts fail, the most reliable remedies are a repair install or a clean reinstall using correct, matching installation media. Given that other PCs are available on the network, use one of them only to verify exact file version/locale or to source the correct media; do not substitute a DLL from a machine with a different edition, service pack, language or architecture.

Recommended Answers

All 2 Replies

Member Avatar for jbennet

boot into safemode
put in any xp disk of the same service pack and edition

type " sfc /scannow " (without the speech marks of course) into the run box and wait. reboot back in to normal mode when it completes.

it will check for corrupted files and replace them with ones from an safe file store inside the PC or , if they are also corrupt, from the CD.

Member Avatar for maddogPC

Hey nydana8, I had the same problem, heres what I did:
I have a working version of the same operating system, so I took the dll file from my computer and put it on a jump drive(make sure you write down the path where the dll file is). Then, I used the recovery disk from the install disk to go into recovery mode. Then, I used the copy command as follows: copy (directory of file on jumpdrive) (directory of file on the computer) and then I allowed it to overwrite the other one. Everything's running smooth now.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.