Windows failed to start - 0xc000000e -AutoRepair doenst help

[syr]

Hello,

I'm using:
Windows 7 Pro 64Bit
for a while without a problem.
After creating a backup of an external hdd using acronis true image 10 I get the folllowing error when booting from the internal HDD that worked for years:

Windows Boot Manager:
Windows failed to start. A Recent hardware or software change might be the cause. To fix the problem:

1. Insert your windows installation disc and restart your computer.
2. Choose your langugae settings, and then click next
3. Click "repair your computer."

Status: 0xc000000e
Info: The boot selection failed because a required device is inaccessible.


So I tried differnent things people advised here and in other forums.


Booted from Windows7-DVD and proceeded to "Repair My Computer"

The OS found was named as "Windows7 (recovered)"

After doing Auto-Repair (several times) the startup error still persists.


In the Win7 debug shell I tried:
chkdsk /f and got:

"file system is NTFS.
the current drive cannot be locked.
checkdisk cannot be executed on this volume because it is write protected."


After that I also tried:

bootrec.exe /FixMbr
bootrec.exe /FixBoot

Also didnt help.


What to try next?

 

[gregrocker]

Work through these steps for Troubleshooting Windows 7 Failure to Boot - Windows 7 Forums.

I'd check first if Win7 partition or it's 100mb System Reserved partition (preferred) is still marked Active as it must be before running Startup Repair - Run 3 Separate Times to repair the boot. Then cover the other steps in tutorial.

 

[karlsnooks]

syr,
You won't like my answer but here is the solution:
Full and complete uninstall of Acronis.
Restore,using a system restore point, to a point before the installation of Acronis.
Do not use Acronis.
Use Windows 7 Backup and Restore to make a full image backup.

There may be an outcry against my recommendations, but I have a trump card: My recommendation works!

 

[syr]

Work through these steps for Troubleshooting Windows 7 Failure to Boot - Windows 7 Forums.

I'd check first if Win7 partition or it's 100mb System Reserved partition (preferred) is still marked Active as it must be before running Startup Repair - Run 3 Separate Times to repair the boot. Then cover the other steps in tutorial.

I just tried PartitionWizard which prints for the concerned Win7 HDD:

Partition: D:System reserved
capacity: 800 MB
used: 28,44 MB
unused: 771,55 MB
file system: NTFS
type: primary
status: active

Partition: E:
capacity: 1862,23 GB
used: 1862,23 GB //comment: that's definitely not correct
unused: 0 B //comment:also not correct
file system: NTFS
type: primary
status: none

It's strange that the system reserved partition is mounted and mapped to a drive letter. Opening D: shows an empty drive, opening E: shows an error message "Cannot access E:\ - The file or directory is corrupted/damaged or not readable"

So what further steps would you propose?

 

[syr]

syr,
You won't like my answer but here is the solution:
Full and complete uninstall of Acronis.
Restore,using a system restore point, to a point before the installation of Acronis.
Do not use Acronis.
Use Windows 7 Backup and Restore to make a full image backup.

There may be an outcry against my recommendations, but I have a trump card: My recommendation works!

Did you take into account that the drive that cannot be booted now wasn't involved in the backup process using acronis?

I just made a backup of an external USB drive to another disk from which I can still boot from.

The restore point would be maybe an option if there was one created automatically.

 

[gregrocker]

I thought Win7 could not boot, so if you're booting PW CD then there should be no drive letters. Also any drive letters in WinRe are not necessarily the same as in Windows.

Did you try running Rebuild MBR from PW Disk tab as suggested in Troubleshooting steps? If this fails did you run Startup Repair 3 separate times with reboots?

Was infection found? What is the result of running SFC from Command Line in System Recovery Options? You must work through every step to know that everything has been done.

Do you have your files copied out and are prepared to Clean Reinstall?

 

[syr]

oh sorry for confusing..I booted from another HDD where XP is installed

I will work through the troubleshooting page when I got some time.

Thanks for the guidance

EDIT: Just executed PW's check disk that prints "master file table damaged..chkdsk aborted.."
sounds bad

 

[gregrocker]

Post back a screenshot of XP Disk management and/or Partition Wizard drive map and listings:
Screenshot with Paint
Screenshots and Files - Upload and Post in Seven Forums - Windows 7 Forums

You must run the repairs on Win7 with all other HD's unplugged, until it starts on its own. Then you can plug back in XP and boot it using the one-time BIOS Boot Menu key or install EasyBCD to Win7 to add XP on Add OS Entry tab.

 

[syr]

The repairs I did with only the win7 HDD plugged in.

screenshots

http://dl.dropbox.com/u/34369176/hdd1.PNG
http://dl.dropbox.com/u/34369176/hdd2.PNG

P.S. note my previous post as we submitted in sync.

Thanks

 

[gregrocker]

The System boot files are not on the Win7 100mb System Reserved partition as they should be and would be if it were labeled System as is the XP partition. This may mean that XP partition was booting Win7 in a Dual Boot and has stopped doing so.

But with separate HD's it's better to have each HD self-bootable with the System boot files on the OS partition - or in the case of WIn7 it's 100mb System Reserved partition, providing it hasn't become corrupted itself.

For this reason you should unplug the XP HD which will boot on its own and work through the full set of steps for Troubleshooting Windows 7 Failure to Boot - Windows 7 Forums since nothing can be ruled out including infection, corruption of System Reserved, et al.

 

