This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi, I am trying to install the Creators Update on my computer, but it fails and has to recover every time I try. What system information should I post to help troubleshoot why the update continues to fail?
Thanks!
-Andrew
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
You are welcome. I think that is correct. The clean install already went through Windows Update to pull in OS Build 16299.309 which is currently the latest one. It was the system partition (that holds the BCD) on the HDD that was the real troublemaker. That BCD was activating during reboots that required the one on the SSD, I think. Windows writes to them during an upgrade.
I have a similar, but slightly different issue. After the most recent Insider update my PC would get caught in the Automatic Repair loop. Nothing I tried, auto repair, bootfix, etc.., worked. I disconnected every HD, external (4 RAID5) and internal, and installed a new HD (Windows install complained that my old HD was about to fail despite no issues reported with chkdsk).
After a clean install, I shut down and reconnected my old drive so that I could copy as much of my old data as I could, leaving all other drives disconnected. When I restarted, the OLD drive booted, giving me access to all of my apps and data.
At this point I turned on my 4 external drives, and after some time away from my PC I came back to find that Windows had crashed, with a blurb requesting that I restart. When I did, I found myself back in the automatic repair loop. I turn the 4 drives off again, and I’m booting.
Note that prior to the last upgrade I’ve had these drives connected in some combination for YEARS, with the most recent added several months ago. All are GPT partitions, the smallest being 10TB, and connected via USB3 or eSATA.
My next step is to connect the drives one at a time until I find the culprit. Anybody got any ideas what’s goig on here?
(1) You wanted to copy files from the original HDD to the new one?
(2) You have two internal HDD slots on the motherboard?
(3) When you reconnected the original drive, you left the new one in?
(4) And it booted to the original drive?
Both the new & original HDD have an EFI system partition. UEFI had to decide which to use. Possibly because the slot it occupies has priority over the other, it chose the one on the original HDD. And that one is set to boot the Windows partition on the same HDD.
I think you should open File Explorer & copy your files over. C:\ would be the original Windows. The new one would be D:\ probably. After that, I would unplug the original HDD. I still say Windows isn't meant to have two HDD plugged in that have their own EFI system partition. Or so said a venerable MVP to me long ago - so long ago, I can't quite recall his name.
After that, try to establish your RAID setup with the new HDD.
