Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Status: 0xc0000225 boot selection failed; required device inaccessible

05 Jul 2014   #1
blablubb1234

Windows 7 x64, Archlinux x64
 
 
Status: 0xc0000225 boot selection failed; required device inaccessible

Hi everybody,

I am dualbooting Windows 7 Ultimate and Arch Linux (using rEFInd boot manager) on a GPT disk and (unfortuunately) have an UEFI system.

My setup used to work perfectly fine, until I recently updated rEFInd - and following this - deleted a paramount file on my ESP: bootx64.efi.

Obviously, I could not boot any OS anymore, so I tried to restore the bootloader but during this process I killed all my partitions.

Luckily, I could restore them using the tool Testdisk on an Archiso live usb stick. I restored bootx64.efi and wanted to boot Archlinux ... where I was greeted by an error message telling me that the root device rEFInd is looking for is not present. I could fix this by adjusting the PARTUUID in the respective config file and now I am booted to Archlinux. So as it seems, recovering the partitions using Testdisk resulted in changed UUIDs for my partitions.

However, I still can not boot Windows 7 because all I see is this boot error:

Code:
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 do not have this disc, contact your system administrator or computer 
manufacturer for assistance.

Status: 0xc0000225

Info: The boot selection failed because a required device is inaccessible.
As the recovery of Archlinux above shows, the error will most likely be a mismatching PARTUUID.

Now, I tried to recover the bootloader - or adjust the BCD file to be more precise - but no luck there.
I followed this guide: How To In My PC Software: A-How-To: BCDedit to fix Windows 7 Boot... in order to repair the BCD file.

But at the screen where I should select the OS I want to repair, I just have a blank list, I can not select C: (as it is done in the guide). In a consequence (I assume) I can not start bcdedit.exe and - ultimatively - can not edit BCD settings. I even tried copying a bcdedit.exe from another working system onto the Windows 7 usb stick and start it from there, but no luck aswell. Is there any way how I can start bcdedit and adjust the UUID of my Windows partition (if this is the error after all)?

Any other ideas? Help is very much appreciated

Best regards


My System SpecsSystem Spec
.
05 Jul 2014   #2
amazing

Windows 7 Ultimate 32bit
 
 

You are right that you have changed GUIDs for all your partitions. In this case, it is impossible to recover your Windows with the recovery tool.
You need to manually restore the BCD store with bcdedit.exe. The method 2 in this page will let you know how to do this.
My System SpecsSystem Spec
07 Jul 2014   #3
blablubb1234

Windows 7 x64, Archlinux x64
 
 

First off: I solved my problem. If you are interested in reading how, read on:

Quote   Quote: Originally Posted by amazing View Post
You are right that you have changed GUIDs for all your partitions. In this case, it is impossible to recover your Windows with the recovery tool.
You need to manually restore the BCD store with bcdedit.exe. The method 2 in this page will let you know how to do this.
Well I tried to follow method 2 from the article Error message when you start Windows 7: "The Windows Boot Configuration Data file is missing required information" as you suggested, but when I wanted to use bcdedit.exe or bootrec.exe to rebuild the BCD I always got an error saying:

Code:
The requested system device cannot be found.
As a consequence even method 3 could not be successfull, as it involves bcdedit and bootrec aswell.

The funny thing however was, that if I did an bootrec /ScanOs it would return:

Code:
Scanning all disks for Windows installations.
Please wait, since this may take a while...
Successfully scanned Windows installations.
Total identified Windows installations: 1
[1]  D:\Windows
So basically it found the Windows partition. But if I tried to write a new BCD (f.e. with bootrec /rebuildbcd) for that OS it failed, although with C: and D: I could access both the EFI system partition and the Windows partition and see all the files on both. And I cannot set partitions active as I am using GPT formatted HDD.

bcdedit - Problem recreating BCD on Windows 7 64bit - The requested system device cannot be found - Super User suggests that this might be due to the wrong USB port, however I can eliminate this possibility now (see below).

The other hint from that post is that one has to explicitely tell bcdedit and bootrec the location for creating the BCD file. I haven't tested that as I saw the tip too late.

What basically did the trick was the ren command to make a backup of BCD to BCD.old. After doing so I gave the automatic recovery from Windows a second chance and it turned out that it could this time resolve the issue (and Windows 7 booted up again). However, Windows RE naturally ****ed up my rEFInd as it writes its backup bootloader to <EFI PARTITION>/boot/EFI/Boot/Bootx64.efi. As I have to store refind_x64.efi as <EFI PARTITION>/boot/EFI/Boot/Bootx64.efi (this is the only way I can load rEFInd properly), rEFInd got overwritten. So I had to get into Arch live system again to overwrite M$' backup bootloader with rEFInd again. and could load both OSs again. M$ bootloader now resides inside <EFI PARTITION>/boot/EFI/Microsoft/Boot/ and is thus found by rEFInd at boot time.

What I still don't get is why I couldn't use the the commands from here: Use Bootrec.exe in the Windows RE to troubleshoot startup issues

As this guide How To Rebuild the BCD in Windows [10 to 20 Minutes] explains all the single steps, this seems exactly like what I need, but still I couldn't make it work. Is this because of the wrong UUID (and thus Windows RE isn't able to talk to the partitions? But why does diskpart then find the partitions and is able to list the files on them)?

