This is why you should run the Repairs from DVD as stated repeatedly. The System files needed for the repair can be corrupt or offline, requiring the fresh copy on the DVD.
Are you being warned that "Startup Repair needs to check the disk which can take up to an hour" as you reported in your first posts? If this happens and then the Repairs hang it can mean the Disk needs checking with diagnostics/repair CD scan as I've also repeated many times.
But Startup Repair could also be failing because it needs the DVD to run successfully, so get your DVD ready to burn the ISO when ready, using ImgBurn at 4x speed.
I will check in the morning.
Yeah, I should have listened to you... but I'm certainly all ears now. You've started me down the path to recovery and given me hope that this could work out, so I'll definitely listen to your advice from now on.
It's exactly as you say, it warns that it may take over an hour. As I recall, you referred me to a link for the diagnostics/repair CD, but I'm unable to figure out my HDD model and make since I have no access to windows. In that guide, you need to be able to use Windows to figure out the make and model.
I definitely will be ready to burn the DVD, hopefully the right way this time.
Goodnight man!

Thanks again for your patience and help.
In the meantime, I'm going to see if the older windows install iso will produce results when I try running startup repair with it. It may be missing some drivers, but perhaps it can still get this particular job done. I'll also run the system sweep and update on how that and the startup repair go.
UPDATE #1:
As mentioned above, I decided to try booting from the Windows ISO that was missing drivers and see if startup repair would work from there.
I selected repair, and from there system recovery options started looking for installations. Then something unusual happened. I got an error. At the top, it seemed to be named "RecEnv.exe - Corrupt File"
The description: "The file or directory D:\found.000 is corrupt and unreadable. Please run the Chkdsk utility."
My only option from there is hitting "OK".
From there, I am able to access recovery tools, but startup repair comes up automatically.
Even though I originally came to do startup repair, I'm going to cancel it, save that for later and do a chkdsk like the system suggested. Will update shortly with results.
UPDATE #2
Looking at the error message, even someone as non-tech savy as myself could deduce that the system wanted me to do a chkdsk of D:. So I specified as such by typing "D:" in the command prompt and ran the command "chkdsk /f", which gave me the following message:
"The type of the file system is NTFS.
Cannot lock current drive.
chkdsk cannot run because the volume is in use by another process. Chldsl may run if this volume is dismounted first. ALL OPEN HANDLES TO THIS VOLUME WOULD THEN BE INVALID. Would you like to force a dismount on this volume? <Y/N>"
I don't want to select yes until I get the okay from you greg. I just don't want to mess things up, so for now I hit N for no...
It then asks if I would like to schedule this volume to be checked the next time the system restarts. When I hit yes, exit the command prompt, and restart, it just goes back to booting from the CD and the check never happens.
I'm going to move on to startup repairs now and see how that goes on the ISO that's missing drivers. Will update soon!
UPDATE #3:
Startup Repair still gives the "Over hour" warning when I do it on the widnows install iso with missing drivers, so I take it I'm missing something important? Luckily the instal of the ISO is nearly complete at the moment. i powered down as soon as I saw the warning. the only thing left to try is running System Sweeper with my USB.
I will return with my final update of the night when the scan is over.
UPDATE #4
When I attempted to scan, I immediately got an error:
"Standalone System Sweeper encountered an error: 0x8050800c. And unexpected problem occurred. Install any available updates, and then try to start the program again. For information on installing updates, see help and support."
I will try to solve the issue. Will update if I find anything before going to bed.