I know this question has been asked before but I've tried all the usual fixes and nothing works.
Active2 years, 8 months ago
Aug 18, 2016 In my case, the “The requested system device cannot be found” message was due to the EFI partition being converted from FAT32 to NTFS due to the client’s failed attempt to install Windows XP on a spare drive. I would add two things to this article.
Basically the hard drive had two partitions with Vista and Windows 7. I've deleted the Vista partition to make more room and expanded the Windows 7 partition to fill the drive (using GParted).
I've tried:
Mar 07, 2012 bootrec /scanos finds no OS. Discussion in 'Tech-to-Tech Computer Help' started by MobileTechie. Bootrec /RebuildBcd #3 itsJim, Mar 7, 2012. It's a Windows 7 Dell laptop that BSOD's with an 0x7b on startup. I've already tried rebuilding the BCD, /fixboot, /fixmbr, and even a restore to the factory image. BootRec /RebuildBcd - I get the message 'Total identified Windows installations: 0' BcdEdit shows a Windows Boot Manager and a Windows Boot Loader, both on C: partition. Update Rename BCD and rerun BootRec /RebuildBcd - worked. Copy bootmgr from DVD - blocked because the file's already there. Update 2 I found an article here that mentioned.
BcdEdit shows a Windows Boot Manager and a Windows Boot Loader, both on C: partition.
[Update]
[Update 2]
I found an article here that mentioned some other commands.
What else can I try?
parsley72
parsley72parsley72
Windows 10 Bootrec No Installations Found
60255 gold badges1313 silver badges3232 bronze badges
8 Answers
I fixed it by:
Windows now boots correctly and looks exactly the same as before.
parsley72parsley72
60255 gold badges1313 silver badges3232 bronze badges
I guess that you had Vista on the disk as partition 1 and then Windows 7 as partition 2, then deleted Vista, meaning that Windows 7 is now on partition 1.
Unfortunately, Windows identifies its partitions by their numbers, so that all partition references in the Windows 7 registry are now incorrect and unusable.
I believe that you will have to reinstall Windows 7. A simple Repair Installation should be enough, and will only refresh Windows and not disturb the installed applications.
Or, for the sneaky solution, you could create some small empty space on the disk before the Windows 7 partition and format it as NTFS, in effect recreating a surrogate dummy partition 1 that will restore the Windows 7 partition to its number 2 position on the disk. You might still need to do again Startup Repair.
[EDIT]
You could force Windows to recreate the BCD store partition by booting from the DVD into the Command Prompt option of Repair and entering :
In case of a permissions problem, use the command
attrib bcd -s -h -r before the rename.Reboot, and if it doesn't work then do Startup Repair again.
Another desperate solution is to assume that bootmgr got corrupted and boot as above and do :
If nothing works, just reformat the entire disk and install from scratch. Not every problem can be analyzed or has a solution.
harrymcharrymc
Bootrec No Windows Installations Found Dead
288k1616 gold badges308308 silver badges627627 bronze badges
Please make sure that the Windows 7 Recovery partition is set as the active!!
I was having trouble because the active partition was set to C:
Felipe TenorioFelipe Tenorio
Had the same issue and the below fixed it for me, assuming that you already know and started the rescue disk in Command Promt, I used the tool bcdboot.exe to recreate BCD:
Where Eduard FlorinescuEduard Florinescu
x is the drive that has the System label.
1,37655 gold badges2121 silver badges4141 bronze badges
Windows boot loader identifies partitions by offset in sectors + 4-byte disk signature in MBR. So when you moved your system partition with GParted, two odd things happened:
1) Disk offset of Win7 system partition changed, all references stored in BCD and SYSTEM registry hives are now broken.
2) Win7 system partition now has the same ID as WinVista system partition used to have, so two references now collide: bootloader with old settings tries to boot Win7 as Vista, but fails.
Basically you need to remove BCD registry hive and rebuild it from scratch, and also fix reference to disk C: in Win7's MountedDevices in SYSTEM registry hive.
Using Emergency Boot CD you can delete BCD in the 'File Manager', then recreate BCD from scratch and fix MountedDevices in 'Mount & Boot Center'.
Mikhail KupchikMikhail Kupchik
Try the fixes listed here: bootmgr is missing fixes
![]()
There are a whole number of various fixes. Solution #2 worked for me. Hope this helps others.
Mithras AdamMithras Adam
I want to improve the solution parsley72 gave:
Instead of copying the partition, install windows, then copy back:
You can boot to CD (either System Rescue Disk or windows set up disk) - I use the SRD to fix mine - then, select the Fix your windows option. It does the magic!
I think the reason is that you already have everything on C: (the restored OS, the MBR, etc.), the only thing left is for Windows to find the boot information (something only Windows software can do).
Logical huh?
Jan Doggen
3,22966 gold badges2828 silver badges4545 bronze badges
minhminh
This is just a clarifying comment on Narkevich's remark (I wanted just to add a comment but seemed to be barred from doing so Jasc photoshop 9 free download.
The reason you didn't need the /s x: option is that by default, bcd boot changes the bcd on the volume which is currently active. That's almost always what you want. If one specifies /s and a drive letter, then either 1. The drive letter is the active volume, and the command would do the same thing without /s x: as with it ;or 2. The drive letter is different from the current active volume. In this case what actually happens at boot time could only affected if either the bcd on the active disk is corrupt, and or 2. At some later time you change which disk is marked active to the one named after /s.
Cheers
Scott PetrackScott Petrack
Not the answer you're looking for? Browse other questions tagged windows-7bootmgr or ask your own question.
After a recent software crash, I've been unable to boot, and all the fixes described here turn up empty: https://www.lifewire.com/how-to-rebuild-the-bcd-in-windows-2624508. (Trying to repair off a recovery USB also fails.)
The error message when I boot reads: File: efimicrosoftbootbcd Status: 0xc0000225 Following the steps on the link above, where I get stuck is on step 4. Running 'bootrec /rebuildbcd' = 'total windows installations: 0' When I get to step #6 (attrib c:bootbcd -h -r -s), I get an error that c:/boot not found. Other sites suggest setting the system volume to 'active.' When I try that, I get an error that the volume is not a fixed mbr drive. (My HDD is a SDD formatted as GPT, as far as I know.) My system: Windows 10 Two EVO 850 SSDs (formatted as GPT) UEFI Anyone have any ideas? I'm wondering if there is something specific about trying to rebuild the boot rec on a GPT SSD that I don't understand? Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |