0xc0000225 error but still works
Hi,
I have 3 identicle systems. HP Z440 with a 128GB SSD drive running Windows 7 Pro x64. I think it's setup as AHCI. Computer 1 and Computer 2 both had SSD drive failures. HP support came out and replaced computer 1 and computer 2 each with a brand new 128GB SSD drive.
I booted into the working computer 3 with Acronis True Image 2016 and took a full disk image and put the image on a shared drive. I then booted into computer 1 and computer 2 and restored computer 3's image onto computer 1 and computer 2.
Now both computer 1 and computer have the same exact problem:
It boots up and stops at this error:
Title: Windows Boot Manager
Status: 0xc0000225
Info: The boot selection failed because a required device is inaccessible
At the bottom of the screen it gives me the option to press ENTER=continue. When I press ENTER it boots into Windows correctly and works just fine. If I reboot the computer it goes back into this screen.
The only I tried is Windows Repair disk = after I boot into it and gives me an error so I can't continue with a disk repair (see image 2 system repair error)
I use Acronis True Image 2016 all of the time on Supermicro and othe HP systems and never had this problem. What is actually causing this and how do I fix?
Thanks for the reply and suggestions. I did verify that the boot order is correct. At the moment, I don't have access to these machines until next week because they are in production. I will try the safe mode test then.
Question:
I found this forum post from three years ago with a user with a simular problem as mine. https://forum.acronis.com/forum/40781
I didn't know there is a server version and a hardware version. This is the point I'm curious about...
Because I created my images using the wrong Boot CD version it caused my images to not be compatible with any of the PC's I tried to put them on.
Is it possible that I'm suffering from the same problem, wrong Boot disk version or is my problem different?
No, Acronis True Image home has only one version. Technically, installing it on Windows server editions is not supported, but should be fine as long as the server version matches a supported OS version that is similar (Windows 10 is the equivalent of server 2016). Acronis supported Operating Systems. Using the rescue media should not matter on any Windows pc as the restrictions are only due to how the software installs when it is installed to the OS. The rescue media all happens offline and doesn't interact with the OS - you're just backing up blocks of data offline.
Now there are a couple caveats with bootable rescue media though...
1) By default, the rescue media is Linux. This allows Acronis to have pre-made rescue media thta can be distributed and used immedately. The downside is that we're backing up Windows machines. In many caseses, the Linux media is just fine. However, drivers are usually what limit the Linux media. If your recue media can see your hard drives and your NIC (if you need network support), the Linux media is fine.
2) If the Linux media can't see your hard drives and/or NIC, then you need WinPE rescue media - this is Preinstallation Environment -it's a mini version of Windows with only some capabilities - it's the same platform that things like a Windows Installer or repair disc run on. With Windows PE, you get the same out of the box drivers that come with the version of the ADK used to build your WinPE. IN many cases, just building rescue media with basic ADK is all you need - especially if using a newer version of the ADK like that for Windows 10 (which, by the way can be installed and used on Windows 7, 8, 8.1 and 10)
3) That said, even the default Windows drivers are not always sufficent for newer hardware and/or custom hardware (some video cards, RAID controllers - even Intel ones, etc.) In those cases, you can add the necessary drivers to WinPE rescue media (which you can't do with the default Linux rescue media)
Good new is, you have Acronis 2016 and I'm assuming you have the latest version of Acronis installed. If so, you can build custom WinPE using our MVP WinPE tool. Just download and install the Windows 10 ADK first (again, it installs on Win 7 - Win 10) and install it. It's a big package 3.4Gb when you pick the first 3 items (those are all you need). Once installed, run our MVP WinPE tool and it will do the rest for you and inject the most common IRST RAID controller drivers for you. If you want to add your own custom drivers you can put them in the driver folder before you run it and they'll be added as sell.
Sounds like a lot, I know. It's really not hard though and once you have ADK installed and run our tool, you'll see it's quite easy. Plus, you get some really nice custom Acronis WinPE rescue media that has a lot of additional functionality. Links are below for the MS ADK download and the WinPE MVP tool.
4) Last - how you boot rescue media is important!!! Especially on any system that is capable of booting both legacy or UEFI. You want to make sure to boot your rescue media to match how the OS was installed when the backup was taken. Why? If you have a legacy OS and boot the rescue media in UEFI mode, the resulting image will be made UEFI/GPT. In some cases this works, but not always. If you have a UEFI/GPT OS and you boot the rescue media in legacy mode, it will result in a legacy/MBR restore.... this will never boot as you can't go backwards.
How can you tell if your is legacy or UEFI? http://www.howtogeek.com/175649/what-you-need-to-know-about-using-uefi-instead-of-the-bios/
How do you know if you're booting the rescue media in legacy or UEFI mode? https://forum.acronis.com/forum/121829#comment-378318
You should run from an admin command prompt bcdedit.
Look for Windows Boot Loader section and confirm that both entries "device" and "osdevice" are bothset as "Partition=C:"
If these entries show as "D:" or "E:" or some ther letter you have found your issue.
To resolve the issue run both commands below.
bcdedit /set {default } device partition=c:
bcdedit /set {default } osdevice partition=c:
Run bcdedit again and confirm that the entries correctly show "C:" is the present.
Wonderfull information you posted. Thank you for breaking this down. I will use this when I have access to the faulty machines in the next week or so. Will post more feedback then.
Thank you for these commands and explanation. I will have access to these faulty machines soon and I will report my findings.
Happy to help. It's kind of like one of those old G.I. Joe shorts - knowing is half the battle :) There seem to be a rash of people getting themselves with clones and encryption and we're trying to help prevent people from starting a clone or restore from within Windows - especially when encryption is being used, but also as a general rule of thumb, because it is just safer.
It's kind of like one of those old G.I. Joe shorts
I have access to this machince tomorrow (Thursday 1/19) and want to run your suggested commands.
You should run from an admin command prompt bcdedit.
How do I get into a admin command prompt pre-windows to run this command? Do I get into a command prompt within Windows or a pre-windows command prompt? Remeber, when I try and run a Windows 7 repair disk, it errors before I get the options.
You can run the commands from within Windows so boot into Windows. Go to Programs, Accessories, and locate Command Prompt. Right click on the Command Prompt entry and select Run as Administrator.
I was able to access these machines and I was able to run bcdedit on both of the machines in question. They both displayed "Partition=C:" for device and osdevice.
What can I try now?
You're saying that under the BCD section entitled Windows Boot Loader the Partition =C is present?
If yes check your boot order and make sure that the correct boot drive is first in the list.
You're saying that under the BCD section entitled Windows Boot Loader the Partition =C is present?
Yes, it's present
If yes check your boot order and make sure that the correct boot drive is first in the list.
Ok, I will have access to this system again in 8 hours I will verfiy this. This hasn't been verfied yet.
Thank You
I have confirmed that the boot order is correct (attached)
When you restored the image to these computers did you select the MBR + Track 0 partition to be included in the restore?
If you did not then you might try doing that. Use the recovery media to do this and you can restore just that partition to the disk by itself to the existing recovered image.
Beyond that it is possible that that the GUID information for the disk has changed and is different than that in the BCD. I would hope that the above MBR + Track 0 recovery would solve that but if not you wold have to rebuild the BCD.
When you restored the image to these computers did you select the MBR + Track 0 partition to be included in the restore?
Yes. I did not personally perform the image creation but I made instructions that stated, "Select the entire disk" which would auto check all of the partitions. And for the image recovery, my instructions said "Recover whole disks and partitions". A remote user performed these steps.
Have a look at the thread linked below, a user with I think the same issue as you. Applying the fix, if in fact this is the case, must be done precisely so make certain that you do have the same problem before you attempt it and then pay close attention to details when you apply the fix.
https://forum.acronis.com/forum/6758#comment-96395
Additionally, you should make certain that the OS disk is attached to the lowest data port number, either 0 or 1.
Thanks for this forum thread, this could be part of my problem. Are you referring to the steps I should follow as layed out in responce #3?
Just want to make sure.
And I'll make sure the OS disk is on the lowest data port.
Unfortunitly, I won't be able to troubleshoot this issue anymore since this needed to get fixed asap. I ended up reinstalling Windows 7 from scratch. That fixed the Windows Boot Manager error from showing up. However, I have another chance to test this. I have the same original problem on another system that was just reported to me today. The original problem is that the SSD drive has disk errors and needs to be replaced. Once I replace the phsical drive with a new drive, I'll then have to restore a disk image onto it. I most likely will run into the same exact issue I posted on this thread so I will attempt the steps above (and the new steps) to fix the Windows Boot Manger problem.
Question
Should I use the same Acronis TI 2016 ISO as before (the Aconis Linux boot loader type) or, should I make a WinPE version with Acronis TI 2017 and insert the nessary HP network and storage drivers?
Post #3 is indeed what I am reffering to. You need to study your BCD output .txt file and compare it with what is posted in the thread. If the same omission is true for you then the recommended commands to fix the problem will work for you as well.
I see no reason to create new recovery media and no advantage or disadvantage in either platform as they only serve to host the True Image application and you are not exxperiencing this due to a driver issue which is the most prominent reason to go with WinPE.
I suspect that the issue has to do with the backup image used in the restore. I would not care to speculate what exactly was the issue but, I would encourage you to recreate that image anew, pay close attention to details, make certain the whole disk, all partitions are included in the backup image created and use that new image when you do this again and see if that corrects the problem as well. I think it just might.