Winload.exe Corrupt?

  • Thread starter Thread starter Geoff Coupe
  • Start date Start date
G

Geoff Coupe

I'm trying to install Vista Beta 2 on a second hard drive of a Dell
Dimension 8100 system (Intel P4 1.3GHz, 512 MB RAM). The install process
runs fine right up until the very last time when it should boot into the new
Vista. Then, on startup, I get a message from the Windows Boot Manager that
"Windows did not start correctly". Further, it claims that: File
\Windows\System\winload.exe "could not be loaded because the application is
missing or corrupt:." - status: 0xc000000e.

System recovery options fail to clear this fault. Anyone have any clue
what's going on?

Thanks,

Geoff Coupe
 
Could be just a bad install, certain files weren't copied right or were
corrupted. I would format the partition, runch CHKDSK to check for any
errors on the hard disk and reinstall Vista BETA 2.
 
I got this - Andre's right, a Chkdsk actually fixed it for me :o)

--
Zack Whittaker
» ZackNET Enterprises: www.zacknet.co.uk
» MSBlog on ResDev: www.msblog.org
» Vista Knowledge Base: www.vistabase.co.uk
» This mailing is provided "as is" with no warranties, and confers no
rights. All opinions expressed are those of myself unless stated so, and not
of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared
that up!

--: Original message follows :--
 
I get the same problem about winload.exe corrupt or missing. But in my case
the status shown is 0xc000000f.

I'm installing on the second primary partition. I can see from the other
Windows that the files are there. I've tried chkdsk on the partition but it
found no errors and didn't solve the problem.

Please help!!

Best regards,
Mello
 
have the same problem here on a dell dimension 8200, intalled vista on a
partition of my second hard drive, got the same error. burned another dvd
same error, tried to format the partitiion, i couldnt do it. this problem
seems to be more common than i thought, any ideas, thanks
 
While it's nice to see I'm no the only schmoe to be suffering this odd
problem, I would definitely like to see a solution. If I run across one, I
promise I'll share. I read on the Lockergnome's Vista forum that Mike
Bernstein got past this very problem. I have an email directly to him. If I
get a response with a solution, you can count on me to relay the info ...
unless someone posts here.

--Mike.
 
While it's nice to see I'm no the only schmoe to be suffering this odd
problem, I would definitely like to see a solution. If I run across one, I
promise I'll share. I read on the Lockergnome's Vista forum that Mike
Bernstein got past this very problem. I have an email directly to him. If I
get a response with a solution, you can count on me to relay the info ...
unless someone posts it here.

BTW, my Dell 5100 has a SATA as DISK1 (as C:) and a PATA as DISK0 (as E:).
Any reason to think this is the culprit? And a way to get the boot loader to
properly see the other drive?

--Mike.
 
I'm also having this problem ... I suspect a problem related to a combination
of SATA and PATA drives in the system during startup that prevents Windows
Vista from seeing the winload.exe file in time to prevent the error. Does
anyone know how to configure how Vista boots up?

--Mike.
 
Im running a Dimension 8200 system, i have exactly the same problem.
Unfortunately, a chkdsk of my E drive where Vista is installed didnt do
anything... When i boot from the DVD, it always wants to install Vista again.
 
Geoff Coupe said:
I'm trying to install Vista Beta 2 on a second hard drive of a Dell
Dimension 8100 system (Intel P4 1.3GHz, 512 MB RAM). The install process
runs fine right up until the very last time when it should boot into the
new Vista. Then, on startup, I get a message from the Windows Boot Manager
that "Windows did not start correctly". Further, it claims that: File
\Windows\System\winload.exe "could not be loaded because the application
is missing or corrupt:." - status: 0xc000000e.
Click to expand...
OK, Taz found the solution to this (look for the message: "Winload.exe FIX -
For me anyway" posted elsewhere in this newsgroup).

Simply put, my second harddrive was invisible to the BIOS (but not to
Windows XP). Once I put it into the BIOS, then Vista installation completed,
and I had a working dual boot system...

Thanks, Taz...

- Geoff Coupe
 
That's exactly what my problem was. Odd that windows xp can see it but it
wasn't in the bios. I thought my computer was set to autodetect new hard
disks. Thanks!
 
One of the causes is due to having two active primary partitions at the same
time.

--


Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)
 
Back
Top