Boot BCD Status: 0xc000000f error The Next CEO of Stack OverflowHow to fix bcd errorWhere can...
Between two walls
Unreliable Magic - Is it worth it?
What connection does MS Office have to Netscape Navigator?
Is it professional to write unrelated content in an almost-empty email?
Interfacing a button to MCU (and PC) with 50m long cable
Are there any limitations on attacking while grappling?
Complex fractions
Elegant way to replace substring in a regex with optional groups in Python?
What expression will give age in years in QGIS?
Can you replace a racial trait cantrip when leveling up?
How to transpose the 1st and -1th levels of arbitrarily nested array?
What benefits would be gained by using human laborers instead of drones in deep sea mining?
Received an invoice from my ex-employer billing me for training; how to handle?
What exact does MIB represent in SNMP? How is it different from OID?
Is there a way to save my career from absolute disaster?
What does convergence in distribution "in the Gromov–Hausdorff" sense mean?
Several mode to write the symbol of a vector
Preparing Indesign booklet with .psd graphics for print
What was the first Unix version to run on a microcomputer?
Contours of a clandestine nature
multiple labels for a single equation
If a black hole is created from light, can this black hole then move at speed of light?
Non-deterministic sum of floats
MessageLevel in QGIS3
Boot BCD Status: 0xc000000f error
The Next CEO of Stack OverflowHow to fix bcd errorWhere can I download Windows 7 (legally from Microsoft)?Windows 10 to Windows 7 Downgrade: BCD error when trying to boot from W7 bootable USBBroken partition causing Windows to be unable to find the boot files?Changed boot settings in msconfig.exe and now Windows 7 doesn't boot“Windows failed to start” error while installing from USBHow to resolve error 0xc000000eNewly (re)installed Windows 7 fails to boot: WINLOAD.EXE could not be loadedWindows failed to start 0xc000000fWindows 7: Boot selection failed because a required device is inaccessibleIs a BCD generic?How to install Windows 7 to UEFI system?0xc000000f BCD error in windows 10… Nothings workingHow to fix bcd error
I am getting the following message whenever I start my laptop:
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 language settings, and then click "Next."
3. Click "repair your computer."
If you don't have this disc, contact your system administrator or computer
manufacturer for assistance.
File: BootBCD
Status: 0xc000000f
I have googled about the error, and from the message it looks like I need to boot my laptop from the Windows installation disc.
My laptop has Windows 7 Professional SP1 x86 installed, but when I try to insert Windows 7 Professional x86 I get the same error. Do I require an SP1 disc? I did setup CD/DVD drive as first in the boot order, but I still got the same error.
Also what other options should I try to get to the Windows 7 System Repair Screen, so that I can repair/rebuild the BCD file?
windows-7 installation windows-installation bcd
add a comment |
I am getting the following message whenever I start my laptop:
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 language settings, and then click "Next."
3. Click "repair your computer."
If you don't have this disc, contact your system administrator or computer
manufacturer for assistance.
File: BootBCD
Status: 0xc000000f
I have googled about the error, and from the message it looks like I need to boot my laptop from the Windows installation disc.
My laptop has Windows 7 Professional SP1 x86 installed, but when I try to insert Windows 7 Professional x86 I get the same error. Do I require an SP1 disc? I did setup CD/DVD drive as first in the boot order, but I still got the same error.
Also what other options should I try to get to the Windows 7 System Repair Screen, so that I can repair/rebuild the BCD file?
windows-7 installation windows-installation bcd
add a comment |
I am getting the following message whenever I start my laptop:
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 language settings, and then click "Next."
3. Click "repair your computer."
If you don't have this disc, contact your system administrator or computer
manufacturer for assistance.
File: BootBCD
Status: 0xc000000f
I have googled about the error, and from the message it looks like I need to boot my laptop from the Windows installation disc.
My laptop has Windows 7 Professional SP1 x86 installed, but when I try to insert Windows 7 Professional x86 I get the same error. Do I require an SP1 disc? I did setup CD/DVD drive as first in the boot order, but I still got the same error.
Also what other options should I try to get to the Windows 7 System Repair Screen, so that I can repair/rebuild the BCD file?
windows-7 installation windows-installation bcd
I am getting the following message whenever I start my laptop:
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 language settings, and then click "Next."
3. Click "repair your computer."
If you don't have this disc, contact your system administrator or computer
manufacturer for assistance.
File: BootBCD
Status: 0xc000000f
I have googled about the error, and from the message it looks like I need to boot my laptop from the Windows installation disc.
My laptop has Windows 7 Professional SP1 x86 installed, but when I try to insert Windows 7 Professional x86 I get the same error. Do I require an SP1 disc? I did setup CD/DVD drive as first in the boot order, but I still got the same error.
Also what other options should I try to get to the Windows 7 System Repair Screen, so that I can repair/rebuild the BCD file?
windows-7 installation windows-installation bcd
windows-7 installation windows-installation bcd
edited 1 hour ago
karel
9,34493239
9,34493239
asked Aug 5 '13 at 8:58
Romil NRomil N
864112542
864112542
add a comment |
add a comment |
5 Answers
5
active
oldest
votes
It sounds like your Windows 7 disc is broke and you should try to create a new one.
Creating a bootable USB
If you have good internet connection, then you can download your windows 7 version here (you still need a legit key ofcourse).
Then you can use Microsoft own tool to make a bootable windows 7 USB.
- Start up Windows 7 USB/DVD download tool when you have downloaded and installed it
- Select the iso file you downloaded in the Source field and click Next
- Insert your USB drive which you want to use (4GB is enough)
- Select USB DEVICE and click Next
- Select the USB device you want to use and click BEGIN COPYING
When it is done, you should have a working bootable Windows 7 USB
The same steps are used for creating a DVD, just select DVD instead of USB device.
BCD Repair
Windows already have a tool for this purpose, called BCDboot.
If the system partition has been corrupted, you can use BCDboot to replace the system partition files with new copies of these files from the Windows partition.
When you have booted to the Windows disc, then go to the command prompt (see here) and type the following to recreate the BCD on the C drive:
attrib -r -s -h c:bootbcd- unhide BCD so it can be deleted
del c:bootbcd- delete the current BCD
bcdboot C:windows- create a new BCD on the C drive
From here you should be able to boot into Windows again.
Thanks for the inputs. I would surely created Windows 7 Bootable USB. But please let me know how to execute BCD Repair commands you have mention if I'm not able to enter the Windows? Moreover from where I'm suppose to execute the BCD Repair commands. Is it inside cmd or from system repair CMD?
– Romil N
Aug 5 '13 at 10:19
To add more to my comments: Does it make any difference if I load from DVD Windows 7 Pro x86 OR Windows 7 Pro SP1 x86??
– Romil N
Aug 5 '13 at 10:21
1
Well you could make a Windows repair disk, which will only have the system recovery options. I've updated the above post to include a link to, "how to get to the command prompt". The Windows version doesn't matter if you just are going to be using the recovery tool.
– Jesper Jensen
Aug 5 '13 at 10:35
Thanks Jesper. I am assuming that the 3 steps of commands you have mentioned need to fire in System Repair CMD Screen (Correct me if I'm wrong). Moreover, let me create a repair disk and see how things shape up. I'll get back to you soon for this.
– Romil N
Aug 5 '13 at 11:24
Yes, when you get into the CMD, you fire those command
– Jesper Jensen
Aug 5 '13 at 11:46
|
show 4 more comments
I had this exact same problem and I did what most people did which was google for an answer and hope for the best. The win 7 install disk has a repair computer option that allows some automatic startup failure fixes to be implemented. Sometimes this does work, but this time it didn't. Think like a computer had a blog post that ended up being the saving grace.
But to make a long story short, here is what I did after I got the 'windows failed to start' error:
- boot from win 7 DVD or usb stick, preferably with the same version and type of windows you have on the target boot drive. For usb stick, use usb 2.0 port (3.0 may cause unexpected errors)
- After picking the language, select 'Repair your computer' (do not install win7!)
- Select 'use recovery tools that can help fix problems starting Windows...'
- Select 'Command Prompt' (CMD) to launch CMD with admin privileges.
type “diskpart” (without quotes) and press enter to launch DISKPART utility:
- type “list disk” to get a list of physical disks installed. Identify which disk has windows boot partition.
- type
select disk 0where 0 = disk # with Win7 boot partition - type
list partition. Win 7 has a 100 or 200MB boot partition size and is primary. - type 'select partition 1` where 1 = the boot partition #
- type
detail partitionand check to see if the partition is active. If active, go to next step.
- to make boot partition active, type
activeand when CMD reports the partition is active, restart the computer into recovery/repair mode (win7 install disk again) and return to CMD prompt.
- to make boot partition active, type
- type
exitto exit out of DISKPART utility
type
c:to get to the boot partition drive's root folder. (c:is the drive letter of boot partition- type
bootrec /fixmbr. Should get 'The operation completed successfully' message. - type
bootrec /fixboot. Should get 'The operation completed successfully' or 'element not found' message. - Restart the computer back into recovery mode/repair mode and load CMD prompt.
- Switch to your boot partition directory if you are not already there (usually
c:)
- Switch to your boot partition directory if you are not already there (usually
- type
bcdboot c:Windowswhere 'c:Windows' is the exact path to your windows folder. Keep in mind that in recovery mode, the path of the boot partition and path to windows may be different. In my case it was**e:**Windows.
- If you get an error 'Failure when attempting to copy boot files' or suspect you may have an EFI system partition, try typing
bcdboot c:Windows /s c: /l en-us
- If you get an error 'Failure when attempting to copy boot files' or suspect you may have an EFI system partition, try typing
- Restart computer (remove startup disks). Windows 7 should load normally.
I had windows 7 64 bit intel i5 3rd generation with an SSD drive. I used a usb thumb drive with win 7 64 bit loaded on it (rufus 1.4.9). Make sure you use usb 2.0 port. USB 3.0 port may give you errors in certain steps (3.0 drivers unavailable at the bios level in most cases).
My copy of win7 was more recent (2014) and had an additional option for recovery tools that includes windows explorer. I used that in addition to the CMD prompt to see which partition had windows installation folder.
This repair trick may also work for win 8 and/or win2k8/2012 server editions. What didn't work: Trying the use bcdedit to repair/rebuild the bootloader file. I got 'element not found' errors. Also, changing the boot order of the drives in bios didn't do anything.
edit 20 May 2018: I've upgraded to win8.1x64 + classic shell several months ago after a few programs crashed that I couldn't get working again after several reinstall attempts; never looked back. Whether you are able to fully recover or not, consider the upgrade.
1
Pitty I can't upvote more! Very comprehensive guide! Saved me lots of looking around, especially the failure part in step 10! Many thanks friend!
– Daniel Wardin
Jul 11 '15 at 16:13
1
Thanks, you gave me right answer related to Win7. All most common Microsoft boot recovery methods were failing to one thing: Cannot find BootBCD. For example bootrec /rebuildBCD: "The requested system device can not befound." After booting to command prompt from recovery CD (or installation DVD), boot location was drive C: and actual Windows at drive D: i.e. the correct command to fix boot was: "bcdboot D:Windows /s C: /l fi_FI". That creates the boot files to drive C: while other Win7 files are at D:, small letter L stands for language, specify whatever you need in your case.
– ajaaskel
May 19 '18 at 12:58
add a comment |
I had this exact same problem, i use bcdboot to fix boot partition
- boot from DOK
- diskpart
- list disk
- select disk 0
list partition, to verify all partition are there
select part 1, this is the 100m boot partition
detail partition, to get the partition Ltr (in my case it was c:) and to verify it is active
exit, to leave diskpart
now after i know windows partition and boot partition letters i can use bcdboot to fix boot partition.
this command will copy boot files needed to boot process from windows partition to boot partition.
- bcdboot d:windows /s c:
- now i can restart and boot process will work
Good luck
add a comment |
Before doing all of this, check your bios. In my situation, my RAID arrays changed due to formation of a new array onthe system volume. The boot order was changed and therefore windows could not load. After updating the bios, windows starts up no issues.
add a comment |
Or you can do what I did, I used MiniWindows to browse to c:boot and deleted "bcd" file which as I remember it was 32kb.
restart and ... here you are with a working system.
but my advice, after this Take the first chance to install a fresh copy of Win.
add a comment |
protected by Community♦ Oct 9 '15 at 15:57
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
It sounds like your Windows 7 disc is broke and you should try to create a new one.
Creating a bootable USB
If you have good internet connection, then you can download your windows 7 version here (you still need a legit key ofcourse).
Then you can use Microsoft own tool to make a bootable windows 7 USB.
- Start up Windows 7 USB/DVD download tool when you have downloaded and installed it
- Select the iso file you downloaded in the Source field and click Next
- Insert your USB drive which you want to use (4GB is enough)
- Select USB DEVICE and click Next
- Select the USB device you want to use and click BEGIN COPYING
When it is done, you should have a working bootable Windows 7 USB
The same steps are used for creating a DVD, just select DVD instead of USB device.
BCD Repair
Windows already have a tool for this purpose, called BCDboot.
If the system partition has been corrupted, you can use BCDboot to replace the system partition files with new copies of these files from the Windows partition.
When you have booted to the Windows disc, then go to the command prompt (see here) and type the following to recreate the BCD on the C drive:
attrib -r -s -h c:bootbcd- unhide BCD so it can be deleted
del c:bootbcd- delete the current BCD
bcdboot C:windows- create a new BCD on the C drive
From here you should be able to boot into Windows again.
Thanks for the inputs. I would surely created Windows 7 Bootable USB. But please let me know how to execute BCD Repair commands you have mention if I'm not able to enter the Windows? Moreover from where I'm suppose to execute the BCD Repair commands. Is it inside cmd or from system repair CMD?
– Romil N
Aug 5 '13 at 10:19
To add more to my comments: Does it make any difference if I load from DVD Windows 7 Pro x86 OR Windows 7 Pro SP1 x86??
– Romil N
Aug 5 '13 at 10:21
1
Well you could make a Windows repair disk, which will only have the system recovery options. I've updated the above post to include a link to, "how to get to the command prompt". The Windows version doesn't matter if you just are going to be using the recovery tool.
– Jesper Jensen
Aug 5 '13 at 10:35
Thanks Jesper. I am assuming that the 3 steps of commands you have mentioned need to fire in System Repair CMD Screen (Correct me if I'm wrong). Moreover, let me create a repair disk and see how things shape up. I'll get back to you soon for this.
– Romil N
Aug 5 '13 at 11:24
Yes, when you get into the CMD, you fire those command
– Jesper Jensen
Aug 5 '13 at 11:46
|
show 4 more comments
It sounds like your Windows 7 disc is broke and you should try to create a new one.
Creating a bootable USB
If you have good internet connection, then you can download your windows 7 version here (you still need a legit key ofcourse).
Then you can use Microsoft own tool to make a bootable windows 7 USB.
- Start up Windows 7 USB/DVD download tool when you have downloaded and installed it
- Select the iso file you downloaded in the Source field and click Next
- Insert your USB drive which you want to use (4GB is enough)
- Select USB DEVICE and click Next
- Select the USB device you want to use and click BEGIN COPYING
When it is done, you should have a working bootable Windows 7 USB
The same steps are used for creating a DVD, just select DVD instead of USB device.
BCD Repair
Windows already have a tool for this purpose, called BCDboot.
If the system partition has been corrupted, you can use BCDboot to replace the system partition files with new copies of these files from the Windows partition.
When you have booted to the Windows disc, then go to the command prompt (see here) and type the following to recreate the BCD on the C drive:
attrib -r -s -h c:bootbcd- unhide BCD so it can be deleted
del c:bootbcd- delete the current BCD
bcdboot C:windows- create a new BCD on the C drive
From here you should be able to boot into Windows again.
Thanks for the inputs. I would surely created Windows 7 Bootable USB. But please let me know how to execute BCD Repair commands you have mention if I'm not able to enter the Windows? Moreover from where I'm suppose to execute the BCD Repair commands. Is it inside cmd or from system repair CMD?
– Romil N
Aug 5 '13 at 10:19
To add more to my comments: Does it make any difference if I load from DVD Windows 7 Pro x86 OR Windows 7 Pro SP1 x86??
– Romil N
Aug 5 '13 at 10:21
1
Well you could make a Windows repair disk, which will only have the system recovery options. I've updated the above post to include a link to, "how to get to the command prompt". The Windows version doesn't matter if you just are going to be using the recovery tool.
– Jesper Jensen
Aug 5 '13 at 10:35
Thanks Jesper. I am assuming that the 3 steps of commands you have mentioned need to fire in System Repair CMD Screen (Correct me if I'm wrong). Moreover, let me create a repair disk and see how things shape up. I'll get back to you soon for this.
– Romil N
Aug 5 '13 at 11:24
Yes, when you get into the CMD, you fire those command
– Jesper Jensen
Aug 5 '13 at 11:46
|
show 4 more comments
It sounds like your Windows 7 disc is broke and you should try to create a new one.
Creating a bootable USB
If you have good internet connection, then you can download your windows 7 version here (you still need a legit key ofcourse).
Then you can use Microsoft own tool to make a bootable windows 7 USB.
- Start up Windows 7 USB/DVD download tool when you have downloaded and installed it
- Select the iso file you downloaded in the Source field and click Next
- Insert your USB drive which you want to use (4GB is enough)
- Select USB DEVICE and click Next
- Select the USB device you want to use and click BEGIN COPYING
When it is done, you should have a working bootable Windows 7 USB
The same steps are used for creating a DVD, just select DVD instead of USB device.
BCD Repair
Windows already have a tool for this purpose, called BCDboot.
If the system partition has been corrupted, you can use BCDboot to replace the system partition files with new copies of these files from the Windows partition.
When you have booted to the Windows disc, then go to the command prompt (see here) and type the following to recreate the BCD on the C drive:
attrib -r -s -h c:bootbcd- unhide BCD so it can be deleted
del c:bootbcd- delete the current BCD
bcdboot C:windows- create a new BCD on the C drive
From here you should be able to boot into Windows again.
It sounds like your Windows 7 disc is broke and you should try to create a new one.
Creating a bootable USB
If you have good internet connection, then you can download your windows 7 version here (you still need a legit key ofcourse).
Then you can use Microsoft own tool to make a bootable windows 7 USB.
- Start up Windows 7 USB/DVD download tool when you have downloaded and installed it
- Select the iso file you downloaded in the Source field and click Next
- Insert your USB drive which you want to use (4GB is enough)
- Select USB DEVICE and click Next
- Select the USB device you want to use and click BEGIN COPYING
When it is done, you should have a working bootable Windows 7 USB
The same steps are used for creating a DVD, just select DVD instead of USB device.
BCD Repair
Windows already have a tool for this purpose, called BCDboot.
If the system partition has been corrupted, you can use BCDboot to replace the system partition files with new copies of these files from the Windows partition.
When you have booted to the Windows disc, then go to the command prompt (see here) and type the following to recreate the BCD on the C drive:
attrib -r -s -h c:bootbcd- unhide BCD so it can be deleted
del c:bootbcd- delete the current BCD
bcdboot C:windows- create a new BCD on the C drive
From here you should be able to boot into Windows again.
edited Mar 20 '17 at 10:17
Community♦
1
1
answered Aug 5 '13 at 9:55
Jesper JensenJesper Jensen
654411
654411
Thanks for the inputs. I would surely created Windows 7 Bootable USB. But please let me know how to execute BCD Repair commands you have mention if I'm not able to enter the Windows? Moreover from where I'm suppose to execute the BCD Repair commands. Is it inside cmd or from system repair CMD?
– Romil N
Aug 5 '13 at 10:19
To add more to my comments: Does it make any difference if I load from DVD Windows 7 Pro x86 OR Windows 7 Pro SP1 x86??
– Romil N
Aug 5 '13 at 10:21
1
Well you could make a Windows repair disk, which will only have the system recovery options. I've updated the above post to include a link to, "how to get to the command prompt". The Windows version doesn't matter if you just are going to be using the recovery tool.
– Jesper Jensen
Aug 5 '13 at 10:35
Thanks Jesper. I am assuming that the 3 steps of commands you have mentioned need to fire in System Repair CMD Screen (Correct me if I'm wrong). Moreover, let me create a repair disk and see how things shape up. I'll get back to you soon for this.
– Romil N
Aug 5 '13 at 11:24
Yes, when you get into the CMD, you fire those command
– Jesper Jensen
Aug 5 '13 at 11:46
|
show 4 more comments
Thanks for the inputs. I would surely created Windows 7 Bootable USB. But please let me know how to execute BCD Repair commands you have mention if I'm not able to enter the Windows? Moreover from where I'm suppose to execute the BCD Repair commands. Is it inside cmd or from system repair CMD?
– Romil N
Aug 5 '13 at 10:19
To add more to my comments: Does it make any difference if I load from DVD Windows 7 Pro x86 OR Windows 7 Pro SP1 x86??
– Romil N
Aug 5 '13 at 10:21
1
Well you could make a Windows repair disk, which will only have the system recovery options. I've updated the above post to include a link to, "how to get to the command prompt". The Windows version doesn't matter if you just are going to be using the recovery tool.
– Jesper Jensen
Aug 5 '13 at 10:35
Thanks Jesper. I am assuming that the 3 steps of commands you have mentioned need to fire in System Repair CMD Screen (Correct me if I'm wrong). Moreover, let me create a repair disk and see how things shape up. I'll get back to you soon for this.
– Romil N
Aug 5 '13 at 11:24
Yes, when you get into the CMD, you fire those command
– Jesper Jensen
Aug 5 '13 at 11:46
Thanks for the inputs. I would surely created Windows 7 Bootable USB. But please let me know how to execute BCD Repair commands you have mention if I'm not able to enter the Windows? Moreover from where I'm suppose to execute the BCD Repair commands. Is it inside cmd or from system repair CMD?
– Romil N
Aug 5 '13 at 10:19
Thanks for the inputs. I would surely created Windows 7 Bootable USB. But please let me know how to execute BCD Repair commands you have mention if I'm not able to enter the Windows? Moreover from where I'm suppose to execute the BCD Repair commands. Is it inside cmd or from system repair CMD?
– Romil N
Aug 5 '13 at 10:19
To add more to my comments: Does it make any difference if I load from DVD Windows 7 Pro x86 OR Windows 7 Pro SP1 x86??
– Romil N
Aug 5 '13 at 10:21
To add more to my comments: Does it make any difference if I load from DVD Windows 7 Pro x86 OR Windows 7 Pro SP1 x86??
– Romil N
Aug 5 '13 at 10:21
1
1
Well you could make a Windows repair disk, which will only have the system recovery options. I've updated the above post to include a link to, "how to get to the command prompt". The Windows version doesn't matter if you just are going to be using the recovery tool.
– Jesper Jensen
Aug 5 '13 at 10:35
Well you could make a Windows repair disk, which will only have the system recovery options. I've updated the above post to include a link to, "how to get to the command prompt". The Windows version doesn't matter if you just are going to be using the recovery tool.
– Jesper Jensen
Aug 5 '13 at 10:35
Thanks Jesper. I am assuming that the 3 steps of commands you have mentioned need to fire in System Repair CMD Screen (Correct me if I'm wrong). Moreover, let me create a repair disk and see how things shape up. I'll get back to you soon for this.
– Romil N
Aug 5 '13 at 11:24
Thanks Jesper. I am assuming that the 3 steps of commands you have mentioned need to fire in System Repair CMD Screen (Correct me if I'm wrong). Moreover, let me create a repair disk and see how things shape up. I'll get back to you soon for this.
– Romil N
Aug 5 '13 at 11:24
Yes, when you get into the CMD, you fire those command
– Jesper Jensen
Aug 5 '13 at 11:46
Yes, when you get into the CMD, you fire those command
– Jesper Jensen
Aug 5 '13 at 11:46
|
show 4 more comments
I had this exact same problem and I did what most people did which was google for an answer and hope for the best. The win 7 install disk has a repair computer option that allows some automatic startup failure fixes to be implemented. Sometimes this does work, but this time it didn't. Think like a computer had a blog post that ended up being the saving grace.
But to make a long story short, here is what I did after I got the 'windows failed to start' error:
- boot from win 7 DVD or usb stick, preferably with the same version and type of windows you have on the target boot drive. For usb stick, use usb 2.0 port (3.0 may cause unexpected errors)
- After picking the language, select 'Repair your computer' (do not install win7!)
- Select 'use recovery tools that can help fix problems starting Windows...'
- Select 'Command Prompt' (CMD) to launch CMD with admin privileges.
type “diskpart” (without quotes) and press enter to launch DISKPART utility:
- type “list disk” to get a list of physical disks installed. Identify which disk has windows boot partition.
- type
select disk 0where 0 = disk # with Win7 boot partition - type
list partition. Win 7 has a 100 or 200MB boot partition size and is primary. - type 'select partition 1` where 1 = the boot partition #
- type
detail partitionand check to see if the partition is active. If active, go to next step.
- to make boot partition active, type
activeand when CMD reports the partition is active, restart the computer into recovery/repair mode (win7 install disk again) and return to CMD prompt.
- to make boot partition active, type
- type
exitto exit out of DISKPART utility
type
c:to get to the boot partition drive's root folder. (c:is the drive letter of boot partition- type
bootrec /fixmbr. Should get 'The operation completed successfully' message. - type
bootrec /fixboot. Should get 'The operation completed successfully' or 'element not found' message. - Restart the computer back into recovery mode/repair mode and load CMD prompt.
- Switch to your boot partition directory if you are not already there (usually
c:)
- Switch to your boot partition directory if you are not already there (usually
- type
bcdboot c:Windowswhere 'c:Windows' is the exact path to your windows folder. Keep in mind that in recovery mode, the path of the boot partition and path to windows may be different. In my case it was**e:**Windows.
- If you get an error 'Failure when attempting to copy boot files' or suspect you may have an EFI system partition, try typing
bcdboot c:Windows /s c: /l en-us
- If you get an error 'Failure when attempting to copy boot files' or suspect you may have an EFI system partition, try typing
- Restart computer (remove startup disks). Windows 7 should load normally.
I had windows 7 64 bit intel i5 3rd generation with an SSD drive. I used a usb thumb drive with win 7 64 bit loaded on it (rufus 1.4.9). Make sure you use usb 2.0 port. USB 3.0 port may give you errors in certain steps (3.0 drivers unavailable at the bios level in most cases).
My copy of win7 was more recent (2014) and had an additional option for recovery tools that includes windows explorer. I used that in addition to the CMD prompt to see which partition had windows installation folder.
This repair trick may also work for win 8 and/or win2k8/2012 server editions. What didn't work: Trying the use bcdedit to repair/rebuild the bootloader file. I got 'element not found' errors. Also, changing the boot order of the drives in bios didn't do anything.
edit 20 May 2018: I've upgraded to win8.1x64 + classic shell several months ago after a few programs crashed that I couldn't get working again after several reinstall attempts; never looked back. Whether you are able to fully recover or not, consider the upgrade.
1
Pitty I can't upvote more! Very comprehensive guide! Saved me lots of looking around, especially the failure part in step 10! Many thanks friend!
– Daniel Wardin
Jul 11 '15 at 16:13
1
Thanks, you gave me right answer related to Win7. All most common Microsoft boot recovery methods were failing to one thing: Cannot find BootBCD. For example bootrec /rebuildBCD: "The requested system device can not befound." After booting to command prompt from recovery CD (or installation DVD), boot location was drive C: and actual Windows at drive D: i.e. the correct command to fix boot was: "bcdboot D:Windows /s C: /l fi_FI". That creates the boot files to drive C: while other Win7 files are at D:, small letter L stands for language, specify whatever you need in your case.
– ajaaskel
May 19 '18 at 12:58
add a comment |
I had this exact same problem and I did what most people did which was google for an answer and hope for the best. The win 7 install disk has a repair computer option that allows some automatic startup failure fixes to be implemented. Sometimes this does work, but this time it didn't. Think like a computer had a blog post that ended up being the saving grace.
But to make a long story short, here is what I did after I got the 'windows failed to start' error:
- boot from win 7 DVD or usb stick, preferably with the same version and type of windows you have on the target boot drive. For usb stick, use usb 2.0 port (3.0 may cause unexpected errors)
- After picking the language, select 'Repair your computer' (do not install win7!)
- Select 'use recovery tools that can help fix problems starting Windows...'
- Select 'Command Prompt' (CMD) to launch CMD with admin privileges.
type “diskpart” (without quotes) and press enter to launch DISKPART utility:
- type “list disk” to get a list of physical disks installed. Identify which disk has windows boot partition.
- type
select disk 0where 0 = disk # with Win7 boot partition - type
list partition. Win 7 has a 100 or 200MB boot partition size and is primary. - type 'select partition 1` where 1 = the boot partition #
- type
detail partitionand check to see if the partition is active. If active, go to next step.
- to make boot partition active, type
activeand when CMD reports the partition is active, restart the computer into recovery/repair mode (win7 install disk again) and return to CMD prompt.
- to make boot partition active, type
- type
exitto exit out of DISKPART utility
type
c:to get to the boot partition drive's root folder. (c:is the drive letter of boot partition- type
bootrec /fixmbr. Should get 'The operation completed successfully' message. - type
bootrec /fixboot. Should get 'The operation completed successfully' or 'element not found' message. - Restart the computer back into recovery mode/repair mode and load CMD prompt.
- Switch to your boot partition directory if you are not already there (usually
c:)
- Switch to your boot partition directory if you are not already there (usually
- type
bcdboot c:Windowswhere 'c:Windows' is the exact path to your windows folder. Keep in mind that in recovery mode, the path of the boot partition and path to windows may be different. In my case it was**e:**Windows.
- If you get an error 'Failure when attempting to copy boot files' or suspect you may have an EFI system partition, try typing
bcdboot c:Windows /s c: /l en-us
- If you get an error 'Failure when attempting to copy boot files' or suspect you may have an EFI system partition, try typing
- Restart computer (remove startup disks). Windows 7 should load normally.
I had windows 7 64 bit intel i5 3rd generation with an SSD drive. I used a usb thumb drive with win 7 64 bit loaded on it (rufus 1.4.9). Make sure you use usb 2.0 port. USB 3.0 port may give you errors in certain steps (3.0 drivers unavailable at the bios level in most cases).
My copy of win7 was more recent (2014) and had an additional option for recovery tools that includes windows explorer. I used that in addition to the CMD prompt to see which partition had windows installation folder.
This repair trick may also work for win 8 and/or win2k8/2012 server editions. What didn't work: Trying the use bcdedit to repair/rebuild the bootloader file. I got 'element not found' errors. Also, changing the boot order of the drives in bios didn't do anything.
edit 20 May 2018: I've upgraded to win8.1x64 + classic shell several months ago after a few programs crashed that I couldn't get working again after several reinstall attempts; never looked back. Whether you are able to fully recover or not, consider the upgrade.
1
Pitty I can't upvote more! Very comprehensive guide! Saved me lots of looking around, especially the failure part in step 10! Many thanks friend!
– Daniel Wardin
Jul 11 '15 at 16:13
1
Thanks, you gave me right answer related to Win7. All most common Microsoft boot recovery methods were failing to one thing: Cannot find BootBCD. For example bootrec /rebuildBCD: "The requested system device can not befound." After booting to command prompt from recovery CD (or installation DVD), boot location was drive C: and actual Windows at drive D: i.e. the correct command to fix boot was: "bcdboot D:Windows /s C: /l fi_FI". That creates the boot files to drive C: while other Win7 files are at D:, small letter L stands for language, specify whatever you need in your case.
– ajaaskel
May 19 '18 at 12:58
add a comment |
I had this exact same problem and I did what most people did which was google for an answer and hope for the best. The win 7 install disk has a repair computer option that allows some automatic startup failure fixes to be implemented. Sometimes this does work, but this time it didn't. Think like a computer had a blog post that ended up being the saving grace.
But to make a long story short, here is what I did after I got the 'windows failed to start' error:
- boot from win 7 DVD or usb stick, preferably with the same version and type of windows you have on the target boot drive. For usb stick, use usb 2.0 port (3.0 may cause unexpected errors)
- After picking the language, select 'Repair your computer' (do not install win7!)
- Select 'use recovery tools that can help fix problems starting Windows...'
- Select 'Command Prompt' (CMD) to launch CMD with admin privileges.
type “diskpart” (without quotes) and press enter to launch DISKPART utility:
- type “list disk” to get a list of physical disks installed. Identify which disk has windows boot partition.
- type
select disk 0where 0 = disk # with Win7 boot partition - type
list partition. Win 7 has a 100 or 200MB boot partition size and is primary. - type 'select partition 1` where 1 = the boot partition #
- type
detail partitionand check to see if the partition is active. If active, go to next step.
- to make boot partition active, type
activeand when CMD reports the partition is active, restart the computer into recovery/repair mode (win7 install disk again) and return to CMD prompt.
- to make boot partition active, type
- type
exitto exit out of DISKPART utility
type
c:to get to the boot partition drive's root folder. (c:is the drive letter of boot partition- type
bootrec /fixmbr. Should get 'The operation completed successfully' message. - type
bootrec /fixboot. Should get 'The operation completed successfully' or 'element not found' message. - Restart the computer back into recovery mode/repair mode and load CMD prompt.
- Switch to your boot partition directory if you are not already there (usually
c:)
- Switch to your boot partition directory if you are not already there (usually
- type
bcdboot c:Windowswhere 'c:Windows' is the exact path to your windows folder. Keep in mind that in recovery mode, the path of the boot partition and path to windows may be different. In my case it was**e:**Windows.
- If you get an error 'Failure when attempting to copy boot files' or suspect you may have an EFI system partition, try typing
bcdboot c:Windows /s c: /l en-us
- If you get an error 'Failure when attempting to copy boot files' or suspect you may have an EFI system partition, try typing
- Restart computer (remove startup disks). Windows 7 should load normally.
I had windows 7 64 bit intel i5 3rd generation with an SSD drive. I used a usb thumb drive with win 7 64 bit loaded on it (rufus 1.4.9). Make sure you use usb 2.0 port. USB 3.0 port may give you errors in certain steps (3.0 drivers unavailable at the bios level in most cases).
My copy of win7 was more recent (2014) and had an additional option for recovery tools that includes windows explorer. I used that in addition to the CMD prompt to see which partition had windows installation folder.
This repair trick may also work for win 8 and/or win2k8/2012 server editions. What didn't work: Trying the use bcdedit to repair/rebuild the bootloader file. I got 'element not found' errors. Also, changing the boot order of the drives in bios didn't do anything.
edit 20 May 2018: I've upgraded to win8.1x64 + classic shell several months ago after a few programs crashed that I couldn't get working again after several reinstall attempts; never looked back. Whether you are able to fully recover or not, consider the upgrade.
I had this exact same problem and I did what most people did which was google for an answer and hope for the best. The win 7 install disk has a repair computer option that allows some automatic startup failure fixes to be implemented. Sometimes this does work, but this time it didn't. Think like a computer had a blog post that ended up being the saving grace.
But to make a long story short, here is what I did after I got the 'windows failed to start' error:
- boot from win 7 DVD or usb stick, preferably with the same version and type of windows you have on the target boot drive. For usb stick, use usb 2.0 port (3.0 may cause unexpected errors)
- After picking the language, select 'Repair your computer' (do not install win7!)
- Select 'use recovery tools that can help fix problems starting Windows...'
- Select 'Command Prompt' (CMD) to launch CMD with admin privileges.
type “diskpart” (without quotes) and press enter to launch DISKPART utility:
- type “list disk” to get a list of physical disks installed. Identify which disk has windows boot partition.
- type
select disk 0where 0 = disk # with Win7 boot partition - type
list partition. Win 7 has a 100 or 200MB boot partition size and is primary. - type 'select partition 1` where 1 = the boot partition #
- type
detail partitionand check to see if the partition is active. If active, go to next step.
- to make boot partition active, type
activeand when CMD reports the partition is active, restart the computer into recovery/repair mode (win7 install disk again) and return to CMD prompt.
- to make boot partition active, type
- type
exitto exit out of DISKPART utility
type
c:to get to the boot partition drive's root folder. (c:is the drive letter of boot partition- type
bootrec /fixmbr. Should get 'The operation completed successfully' message. - type
bootrec /fixboot. Should get 'The operation completed successfully' or 'element not found' message. - Restart the computer back into recovery mode/repair mode and load CMD prompt.
- Switch to your boot partition directory if you are not already there (usually
c:)
- Switch to your boot partition directory if you are not already there (usually
- type
bcdboot c:Windowswhere 'c:Windows' is the exact path to your windows folder. Keep in mind that in recovery mode, the path of the boot partition and path to windows may be different. In my case it was**e:**Windows.
- If you get an error 'Failure when attempting to copy boot files' or suspect you may have an EFI system partition, try typing
bcdboot c:Windows /s c: /l en-us
- If you get an error 'Failure when attempting to copy boot files' or suspect you may have an EFI system partition, try typing
- Restart computer (remove startup disks). Windows 7 should load normally.
I had windows 7 64 bit intel i5 3rd generation with an SSD drive. I used a usb thumb drive with win 7 64 bit loaded on it (rufus 1.4.9). Make sure you use usb 2.0 port. USB 3.0 port may give you errors in certain steps (3.0 drivers unavailable at the bios level in most cases).
My copy of win7 was more recent (2014) and had an additional option for recovery tools that includes windows explorer. I used that in addition to the CMD prompt to see which partition had windows installation folder.
This repair trick may also work for win 8 and/or win2k8/2012 server editions. What didn't work: Trying the use bcdedit to repair/rebuild the bootloader file. I got 'element not found' errors. Also, changing the boot order of the drives in bios didn't do anything.
edit 20 May 2018: I've upgraded to win8.1x64 + classic shell several months ago after a few programs crashed that I couldn't get working again after several reinstall attempts; never looked back. Whether you are able to fully recover or not, consider the upgrade.
edited May 20 '18 at 8:33
answered Aug 4 '14 at 2:24
Jon GrahJon Grah
232210
232210
1
Pitty I can't upvote more! Very comprehensive guide! Saved me lots of looking around, especially the failure part in step 10! Many thanks friend!
– Daniel Wardin
Jul 11 '15 at 16:13
1
Thanks, you gave me right answer related to Win7. All most common Microsoft boot recovery methods were failing to one thing: Cannot find BootBCD. For example bootrec /rebuildBCD: "The requested system device can not befound." After booting to command prompt from recovery CD (or installation DVD), boot location was drive C: and actual Windows at drive D: i.e. the correct command to fix boot was: "bcdboot D:Windows /s C: /l fi_FI". That creates the boot files to drive C: while other Win7 files are at D:, small letter L stands for language, specify whatever you need in your case.
– ajaaskel
May 19 '18 at 12:58
add a comment |
1
Pitty I can't upvote more! Very comprehensive guide! Saved me lots of looking around, especially the failure part in step 10! Many thanks friend!
– Daniel Wardin
Jul 11 '15 at 16:13
1
Thanks, you gave me right answer related to Win7. All most common Microsoft boot recovery methods were failing to one thing: Cannot find BootBCD. For example bootrec /rebuildBCD: "The requested system device can not befound." After booting to command prompt from recovery CD (or installation DVD), boot location was drive C: and actual Windows at drive D: i.e. the correct command to fix boot was: "bcdboot D:Windows /s C: /l fi_FI". That creates the boot files to drive C: while other Win7 files are at D:, small letter L stands for language, specify whatever you need in your case.
– ajaaskel
May 19 '18 at 12:58
1
1
Pitty I can't upvote more! Very comprehensive guide! Saved me lots of looking around, especially the failure part in step 10! Many thanks friend!
– Daniel Wardin
Jul 11 '15 at 16:13
Pitty I can't upvote more! Very comprehensive guide! Saved me lots of looking around, especially the failure part in step 10! Many thanks friend!
– Daniel Wardin
Jul 11 '15 at 16:13
1
1
Thanks, you gave me right answer related to Win7. All most common Microsoft boot recovery methods were failing to one thing: Cannot find BootBCD. For example bootrec /rebuildBCD: "The requested system device can not befound." After booting to command prompt from recovery CD (or installation DVD), boot location was drive C: and actual Windows at drive D: i.e. the correct command to fix boot was: "bcdboot D:Windows /s C: /l fi_FI". That creates the boot files to drive C: while other Win7 files are at D:, small letter L stands for language, specify whatever you need in your case.
– ajaaskel
May 19 '18 at 12:58
Thanks, you gave me right answer related to Win7. All most common Microsoft boot recovery methods were failing to one thing: Cannot find BootBCD. For example bootrec /rebuildBCD: "The requested system device can not befound." After booting to command prompt from recovery CD (or installation DVD), boot location was drive C: and actual Windows at drive D: i.e. the correct command to fix boot was: "bcdboot D:Windows /s C: /l fi_FI". That creates the boot files to drive C: while other Win7 files are at D:, small letter L stands for language, specify whatever you need in your case.
– ajaaskel
May 19 '18 at 12:58
add a comment |
I had this exact same problem, i use bcdboot to fix boot partition
- boot from DOK
- diskpart
- list disk
- select disk 0
list partition, to verify all partition are there
select part 1, this is the 100m boot partition
detail partition, to get the partition Ltr (in my case it was c:) and to verify it is active
exit, to leave diskpart
now after i know windows partition and boot partition letters i can use bcdboot to fix boot partition.
this command will copy boot files needed to boot process from windows partition to boot partition.
- bcdboot d:windows /s c:
- now i can restart and boot process will work
Good luck
add a comment |
I had this exact same problem, i use bcdboot to fix boot partition
- boot from DOK
- diskpart
- list disk
- select disk 0
list partition, to verify all partition are there
select part 1, this is the 100m boot partition
detail partition, to get the partition Ltr (in my case it was c:) and to verify it is active
exit, to leave diskpart
now after i know windows partition and boot partition letters i can use bcdboot to fix boot partition.
this command will copy boot files needed to boot process from windows partition to boot partition.
- bcdboot d:windows /s c:
- now i can restart and boot process will work
Good luck
add a comment |
I had this exact same problem, i use bcdboot to fix boot partition
- boot from DOK
- diskpart
- list disk
- select disk 0
list partition, to verify all partition are there
select part 1, this is the 100m boot partition
detail partition, to get the partition Ltr (in my case it was c:) and to verify it is active
exit, to leave diskpart
now after i know windows partition and boot partition letters i can use bcdboot to fix boot partition.
this command will copy boot files needed to boot process from windows partition to boot partition.
- bcdboot d:windows /s c:
- now i can restart and boot process will work
Good luck
I had this exact same problem, i use bcdboot to fix boot partition
- boot from DOK
- diskpart
- list disk
- select disk 0
list partition, to verify all partition are there
select part 1, this is the 100m boot partition
detail partition, to get the partition Ltr (in my case it was c:) and to verify it is active
exit, to leave diskpart
now after i know windows partition and boot partition letters i can use bcdboot to fix boot partition.
this command will copy boot files needed to boot process from windows partition to boot partition.
- bcdboot d:windows /s c:
- now i can restart and boot process will work
Good luck
answered Aug 6 '14 at 9:37
liorlevi1974liorlevi1974
211
211
add a comment |
add a comment |
Before doing all of this, check your bios. In my situation, my RAID arrays changed due to formation of a new array onthe system volume. The boot order was changed and therefore windows could not load. After updating the bios, windows starts up no issues.
add a comment |
Before doing all of this, check your bios. In my situation, my RAID arrays changed due to formation of a new array onthe system volume. The boot order was changed and therefore windows could not load. After updating the bios, windows starts up no issues.
add a comment |
Before doing all of this, check your bios. In my situation, my RAID arrays changed due to formation of a new array onthe system volume. The boot order was changed and therefore windows could not load. After updating the bios, windows starts up no issues.
Before doing all of this, check your bios. In my situation, my RAID arrays changed due to formation of a new array onthe system volume. The boot order was changed and therefore windows could not load. After updating the bios, windows starts up no issues.
answered Jun 1 '15 at 11:44
NickNick
1861111
1861111
add a comment |
add a comment |
Or you can do what I did, I used MiniWindows to browse to c:boot and deleted "bcd" file which as I remember it was 32kb.
restart and ... here you are with a working system.
but my advice, after this Take the first chance to install a fresh copy of Win.
add a comment |
Or you can do what I did, I used MiniWindows to browse to c:boot and deleted "bcd" file which as I remember it was 32kb.
restart and ... here you are with a working system.
but my advice, after this Take the first chance to install a fresh copy of Win.
add a comment |
Or you can do what I did, I used MiniWindows to browse to c:boot and deleted "bcd" file which as I remember it was 32kb.
restart and ... here you are with a working system.
but my advice, after this Take the first chance to install a fresh copy of Win.
Or you can do what I did, I used MiniWindows to browse to c:boot and deleted "bcd" file which as I remember it was 32kb.
restart and ... here you are with a working system.
but my advice, after this Take the first chance to install a fresh copy of Win.
answered Feb 7 '14 at 9:10
Ray MassRay Mass
1
1
add a comment |
add a comment |
protected by Community♦ Oct 9 '15 at 15:57
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?