Solved Error code 0x8007045D during Windows 7 Professional x64 Installation

[Gyrger]

I tried to reinstall windows 7 after installing my new Asus M5A97 LE R2.0 mainboard, but the process stops at 1-2% and throws the 0x8007045D
Error message. I quick formatted and repartitionated the HDD. Still the same error. I tried again after low formatting the HDD with partition wizard,
repartitionated again, still getting Error 0x8007045D.

Also updated my bios, ran chkdsk and partition wizards sector check, which both say the HDD is fine, installed xubuntu and archlinux without any problem, reformatted and repartitioned again, changed my SATA-Controller in BIOS from AHCI to IDE, took out 1 RAM module, tried win 7 professional 64-bit without SP1 and win 7 prof. 32-bit. I ran the Installation Disk in both, UEFI and normal mode (of course with gpt partition table in uefi mode and mbr in normal mode), tried different SATA connectors and cables and burned and tried every single iso at least twice (with different programs).

I'm still getting Error 0x8007045D with every single setup I try.

System Specs:

Mainboard: Asus M5A97 LE R2.0 with BIOS Version 1602
Previous Mainboard: Asrock N68C-S UCC
RAM: 2x2GB DDR3 Dual Channel 1333MHz
Video Card: Gainward Nvidia GeForce GTS 450
HDD: Western Digital WDC WD10EALX-009BA0 1TB
CPU : AMD Athlon II X4 640 4x3Ghz
ODD: Optiarc DVD RW AD-7260S

Also interesting:
When I try to wipe out the disk with diskpart after booting the installation disk, it also throws an I/O Error but I don't know what to do about that.

Windows XP Home Premium x86 gets stuck at 2% also, though not throwing an error message.


I am really out of ideas, what to do next but maybe I just missed something during my efforts. It would be really nice to see some ideas or recommendations what to do.

 

[Golden]

Hi,

You covered a lot, so the only thing I can think of is to take the CD/DVD drive out of the equation (although I note you did install a Linux distro using that, in addition to PW).

Download the appropriate Windows 7 ISO here, then use this tool to write it to a 4GB USB flash drive, which also makes it bootable. Insert the drive into a USB2.0 port, and then boot from that and try the installation.

The error is usually an I/O error....although I don't know why you should be able to install a Linux distro and not Windows. Did you install all the motherboard drivers prior to attempting to install Windows 7?

Regards,
Golden

 

[Gyrger]

I'm downloading the image right now but it will take some time, since i only have a 300k connection.
And yes I tried to install the mainboard drivers when the old windows installation was still there, using the support disk delivered with the mainboard, but it gave me some errors too, saying Error reading partition drive x sector (with the x counting up, until I got into the make disk for DOS Menu). This originally led me to format my disk and reinstall windows.

 

[Golden]

Mmmm. And prior to adding the new motherboard, you never had this problem and you were using the same disk? I wonder if there is a problem with the motherboard?

 

[Gyrger]

No I never had this problem before and the asus motherboard is brand-new and only 3 days old. If the USB flash drive won't work, I maybe will contact the ASUS support.

 

[Golden]

What concerns me is that the motherboard is the only new hardware in the configuration since the problem started, so by process of elimination it could be the problem, even if its only a few days old.

Lets see what the USB installation method coughs up.

 

[Gyrger]

Ok, i am extremly happy by now because i just ran a bootable windows repair tool. It changed something on my filesystem but though it didn't tell
me what exactly it did, I am now getting Error code 0x80070002. I will search for that in a minute but though it still not works, another error code is a massive progress after almost 30h of failing repeatedly.

 

[Gyrger]

I just tried the windows installation with the new image and the usb flash drive and its just throwing 0x8007045D again.
I think there is nothing left for me to do except exchanging the mainboard.

 

[gregrocker]

If you ran Diskpart Clean Command and it threw up an I/O error then the problem is almost always the HD. There's no other reason you wouldn't be able to run it unless the installer is bad, so try another one.

Then test the HD with WD's extended CD scan: WD Data Lifeguard CD download page

If it passes boot PW CD to create and format a Primary NTFS partition, mark it Active, run a Surface Scan and Check the File system, or from the Win installer Command Line run Disk Check. If these are all clear, it should install.

 

[Golden]

Greg, we suspect its not the HDD because:

1. On old motherboard and same HDD = no problems
2. On new motherboard with same HDD, Linux installs perfectly = no problems

He got an IO error when installing mobo drivers, so never proceeded with that. The only thing that has changed here is the mobo - thus it is more likely the problem?

 

[gregrocker]

Hi Colin -

Have only seen Diskpart fail with I/O error before when the HD was faulting. Thought that might warrant testing the HD.

The most common fix for install failures of all types is Diskpart Clean Command. If it won't run there is usually a reason, and that so far as I've seen has been the HD.

There could be an anomaly with the installer which is why that was a good first step for you to give.

