Yeah, if it changed, let it keep running. It may say that it could not fix the problem when it finishes. Ignore that message, then run it again by clicking the x and starting the startup repair again. Even if it says it didn't find any problems the second time, run it a third time. Hopefully that will fix the issue.
Status: 0xc0000000e
This error I had after moving a partition with GPARTED. I think C-partition is visible now in diskpart and type=ntfs
You can even do: DIR C:
anyway perfoming a chkdsk will fix the problem. After chkdsk start your windows normally. not starting? try startup repair again
don't do bootrec.exe /RebuildBcd because this rebuilds your bootmenu and maybe you lose some options in bootmenu. Please post results
from recovery environmet (or from within windows, elevated command prompt)
bcdedit /enum all
Does bootmgr display the red items? and current (or default) as well? check all items I marked red
=============
Windows-opstartbeheer
---------------------
id {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale nl-NL
inherit {globalsettings}
default {current}
resumeobject {fa1a7f9d-ab26-11df-bc4f-ce7145d50d35}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 10
Windows-opstartlaadprogramma
----------------------------
id {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium
locale nl-NL
inherit {bootloadersettings}
recoverysequence {fa1a7fa1-ab26-11df-bc4f-ce7145d50d35}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {fa1a7f9d-ab26-11df-bc4f-ce7145d50d35}
nx OptIn
Windows-opstartlaadprogramma
----------------------------
id {fa1a7fa1-ab26-11df-bc4f-ce7145d50d35}
device ramdisk=[C:]\Recovery\fa1a7fa1-ab26-11df-bc4f-ce7145d50d
35\Winre.wim,{fa1a7fa2-ab26-11df-bc4f-ce7145d50d35}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\fa1a7fa1-ab26-11df-bc4f-ce7145d50d
35\Winre.wim,{fa1a7fa2-ab26-11df-bc4f-ce7145d50d35}
systemroot \windows
nx OptIn
winpe Yes
Hervatten uit sluimerstand
--------------------------
id {fa1a7f9d-ab26-11df-bc4f-ce7145d50d35}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale nl-NL
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No
Windows-geheugentest
--------------------
id {memdiag}
device partition=C:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale nl-NL
inherit {globalsettings}
badmemoryaccess Yes
EMS-instellingen
----------------
id {emssettings}
bootems Yes
Debugger-instellingen
---------------------
id {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200
RAM-defecten
------------
id {badmemory}
Globale instellingen
--------------------
id {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}
Instellingen voor opstartlaadprogramma
--------------------------------------
id {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}
Hypervisor-instellingen
-------------------
id {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200
Instellingen voor hervattingslaadprogramma
------------------------------------------
id {resumeloadersettings}
inherit {globalsettings}
Apparaatopties
--------------
id {fa1a7fa2-ab26-11df-bc4f-ce7145d50d35}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\fa1a7fa1-ab26-11df-bc4f-ce7145d50d35\boot.sdi
I ran one round of Startup Repair, rebooted, and got the same error, so I loaded the recovery disc intending to run Startup Repair for a second time. Only now, after two tries, the disc hasn't been able to get past the black screen with a cursor that shows after the "Windows is loading files..." screen. Once it did eventually load the blue Windows background and "Choose a language" screen, but then nothing. I let it run for 20 minutes and came back, and the screen was the same. The disc drive had stopped making noises and no light was coming from it. I didn't know whether that meant I had to wait longer or it had stopped working, but I ended up shutting down the computer. It used to be slow, but not THIS slow...maybe 5-10 minutes between loading the next screen.
So now I can't load the recovery disc or access any of the Recovery options. What happened? Is it just a matter of it loading extremely slowly, and I should wait longer? Do I need to let the computer sit for a while and cool down?
Does this mean you cannot startup from dvd??? Use another bootdisk some livecd does it start?
If you can start try to enter "command prompt" and do DIR C:
OK, given that my recovery disc has consistently spun up/spun down and stalled at the beginning the past three times I've tried it, and pressing F8 repeatedly at boot to try to access Recovery Options from my PC isn't working anymore, I guess I'm stuck. I have to go to work now, but when I come back I'll try to see if a USB stick or something else can load. Is it possible running Startup Repair corrupted the recovery CD, or was it just coincidence? Ugh, this has been unbelievably frustrating.
startup repair CANNOT corrupt a readonly cd.
What do you see exactly when booting from dvd? And please check if dvd isn't damaged. for example try to start from it in another pc.
Did you open the computer case and touched the cables?
The disc cannot be corrupted, but it may have been physically damaged. I would check to see if any deep scratches appeared or if there is excessive dust on it. You may have to clean it using the appropriate tools. You need a cloth that is meant for cleaning eye glasses or camera lenses, or a cloth specifically for cleaning discs. Then you have to wipe from the middle of the disc to the outside (never wipe in circles on a disc, straight lines from the middle to the outside).
If it is not the disc, then I have a suspicion that there is something wrong with your hard drive because the windows files are loaded from the disc to the drive when you boot from the disc. Have you run a chkdsk as suggested by Kaktussoft? If not, we will have to find a way to get a command prompt open.
Quote