Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

WINLOAD.EXE Problem


  • Please log in to reply

#1
NTxC

NTxC

    New Member

  • Member
  • Pip
  • 3 posts
Hello to all!
I'm new here.
I bought Windows Vista Ultimate yesterday.
I installed it today, but it can't boot.

I have one HD, Western Digital Caviar 200GB. I have two partitions - C:, where XP Pro resides, and D:, where I wanted to install Vista. I run the Vista Setup, then I choose "Clean installation" as the method of installation, I choose drive D:, etc. and it started to install. After installing it rebooted. When I try to boot Vista it complains about a missing or corrupt \Windows\system32\winload.exe, error 0xc000000f (or sometimes 0xc000000e).

What the problem is? :whistling: Please help if you can.

Cheers!

EDIT: I want to have dual-boot so I can choose XP or Vista to run from list at the computer startup.

Edited by NTxC, 20 June 2007 - 09:17 AM.

  • 0

Advertisements


#2
starjax

starjax

    Global Moderator

  • Global Moderator
  • 6,646 posts
take a look at this thread: http://forums.techgu...st-xp-home.html
specifically post #2.

This will allow you to check your boot manager to verify if it is configured properly.

From what I have been reading, there are issues with dual booting xp and vista. Please post your results so we can what else may need to be done.
  • 0

#3
NTxC

NTxC

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts
Hi Starjax
'Device' and 'osdevice' settings under 'Windows Boot Loader' part are set as they are supposed to be.

BCDEdit results:

Windows Legacy OS Loader
------------------------
identifier {ntldr}
device unknown
path \ntldr
description Earlier Version of Windows

Windows Boot Loader
-------------------
identifier {default}
device partition=D:
path \Windows\system32\winload.exe
description Microsoft Windows Vista
locale en-US
inherit {bootloadersettings}
osdevice partition=D:
systemroot \Windows
resumeobject {6726b3f1-1f91-11dc-ab69-ae0b82821ccb}
nx OptIn
detecthal Yes


Do you recommend installing a third-party bootmanager? Which do you recommend?
  • 0

#4
gumby701

gumby701

    Member

  • Member
  • PipPip
  • 72 posts
Mmm, but this isn't:

identifier {ntldr}
device unknown

I don't remember what to do about that...at least you didnt delete winload.exe like me, out of frustration.
  • 0

#5
NTxC

NTxC

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts
The unknown parameter is in Legacy OS Loader (section which loads XP). XP is working properly, but Vista shows dumb 0xc000000f (of 0e) error. Looks like I wasted my money on Vista. :whistling:
  • 0

#6
starjax

starjax

    Global Moderator

  • Global Moderator
  • 6,646 posts
well this is what I would do if I wanted to run dual boot:

install vista on the primary © drive. install xp on a secondary hard drive (d).

Point I'm making is that everyone who I saw having this issue tried putting vista on a different drive than c. That seems to be the common thread.

those that had it installed on c either were using a beta version or a cracked copy of vista.

This was culled from doing searching via google.


Another option is to consider running an os in a virtual environment using Microsoft virtual pc: http://www.microsoft...pc/default.mspx

I personally bit the bullet and got Vista Ultimate 64bit version. I haven't run into any compatability issues with any of the software and games that I play.
  • 0

#7
gumby701

gumby701

    Member

  • Member
  • PipPip
  • 72 posts
mmm try changing

path \Windows\system32\winload.exe

to

path \Windows\system32\boot\winload.exe
  • 0

#8
gumby701

gumby701

    Member

  • Member
  • PipPip
  • 72 posts
Really, that's what worked for me...until my HDD decided to die on the next reboot....but that was a cause of the problem, most likely. I dont think changing the BCD will hurt your HDD.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP