Unsolved
This post is more than 5 years old
5 Posts
0
26012
November 9th, 2005 16:00
replace corrupt .dll file via Recovery Console?
Dimension 3000, 3GHz, 512, WindowsXP Home
I have a "STOP" error ("Bad Image Checksum - the image Ole32.dll is possibly corrupt") that prevents me from booting to Windows in ANY mode (unless there's some way to bypass the .dll verification step in the boot process). So I'm trying to replace the suspect Ole32.dll file, as suggested in a Microsoft support article.
After getting to the Recovery Console command prompt and the Windows directory, there are two steps: rename the corrupt file, and then replace it with a good file from the WinXP CD.
I think I understand the first step:
cd windows\system32
ren ole32.dll ole32.old
The 2nd step, I don't know. Does this string make sense:
extract d:\386\ole32.dll_c:\windows\system32\ole32.dll
--Would that copy the file from the WinXP CD in the d drive to the windows\system32 directory on the c drive? I didn't see "extract" in the list of Recovery Console commands. Here's where I got my info: http://support.microsoft.com/default.aspx?scid=kb;en-us;326687&Product=winxp . It's not the exact same situation, but close. Can one of you codeslingers verify that for me?
It would be great to be able to boot to Windows and just use System Restore, but I don't see any way to do that. It won't boot into either Safe Mode or Safe Mode With Command Prompt.
Thanks!
By the way, the error occured after installing the latest Windows Update patches. My computer crashed and restarted during the first attempt at downloading. 2nd attempt succeeded. That shouldn't have affected the install, since it was only the download that was interrupted (not the install), and all downloads were verified before patches were installed--but maybe it did??
I have a feeling I'm going to be reinstalling WinXP :(
I have a "STOP" error ("Bad Image Checksum - the image Ole32.dll is possibly corrupt") that prevents me from booting to Windows in ANY mode (unless there's some way to bypass the .dll verification step in the boot process). So I'm trying to replace the suspect Ole32.dll file, as suggested in a Microsoft support article.
After getting to the Recovery Console command prompt and the Windows directory, there are two steps: rename the corrupt file, and then replace it with a good file from the WinXP CD.
I think I understand the first step:
cd windows\system32
ren ole32.dll ole32.old
The 2nd step, I don't know. Does this string make sense:
extract d:\386\ole32.dll_c:\windows\system32\ole32.dll
--Would that copy the file from the WinXP CD in the d drive to the windows\system32 directory on the c drive? I didn't see "extract" in the list of Recovery Console commands. Here's where I got my info: http://support.microsoft.com/default.aspx?scid=kb;en-us;326687&Product=winxp . It's not the exact same situation, but close. Can one of you codeslingers verify that for me?
It would be great to be able to boot to Windows and just use System Restore, but I don't see any way to do that. It won't boot into either Safe Mode or Safe Mode With Command Prompt.
Thanks!
By the way, the error occured after installing the latest Windows Update patches. My computer crashed and restarted during the first attempt at downloading. 2nd attempt succeeded. That shouldn't have affected the install, since it was only the download that was interrupted (not the install), and all downloads were verified before patches were installed--but maybe it did??
I have a feeling I'm going to be reinstalling WinXP :(
No Events found!
Denny Denham
2 Intern
•
18.8K Posts
0
November 9th, 2005 16:00
The command to enter in Recovery Console is:
expand d:\i386\ole32.dl_ c:\windows\system32\ole32.dll
Note that there is a space between dl_ and c:\ and I assume that d:\ is your CD-ROM drive.
isthatso
5 Posts
0
November 9th, 2005 17:00
Thanks, I'll try it! Thanks for spotting the typos--but why is one "l" dropped in the first reference to ole32.dll?
Denny Denham
2 Intern
•
18.8K Posts
0
November 9th, 2005 19:00
The copy of the file in the I386 folder is compressed. If you check the contents of that folder, nearly all the files are compressed and have their extension ending in the _ character (replacing the normal final character). The notable exceptions are a few *.inf files. To expand the file you need to refer to it by its name (which in your case ends in .dl_).
isthatso
5 Posts
0
November 13th, 2005 14:00
The "expand" command didn't work; Recovery console was "unable to create file." Substituting "copy" for "expand" *did* work. It turns out that in Recovery Console (the 2005 version anyway), the copy command automatically decompresses compressed files on the WinXP setup CD. Cool!
So, I was able to replace the bad ole32.dll file, which enabled me to boot into Windows, but unfortunately, it was a sad and crippled Windows, with no printer access, no Internet, not even a taskbar at the bottom of the screen. So there were other issues besides the bad ole32.dll file.
System Restore was not available, so I ran the Windows setup CD and chose the "repair" (rather than clean install) option. I don't know what that does--probably restored a lot of the original system files. It left all my data intact and programs installed. So far so good; I haven't had any problems in the last few days.
-isthatso