Missing or corrupt winload.exe (0xc000000e)
I've encountered several posts regarding WBM issues with dual-boot systems, but I'm experiencing this issue with a single drive/single OS after Ghosting a Vista image to it. The repair process has worked every time, but is there a workaround to avoid it altogether? (using Vista Ultimate on Dell Latitude D820 w/ 80GB SATA HD)
Thanks!
TursiopsTech
Answers
I ran into this problem as well.
On a system I wanted to dump an image to, I would run a diskpart performing these actions: select disk 0, clean, create partition primary, assign letter=c:, active, exit and then format c: /q /y.
After that I booted to PE and ran an imagex /apply from an image located on a server. Every single time I was getting that same error. The issue is that the devices and the osdevice in bcdedit is set to unknown (run bcdedit from a working Vista system and one from PE on a non working Vista system and you will see what I mean).
To resolve the problem, I did these three commands from PE which resolved my problem:
x:\windows\system32\bcdedit /set {default} device partition=c:
x:\windows\system32\bcdedit /set {default} osdevice partition=c:
x:\windows\system32\bcdedit /set {bootmgr} device partition=c:Good luck
All Replies
I ran into this problem as well.
On a system I wanted to dump an image to, I would run a diskpart performing these actions: select disk 0, clean, create partition primary, assign letter=c:, active, exit and then format c: /q /y.
After that I booted to PE and ran an imagex /apply from an image located on a server. Every single time I was getting that same error. The issue is that the devices and the osdevice in bcdedit is set to unknown (run bcdedit from a working Vista system and one from PE on a non working Vista system and you will see what I mean).
To resolve the problem, I did these three commands from PE which resolved my problem:
x:\windows\system32\bcdedit /set {default} device partition=c:
x:\windows\system32\bcdedit /set {default} osdevice partition=c:
x:\windows\system32\bcdedit /set {bootmgr} device partition=c:Good luck
- I had a windos vista home premium os with problems...
I reinstaled from cd and get an gray screen saying error (on red letters)...
After that, i reboot and load vista image from HD.
It installs perfectly... when reboot's i get an error message: (0xc000000e)!
Any ideia why? Add the 3 lines below to Alitirs WINPE script after you have restored the image with imagex to solve the problem:
To resolve the problem, I did these three commands from PE which resolved my problem:
bcdedit /set {default} device partition=c:
bcdedit /set {default} osdevice partition=c:
bcdedit /set {bootmgr} device partition=c:Make sure you use the version of bcdedit that works with your version of WinPE. I copied the Vista RTM bcedit to my WinPE 2.0 script and it worked.
- I've run this command successfully and everything is working fine now. But is there a way to incorporate this into the winpe image so after i apply the image i dont have to do this each time?
Wow, it’s finally fixed! Thank you, I no longer have to use the Vista CD to do the repairs. I added these lines of commands suggested to my batch file that is used to deploy images.
Thank you again,
Brian.
Can you please let me know how did you run the batch file or incorporate it with win pe cd?
If possible ca i have the batch file?
Thanks.
Yes, this solution works. Just 2 comments:
1. From within PE, I had run the commands on the C: drive (Vista), not the X: drive. There was no bcdedit command in X:\windows\system32, but I did find it in C:\windows\system32.
2. I have a dual boot setup with Vista on C: and Windows XP on D:, after running the bcdedit commands listed in your post, i was finally able to boot vista, but not Windows XP. A little further digging revealed that I needed to run another bcdedit command: C:\windows\system32\bcdedit /set {ntldr} device partition=c: (note: the ntldr file is on C: drive, even though Windows XP is on D: drive).
- Works perfectly for a clone produced by Ghost of Windows Server 2008 RC2. Thanks!!