[syr]

The System boot files are not on the Win7 100mb System Reserved partition as they should be and would be if it were labeled System as is the XP partition. This may mean that XP partition was booting Win7 in a Dual Boot and has stopped doing so.

But with separate HD's it's better to have each HD self-bootable with the System boot files on the OS partition - or in the case of WIn7 it's 100mb System Reserved partition, providing it hasn't become corrupted itself.

For this reason you should unplug the XP HD which will boot on its own and work through the full set of steps for Troubleshooting Windows 7 Failure to Boot - Windows 7 Forums since nothing can be ruled out including infection, corruption of System Reserved, et al.

I can assure that each hdd is independly self-bootable as I could boot from every single plugged HDD (HDD1 -> WinXP, HDD2 -> Win7)

Btw. you gave me the advice (1-2 years ago) to open drive selection prior boot to select the hdd to boot from because I had problems setting up multi boot.

I will go through the troubleshooting next time

 

[gregrocker]

In that case it may be a reporting anomaly from PW Home (installed) edition and Disk Mgmt as seen from XP. How is it seen from Win7?

There should absolutely be both System + Active flags on the System Reserved partition which is abnormally large for some reason?

 

[syr]

In that case it may be a reporting anomaly from PW Home (installed) edition and Disk Mgmt as seen from XP. How is it seen from Win7?

There should absolutely be both System + Active flags on the System Reserved partition which is abnormally large for some reason?

As I have only a Win7 Laptop I plugged it in using external case via usb3.

Here what I see:

http://dl.dropbox.com/u/34369176/[email protected] (Datenträger 1)
http://dl.dropbox.com/u/34369176/hdd%407-2.png (Disk 2)

 

[gregrocker]

It doesn't say which Disk is attached externally so I'm assuming it is Disk 1 since it has the 800mb jumbo System Reserved partition.

Attach only that HD internally to the problem machine, boot the Win7 DVD or System Repair Disk
to run Startup Repair - Run 3 Separate Times until System Reserved is marked System Active and boots.

It is not going to start unless you have the system flag on either the SysReserved partition or Win7 partition.

If it fails after three separate Startup Repairs to repair or rewrite the System boot files to System Reserved partition, then mark Win7 partition Active and run the Repairs again: Partition - Mark as Active (Method Two). It's possible the unusually large System Rserved partition is corrupt.

 

[syr]

It doesn't say which Disk is attached externally so I'm assuming it is Disk 1 since it has the 800mb jumbo System Reserved partition.

I wrote the concerned hdd behind the links to the screenshots in my previous post

Attach only that HD internally to the problem machine, boot the Win7 DVD or System Repair Diska
to run Startup Repair - Run 3 Separate Times until System Reserved is marked System Active and boots.

Did that...even 4 times..still can't boot...So I will try "Mark as active method" tomorrow.



Btw. I also tried the windows "shell" and pasted here (roughly translated) what was printed to the prompt

> bootrec.exe /FixMbr
command finished

> bootrec.exe /FixBoot
command finished

> bootrec.exe /ScanOS

all drives were scanned for Windows installations.
found windows installations: 0

That was surprising as there is always a windows7 installation (recovered) displayed when entering startup repair.

 

[gregrocker]

If the OS shows up in Repair window then there's no reason to run bootrec commands as they are automated along with dozens of other test, fixes and commands in Startup Repair.

 

[karlsnooks]

syr,
Something isn't jiving here (in other words, there are inconsistencies).
use following procedure.
Do NOT use dropbox, use this procedure to upload your snapshot.
HOW TO POST A SNAPSHOT OF DISK MANAGEMENT DISPLAY
Run disk management:
WIN | type DISKMGMT.MSC | ENTER
WIN=key with Microsoft logo on top.


Maximize the output of Disk Management:
ALT-Spacebar key combo | X key (selects Maximize) |
Drag the field separators (such as between Status and Capacity) to show entire field.


Make a snapshot:
WIN | type SNIPPING | ENTER | New
Drag the cursor around the area you want to snip.
File | Save as | select save location and name | Save


Post the snapshot:
Post a File or Screenshot in Seven Forums

===========================================
thanks for your cooperation,
Karl

 

[syr]

I'm just at the diskpart.

Which partition should I switch to active...the small(800mb) or the big one (1,8TB)?

EDIT:

I chose the big one...repaired 3 times.

Two things changed:
1) In the startup rapair dialog the list that showed "windows 7 (recovered)" is empty now
2) after the 3 repairs I booted and get another failure message than the former MBR-error: a disk read error occured, press ctrl+alt+del to restart

When I set the 800MB partition as active I get the original MBR error again

 

[gregrocker]

With the Active flag on the 800mb partition, did you run 3 separate Startup Repairs with reboots no matter what it reports? Are all other HD's unplugged?

It is expected that you will get the error until Startup Repair is run enough times to start Win7 on its own.

If you've run it three separate times with reboots, then switch the Active flag to the Win7 partition itself and try the three repairs again.

Next boot into free Partition Wizard bootable CD to try the Active flag on each partition but this time click on the HD # to highlight it, then from Disk tab select Rebuild MBR, Apply. If this fails to start it run the 3 Startup Repairs again on each partition while marked Active.

 

[syr]

today I took the time to proceed as you described...so had numerous repairs+reboots (3 after each config)..

But behaviour haven't changed...so my win7 installation is gone, right?