Fresh Install Repair loop

I had a 60GB SSD/500GB HDD setup running Win 7 Pro. Windows was installed on the SSD and all my "stuff" on the HDD. I decided I wanted to install Ubuntu on the SSD and just put Windows on the HDD.

I wiped the HDD with DBAN and then tried to install Windows 7 on it. Once installed, I had no network connection (I had to install the driver for my motherboard) and then I downloaded all the updates. Once done, I rebooted and get a screen telling me I can start Windows normally or run a repair because there were errors. I ran the repair and when it rebooted it came right back to that screen.

Now, I still have windows on the SSD so I decided to unplug it and remove it from the scenario. I then installed Windows again (formatting the drive) and the exact same thing happened - I got stuck in the repair error loop. I have done it 2 more times and it just keeps re-occurring.

Are there any steps I am missing? What could I be doing wrong?

Please plug in all drives and post back from the SSD's Win7 a screenshot of Disk Management - Post a Screen Capture Image

If you installed to the HD with the SSD plugged in then it most likely placed the boot files on the old Win7 System partition to configure a Dual Boot. Did you get a Dual Boot menu afterwards?

If so then the solution is to Mark new Win7 Partition Active, power down to unplug the SSD, then boot into Win7 installation media or System Repair Disk to run Startup Repair - Run 3 Separate Times until Win7 starts and has its own System flag. Then install Linux to the SSD with only it plugged in, choose which to boot via the BIOS Boot Menu key.

Or you can unplug the SSD, boot the Win7 media to Clean Install Windows 7
making sure to delete all partitions during Steps 7/8, create and format new to install.

Other tips to get and keep a perfect install are the same as for Clean Reinstall - Factory OEM Windows 7

It came up with two prompts: Windows 7 and Windows 7. The bottom option is the SSD (which I am currently posting this from). I will attempt your first solution now.

Okay, so I did the startup repair for three go around. Then I let Windows boot. I decided I'd try to get some drivers so I went into the devices and printers and let it ddo its thing. It found a couple and didn't find some. Then it wanted to restart so I said sure. It did a DSKCHK and then went into the splash screen. It then rebooted itself and I got the windows recovery deal again. I let it do the repair and I checked the log. It says the root cause is System volume on disk is corrupt. Result: completed successfully. Took about 14 seconds.

So I let it finish. It reboots and I get a screen that says windows is configuring settings. And it just sits at a black screen with an operable mouse, the windows 7 pro logo at the bottom and the power off options on the right. Looks a lot like the login screen with a black background and no prompts.

Any ideas now?

Did you the unplug the SSD when running Startup Repair x3?

I don't know how you got the paging file for the SSD install onto the HD, but it's flagged there. This may be interfering, so move it back to SSD: Virtual Memory Paging File - Change

Otherwise since it's marked Active you should only need to run Startup Repair - Run 3 Separate Times to write the System boot files to the HDD install and start it.

If not unplug the SSD and work through the steps for Overcoming Windows 7 Installation Failures - Windows 7 Help Forums.

If those fail, report back failure point and symptoms then test your hard drive with maker's HD Diagnostic extended CD scan followed by a full Disk Check.

I have had the SSD unplugged. I went through the overcoming windows installation failures tut and when everything finally booted up I got an error: windows discovered a corruption in the file "C:\Documents and Settings". This file has now been repaired. Please check if any data in the file was lost because of the corruption.

Then I got another warning: msoobe.exe -corrupt file The file or directory C:\Documents and Settings is corrupt and unreadable. Please run the Chkdsk utility.

What is going on? Can I just wipe my drive with DBAN again and retry the install? I really need windows up and running soon for work.

Thanks for your continued help, gregrocker.

It isn't necessary to wipe the HD with DBAN or at all unless there is installation failure and then use the commands in Overcoming Windows 7 Installation Failures - Windows 7 Help Forums
which are all that is necessary.

Just unplug all other drives, boot the installer, delete all partitions and create new to begin installing.

First however look over these steps for Clean Reinstall - Factory OEM Windows 7 which compile everything that works best to get and keep a perfect Win7 install. The steps are same for retail.

The msoobe file error pertains to MSE which can be resolved normally by uninstalling and reinstalling it. If not then there is another fix. It seems like a Disk Check was run so you may have had file system corruption and should test the HD to know its condition for sure.

I did as you said. All seemed to go well-no errors. I let it install updates and when it rebooted, I got another recovery error. Then it rebooted a couple of times and now it's stuck at loading operating system...

Can I just do a single DBAN pass and try again?

Have you run DBAN a lot on the HD because it is hard on the drive and unnecessary to zero a drive unless there is data which for security reasons needs to be deleted? I would test he HD with the maker's HD Diagnostic extended CD scan.

What was the exact error message and when exactly was it given? If you're unsure then do the install over following the steps in Overcoming Windows 7 Installation Failures - Windows 7 Help Forums
and this time report back the error and at which step as it says.

It's the windows error recovery screen. I have only done DBAN once on the drive. I'm doing the install over following those steps. The format is at 50% right now. When I go to advanced install once that finishes will I click format again or just go straight into the install? I am skeptical that this will work, though since I've already been through this exact same process once.