CALL 8754542653 / 8971423090 [email protected]
Last Updated On April 19, 2018
You are here:
< Back

Click here to learn more

I ran into an issue Ghosting a PC. The PC I am on is an HP Z440 Workstation, the PC has 3 hard drives. One SSD connected via PCIe and two SSDs connected via SATA and configured as a RAID. The goal was to install Windows onto the RAID, however I made the error of installing to the PCIe SSD. I didn’t realize that I had made this mistake until after I had done a fair bit of configuration (installed all drivers, updates, apps). I figured I could simply use Ghost to capture an image of the PCIe SSD and then push it out to the RAID. The imaging process completed successfully however some very strange things happened when the PC booted.

I was logged in with a temp profile, and nothing would run except for Regedit and Command Prompt. My system drive was also being mounted as D: rather than C: After doing a bunch of research I found the issue was related to a registry key at HKLM\SYSTEM\MountedDevices and I just needed to rename the key \DosDevices\D: to \DosDevices\C: (and vice versa). After a reboot everything was working perfectly again.

There was one other oddity though. In Disk Management the PCIe SSD (which now contains a single volume D:) is listed as Disk0 meanwhile the disk containing my system volume C: is listed as Disk1. I was under the impression that while strange this was nothing to be concerned about.

So the issue started when I brought the PC to the end user, he has an external USB drive. I mounted this drive as B: for him (his preference), and everything was fine, but when I rebooted the PC it no longer boots to windows.

I would reach the Windows Boot Manager and get the “Windows failed to boot” message. I had the option to launch startup repair but it would start loading windows files and suddenly bring me back to the Failed to boot screen, starting Windows Normally also would fail. I tried putting in a Windows Install Disk to reach startup repair from there but I recieved a message: “This version of System Recovery Options is not compatible with the version of Windows” (I think this issue is because the install disk does not have the Intel RAID driver loaded). When I unplugged the External Hard Drive, I was able to get to the startup repair, I was met with a message that no OS was found and it asked me to load storage drivers. I loaded the drivers and it immediately asked to reboot itself. On reboot I could again boot to Windows, but that just put me at square one, and when I tried reconnecting the external HDD the same issue occurred.

Thinking the issue was related to the BCD I tried following the steps here but it didn’t resolve the issue. I’m also now receiving an new error when I try to boot with the external HDD attached error code 0xc225 and don’t have the option to launch start-up repair. Removing the external HDD then selecting “use last good configuration data” will again allow me to boot.

Any help would be really appreciated I’d like to avoid reinstalling Windows and starting over considering the rest of the PC is good to go. 

solution: Figured the issue out later on. The External Hard Drive was a Western Digital MyBook. Windows apparently needed an SES drive installed for this device. Without that Windows would fail to boot. Strangely the issue was only during boot, so I was able to disconnect the drive boot to Windows plug in the drive, and right at the root of the drive there was the package for installing the SES driver.

I ended up reinstalling Windows and starting from scratch anyways because I was concerned that Windows was seeing the C:/ volume on Disk1 rather than Disk0, and the network driver became very strangely uninstalled. Assumed these were surface issues to potential larger problems down the road, and figured I would cut my losses.