OP said he did low-level format with PW CD so if that wasn't Wipe Disk from Disk tab he can do that in place of Clean command, then create an NTFS Primary Active partition which again passes Surface and File check - about everything known to prepare the disk on failed install.

 

[mjf]

You say you've changed motherboards - correct. Are your attempting a clean install with a retail version of Windows? or
1) doing a System reimage from your old ASRock motherboard or
2) attempting a clean install from an OEM OS that was activated on the ASRock.

1) or 2) won't work.

If a retail clean install I would suggest you run the WD Lifeguard diagnostics. If you have another HDD then obviously try it.
I know it sounds an obvious thing but did you reset your ASUS BIOS to defaults and download the latest or recent drivers?

Can you get your ASRock motherboard up and running again? If yes and the above fails I'd return your ASUS motherboard. Since you have flashed your BIOS they may balk.

A final point I'd try a straight MBR boot install since you are using only a 1TB HDD.

 

[Gyrger]

@gregrocker
1. I maybe should further mention that the I/O error from diskpart only occurs when i use the "clean all" command, the "clean" command works fine for me. (I don't know if this draws a distinction)

2. I have problems setting up the WD diagnostics tool because i have neither a floppy drive nor a floppy disk. I'm trying to put it on a FAT16 formatted USB-Stick right now but I don't know if I'm destinated to fail with that.

@mjf
I'm trying to do a clean retail install and unfortunately I can't get my old Asrock mainboard to work, because it isn't able to start the power supply. (I bridged the power button and the 24-pin ATX Connector with a paperclip and the power supply started normally without the mainboard).

Last but not least I have no opportunity to switch the HDD, since it is the only one I have right now. So doing that would require me to buy a new one.

Before I do that, I'm trying to wipe format and partitionate the HDD with PW again and maybe I can get the WD diagnostic tool to run in the meantime.

Update:
I rebuilded MBR, wiped, repartitionated and formatted the HDD, sector checked it with PW and chkdsk again as recommended (0 Sector Erros from both), tried to install again and got Error 0x8007045D as always.

Even though I didn't ran the Wd diagnostics yet (still not working with the stick), I really think there is something wrong with the mainboard now.

diskpart is now throwing I/O Errors with both, the "clean" and "clean all" command while every single other partitioning tool
including gparted from Xubuntu's live distro, as well as fdisk, dd, PW and DBAN has no problem at all. I don't know why, but this seems to be some strange "windows-only" problem.

 

[gregrocker]

Western Digital seems to have taken down their Data Lifeguard CD ISO's and only left floppy support (Hello? :huh.

I found this download of the CD ISO, which needs extracting before burning the ISO to CD using Windows Image Burner: Western Digital Data Lifeguard CD ISO (extract first)

 

[Gyrger]

This is interesting. The tool doesn't even find my HDD. With Ide Sata Contoller it recognizes the disk, but when i run quick or extended test it says "Command Error Error/Status Code: 0132".

 

[gregrocker]

Normally the HD Diagnostics are definitive but if PW Surface Scan and File System Check are okay then it may be an anomaly with WD Diagnostics - possibly the reason they've taken them down from their site. I'm inquiring about that now.

Unless you really want to keep the mobo the consensus seems to be to return it. Have you asked their tech support about the issue, in preparation for RMA'ing it?

 

[mjf]

Have you checked your sata cable (try replacing it).
I wouldn't use a Marvell port
Make sure your sata utilities are compatible with the current BIOS version.

I think the basic sata drivers are stock standard Windows - others is this correct?

 

[gregrocker]

As far as I know, Michael. Have yet to see a SATA driver not in the Win7 installer. Older IDE drivers, maybe.

There also isn't any reason to install mobo drivers as Win7 will decide which ones it wants, which I would stick with unless performance dictates importing OEM.

 

[Gyrger]

I have put in a jumper on my HDD scaling down the data transfer rate from 6.0GB/s to 3GB/s. Windows expansion is now at 40% and maybe it'll work .
I think the error was caused because I used only SATAII cables, while both, Mainboard and HDD had SATAIII 6GBps Connectors.

Windows is now installed and works perfectly.

Thanks for the support to all of you

 

[mjf]

I have put in a jumper on my HDD scaling down the data transfer rate from 6.0GBps to 3GBps.

So referring to this
How to physically install, set jumper settings, and set up a Serial ATA, EIDE, or SSD drive in Windows 7, Vista, XP, and 2000
are you saying the default the no jumper default didn't work. Connecting the jumper to pins 5 and 6 worked? It's 3Gb/s not bytes. I know WD say "3Gb/s data transfer speed activated" but you won't get anything like 3Gb/s out of a standard 7200RPM 3.5" HDD. So I'm not sure what the jumper actually does.

I'm a Seagate user for internals so maybe a WD user could explain.

It's good that you seem to have things going.