Hard Drive continues to refuse Windows installation.

Topaez
Junior Member

11-06-2016, 06:30 AM

Recently I purchased Seagate's 7200rpm HDD for a friend's dad and his machine. We've been attempting to install Windows 10 home via the USB we received from Best Buy. But each time we reach the stage where it begins preparing the files, it crashes. What could be causing this issue with a fresh hard drive? This specific model was the one we bought. https://www.amazon.com/gp/product/B01LNJ...UTF8&psc=1

Topaez

11-06-2016, 06:30 AM #1

LoucoDoPC
Junior Member

11-08-2016, 05:23 PM

My assumptions are that the drive is failing or the steering wheel is broken.

LoucoDoPC

11-08-2016, 05:23 PM #2

My assumptions are that the drive is failing or the steering wheel is broken.

PecaPAG
Junior Member

11-11-2016, 11:59 PM

Ram could cause issues during installation by interfering with the system's boot process or triggering conflicts that prevent proper setup.

PecaPAG

11-11-2016, 11:59 PM #3

Ram could cause issues during installation by interfering with the system's boot process or triggering conflicts that prevent proper setup.

BurstMuffin
Member

11-17-2016, 03:35 AM

Relies on the problem being identified; Windows fails to install when it finds defective memory or access issues

BurstMuffin

11-17-2016, 03:35 AM #4

Relies on the problem being identified; Windows fails to install when it finds defective memory or access issues

Streiyn
Posting Freak

768

11-17-2016, 08:21 AM

The installer might be damaged or the hard drive could be faulty. Error code: 0x80070570

Streiyn

11-17-2016, 08:21 AM #5

The installer might be damaged or the hard drive could be faulty. Error code: 0x80070570

damojosh
Member

200

11-17-2016, 09:06 AM

Use the Media Creation Tool to reinstall your USB drive. If the issue persists, try a different SATA cable. If that doesn’t work, the problem likely lies with your drive itself. This isn’t a RAM or memory issue.

damojosh

11-17-2016, 09:06 AM #6

timmyblack
Member

229

11-17-2016, 09:32 AM

It turned out the flash drive was the issue. We ended up creating our own boot drive. This is my first time encountering a completely new drive fail like this.

timmyblack

11-17-2016, 09:32 AM #7

It turned out the flash drive was the issue. We ended up creating our own boot drive. This is my first time encountering a completely new drive fail like this.