How can I repair a Vista winload.exe boot error?

I have a Windows Vista installation that is giving the below error upon booting.  I've saerched both EE and Google, EE doesn't seem to have much on the topic.  Google has a few things I'm trying now, but I'm wondering if a fellow EE member can chime in and point me in the right direction?  Thanks in advance


Windows Failed to start. a recenent hardware or software change may be the cause. to fix this problem:

(boot from the cd and repair windows) (doesnt actually say that but thats what it tells ya to do)

File: /windows/system32/winload.exe

Status: 0xc0000221

Info: the file is possibaly corupt. its header checksum does not match the computed checksum.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Yes, if you boot from the Vista DVD, you can get into the Recovery Environment, which is Vista's replacement for the old XP Recovery Console, and then you could go into the Command Prompt section of the RE, and use the DOS copy command to put a good copy of winload.exe on your hard disk.  Since the files are not stored in compressed form in an I386 folder as they were in XP, however, you would need to obtain a copy of the file from a computer that is working ok and put it on a floppy disk or a USB stick, for example.  See this tutorial on using the Command Prompt in the Vista Recovery Environment:
How to use the Command Prompt in the Vista Windows Recovery Environment
JsmplyAuthor Commented:
Does it matter which version of Vista I pull it from?  IE: Home basic to Ultimate, etc?  I did some googling on the issue and most of the results said the file is not actually corrupt, but Windows is referencing it wrong and can be repaire via bcdedit.  However, I'm more inclined to trust you from EE.  

JsmplyAuthor Commented:
Tried the copy, it didn't work though.  I also checked and the path is correct in bcdedit.  Any other ideas?

Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

I found this Previously Answered Question on the same error message where the problem was bad memory:
Checksum Error when Vista Boots
JsmplyAuthor Commented:
Okay, after messing around with bcdedit I was able to fix the first error, but now I get the same black screen and same error message but with the file


Could that many files really be messed up or is this a bigger issue?  

I will test the memory for the fun of it, thanks.
With multiple module names coming up like that, I would expect it might be either your memory or the hard disk. You can check the memory with the built-in diagnostic from the Recovery Environment of Vista on the DVD.  For the hard disk:  I would suggest running a disk diagnostic utility. Most disk vendors have these for free. 

For example:


Western Digital

The diagnostic tools are usually going to have to be written to a floppy disk.  If you don't have a floppy drive available (even a cheap USB one) or cannot boot to one, then you could try the diagnostic tools on The Ultimate Boot CD:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JsmplyAuthor Commented:
I'm running memtest now. I assume that's as good as the Windows memory test on Vista?  I will test the hard drive next.
JsmplyAuthor Commented:
Okay it passed Memtest but Seagate diagnostic test found lots of errors, 20 + errors within 30 seconds of running their long test on the hard drive.  

I assume it's not worth repairing.

It's pretty strange, this laptop has had the hard drive changed once before and this customer has had me change hard drives on two other laptops they have had as well.  They seem to be a curse to laptop hard drives.  I know sometimes drives just go bad, but what else can cause this?  Could it be them being rough with the laptop while the drive is in use?

>They seem to be a curse to laptop hard drives.
>Could it be them being rough with the laptop while the drive is in use?

Who knows?  I sure would be expecting some sort of answer like that given their past history...
Jsmply, is your question answered?
JsmplyAuthor Commented:
Yes, thank you!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Vista

From novice to tech pro — start learning today.