Now with the repaired Windows if I start Windows RE from the same USB port it shows me C:\ as the found Windows OS to repair. After choosing this as the correct entry, I could use bcdedit just as mentioned in all the guides. So this is why for my setup the wrong USB port is not the reason why bcdedit and bootrec didn't work. But again the question: Why couldn't I use both before?
My System SpecsSystem Spec
.

07 Jul 2014   #4
gregrocker

 

Almost all of the win7 repair regimens (many developed here) are upended by UEFI. It offers too few benefits for the troubles.
My System SpecsSystem Spec
08 Jul 2014   #5
blablubb1234

Windows 7 x64, Archlinux x64
 
 

Quote   Quote: Originally Posted by gregrocker View Post
Almost all of the win7 repair regimens (many developed here) are upended by UEFI. It offers too few benefits for the troubles.
Well, honestly I don't see what this should have to do with (U)EFI... after all I am still booting both OSs in (U)EFI mode and can use bcdedit, bootrec etc. in Windows RE. So I don't think that being unable to use them before was a (U)EFI feature/issue/bug, but correct me if I'm wrong.

Furthermore it would be tragic if the recovery routines from Windows were not to work on (U)EFI systems in general as it is (unfortunately) very likely that regular BIOS systems are to disappear in the very near future.
My System SpecsSystem Spec
17 Jun 2015   #6
gouravkumar220

Windows 7 Ultimate x32
 
 

Hello

I am facing a similar problem as described here.
Status: 0xc0000225 boot selection failed; required device inaccessible
I used paragon partition software to add my D:/ drive (100 MB Reserved drive) to my C:/ drive (Windows Drive). After merging operation by paragon, when the system restarted it failed to boot up. I tried to repair by using the Windows disk but it is showing this error.
Kindly help me out in getting this sorted as soon as possible. Also i want my data to stay preserved as it is important.
Please elaborate your solution as i am a novice in back-end details of windows 7.
My System SpecsSystem Spec
17 Jun 2015   #7
gregrocker

 

Why would you merge the critical System Reserved partition with C if you don't know exactly what you're doing. This essentially means you were sacrificing your Win7 install. Do you mean to tell us you also don't keep valuable data backed up? This is utterly reckless behavior.

Mark the Win7 Partition Active then run Startup Repair - Run 3 Separate Times
until Win7 starts and has the System flag on its partition.

If you use the bootable Partition Wizard option to Mark Active, then take a picture of the drive map showing all listings and post it back using paper clip icon in reply box.
My System SpecsSystem Spec
18 Jun 2015   #8
gouravkumar220

Windows 7 Ultimate x32
 
 

I detached my laptop HDD and tried to use it as an external HDD so that i can backup any data i can access before doing any operation on it. I can access my E:/ and F:/ drives but can't access C:/. Also, whenever i connect my HDD to another, it asks me to format my C:/. I checked my HDD in the disk management and C:/ is marked as active but its type is defined as RAW. Also when i had tried to explore my C:/ drive, the system popped up a dialog box saying that the volume does not contain a recognized file system. Please make sure all the drivers are loaded and the volume is not corrupted.

Attached is the disk management snapshot. G:, K: and L: are my C:, E: and F: drives respectively


Attached Thumbnails
Status: 0xc0000225 boot selection failed; required device inaccessible-disk.jpg  
My System SpecsSystem Spec
18 Jun 2015   #9
gouravkumar220

Windows 7 Ultimate x32
 
 

I am not able to repair my windows using Windows CD.....When i try through safe mode with command prompt, it lists the drivers loading till asyswrt.sy and after that the system restarts.
My System SpecsSystem Spec
Reply

 Status: 0xc0000225 boot selection failed; required device inaccessible




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Boot selection failed because a required device is inaccessible
Hi all, I'm desperately in need of help. I just talked my gf into restoring her dell inspiron 5010n. It was getting slow and running way too many background programs (she likes to download games). We also believed that it was infected due to some program glitches. Anyway, after copying...
Installation & Setup
the boot selection failed because a required device is inaccessible
I have an Intel i5, Windows 7 Ultimate, and an SSD as my main drive and 2 SATA HDDs. One day, I got a BSOD appeared and my PC restarted restarted. After that, the following error appeared: Window failed to start. A recent hardware or software change might be the cause. To fix the...
General Discussion
Boot selection required device is inaccessible 0xc0000225
Hi, I'm having this error for a while now. this: 0xc0000225 Boot selection required device is inaccessible What happened before this is just a forced shut down because the computer is lagging. After that, this error in now showing up. I have a recovery disk but I can't manage to open it up,...
Installation & Setup
the boot selection failed because a required device is inaccessible
Hy there... I was on my tour to Cyprus and last night I came back I saw my PC uptime was 22days. I asked my brother wht's going on , he told me if you'll shut down pc, i'll not get it stared. Due to some reasons I restarted my pc and now its giving me this error. "the boot selection failed because...
Hardware & Devices
Boot selection failed because a required device is inaccessible
right, i've noticed another thread with the similar problem, here, and apparently it's fixed, but as i'm running my system on a laptop, i'm wondering what i can do to recover my system without any data loss. error message's more or less the same, "Windows failed to start. A recent hardware or...
General Discussion
Boot selection failed because a required device is inaccessible
I tried to bring my computer out of hibernation and was confronted with: 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...
General Discussion


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 00:05.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App