I'm trying to do a fresh clean install of Windows 7 x64 on a new harddrive (Seagate Barracuda ST31000524AS 1TB 7200 RPM 32MB Cache SATA 6.0Gb/s 3.5") through a USB Key CPU: Intel i5-2500k MSI P67A-C43 (B3) Installing proceeds as normally, until it restarts at Configuring hardware.... The resolution will change and then the error message "Windows setup could not configure windows to run on this computer's hardware" will pop up. I've changed my SATA settings in the bios to ACHI, RAID, IDE and tried installing multiple times under each option but no dice. I've tried loading Intel Rapid Storage Technology Driver from the MSI website prior to the Windows installation, but its giving me an error message about the drivers not being signed. Please help. I've been struggling with this for 3 days.
The error message you get screams for SATA related issue - but seems you have taken a logical approach already. The one I was counting on, was to change from ACHI > IDE. Have you tried loading Failsafe Default settings in BIOS? I presume you haven't changed / overclocked anything I am also a bit wary of this being a graphics issue - as you say that the error comes up immediately after the resolution optimisation part of the installation. Let's just wait and hear some more opinions here ...
I would have to agree with x86 and say it's a SATA issue. My best guess would be the problem is caused by the driver giving you the unsigned error. If you can get the driver installed, I think that will fix the problem. Have you tried using another source for the drivers? Perhaps the ones that came with the MB.
Thanks for all the input, I'm reburning my iso and hoping for the best. As for the drivers, I unfortunately do not have a DVD drive so I cannot technically get the drivers that came with the motherboard, but I am getting it off the website. If worse comes to worse, I think I'll try installing on a different computer then just pop it back in.
This is for Intel CPUs and ICH 7,8,9 and 10. Disconnect the cables to all hard drives except the one you wish to install windows 7 on. If you have a good clean Windows 7 Ultimate ISO from Digital River and used the Microsoft Windows 7 DVD/USB TOOL to unpack the ISO onto a 4GB or larger USB flash drive you're almost ready to start. Open the files on the USB stick and delete ei.cfg in the sources folder.Nows also the time to add a $OEM$ folder to the sources folder if you need it. Put the USB stick in a supported USB port and power up. At the first bios screen press F8 to choose Boot From The USB Stick. On Notebooks you'll need to press a certain F key to pick the boot device. Choose your keyboard /language then Install Now>Agree To EULA>Custom Clean Install Now you come to a window where you can add drivers and disk utilities. Click on the disk utilities and format every partition that is showing.Then delete every partition until only 1 is left. Now click on Add Driver.From a 2nd usb stick install the f6flpy version of the Intel RST version 10.6.0.1002 32 or 64bit. If at this point you see a message that Windows cannot be installed it's probably because the drive was zeroed and not initialized. When RST installation completes click OK and continue the installation. At first reboot during the installation remove all the attached USB sticks. Complete the installation of Windows then install the Intel chipset software version 9.2.3.1017
You are the man. Seriously. This was great advice! To be honest though, not sure if it was removing the thumb drive or using windows 7 with sp1 instead of straight windows 7. Found downloads here: :sorry, can't post links, just search for windows 7 64 home premium sp1 iso, or whatever your version is, to find the links. They will be under a domain like msft dot digitalrivercontent dot net. Make sure it is bundled with sp1 Downloaded the iso and used it to install. I read this post during the part where it normally fails, yanked the usb stick out, and got to the next step. I would do both to be sure. FWIW, When I thought it was a SATA error, I tried to look at the C: drive for errors using the repair utility and did not see any files there. That's what prompted me to look past the error being caused by the onboard drivers.