Windows could not complete the installation

[dwang040]

I'm not sure what's going on. I created a boot able flash drive, plugged it in, hit f8 or something to select the drive as boot. Then installed. It finished installing amd automatically restart. Then I got this error. So, I rebooted into the installer, deleted all the partitions and started again. This time, I remo we the flash drive and booted with the hard drive. Failed again. I've tried reordering boot priorities and everything but it's just not working. It keeps failing. Finally, all these videos and articles say oh, just hit f10, but I can't cause my keyboard if mouse won't even work when the message pops up. 

[Droidbot]

Specs? 

Fresh build, prebuilt, or used?

Have you tested memory?

 

[DiamondShark286]

can you try reinstalling windows or you could download some sort of bootable reformatting to to reformat the drive then install

[SonoDanshi]

I ran into a similar issue with my last build and it was caused by one of my other hard drives. The simple solution (for me at least) was to unplug all drives apart from the one I wanted to install Windows on and then re-ran the setup from scratch. After it booted into windows for the first time, I shut down and reattached my other drives.

[dfsdfgfkjsefoiqzemnd]

1 minute ago, SonoDanshi said:

The simple solution (for me at least) was to unplug all drives apart from the one I wanted to install Windows on

I generally recommend doing this anyway if you're using more than 1 drive.  Windows has this annoying tendency to put the boot manager on another drive than the one Windows itself installs on.  If you then replace that drive, all of a sudden you're stuck with a PC that doesn't boot anymore. 

[dwang040]

Hmm. After doing the same thing 6 times, I was finally able to get into Windows.... I don't know why it finally worked, given that I did the same thing over and over again. But it was able to boot up. Thanks for all the suggestions. 

[dwang040]

Actually, I did do something different... I didn't use a product key. Instead of typing in the product key, I just said I didn't have one, and it installed. Odd. Thanks again for all the suggestions. 

[DnFx91]

10 minutes ago, SonoDanshi said:

I ran into a similar issue with my last build and it was caused by one of my other hard drives. The simple solution (for me at least) was to unplug all drives apart from the one I wanted to install Windows on and then re-ran the setup from scratch. After it booted into windows for the first time, I shut down and reattached my other drives.

yup, this, every time. For some reason that is beyond me, windows just loves to put it's bootloader on a different drive to where you installed it. I covered this in more detail in my hackintosh article. 

 

 

[dwang040]

It's strange since I only had the hdd connected, my ssd isn't coming until another month. But I still ran into the issue. 

[DnFx91]

1 minute ago, dwang040 said:

It's strange since I only had the hdd connected, my ssd isn't coming until another month. But I still ran into the issue. 

were you trying to install UEFI on a MBR drive ? i've had that mess up installations before

[dwang040]

3 minutes ago, DnFx91 said:

were you trying to install UEFI on a MBR drive ? i've had that mess up installations before

I'm not sure. I think my flash drive was uefi but not sure what my hard drive was. 

[DnFx91]

1 minute ago, dwang040 said:

I'm not sure. I think my flash drive was uefi but not sure what my hard drive was. 

well there are 2 types of partition map that apply to windows, MBR is for legacy installations, and GPT is for UEFI. If you try installing in UEFI mode on an MBR drive, it usually craps out and tells you that it won't work, but sometimes it tries anyway and fails.