I’m sure you did this, but typing, Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key, into the Google search engine reveals many videos and web pages that may offer solutions to your issue. Here’s one for example: Link.

This message has been edited. Last edited by: trapper189,

Are you sure the SATA cable was plugged into the exact same socket it came from? Sometimes certain SATA ports are shared with something else or have different controllers.

Did you add anything? My last build i added a PCI card and I think it took control of the bus that one of my SSDs was on. I could see it in bios but it couldn’t be used.

I've made SOME progress this morning...

I found my original Windows 10 installation DVD and in that envelope, I found a Repair Disk that I had made. Unfortunately, when booting with the Repair Disk and using the "Startup Repair" option, it was unable to repair.

I then booted with the Windows 10 installation disc and ran a repair from that using "Startup Repair". It stated, "Diagnosing your PC" and then "Attempting Repairs". All that does is just reboot and then go back to the main installation screen...seems to be stuck in a loop.

So my question...IF memory serves, I remember in my former life in IT and desktop support that we would re-install Windows on top of an installation that already existed. When doing that, it fixed the issue and the data and programs you had installed remained intact. Is that a true statement? Is it recommended I go ahead and reinstall Windows on the drive that already has Windows installed on it?

Thanks y'all...I've been fortunate to not had computer issues for YEARS. This is the first time as long as I've lived in this house since 2008.

quote:

Originally posted by trapper189:
I’m sure you did this, but typing, Reboot and Select proper Boot device
or Insert Boot Media in selected Boot device and press a key, into the Google search engine reveals many videos and web pages that may offer solutions to your issue. Here’s one for example: Link.

Looking at that stuff now, trapper. Thanks for pointing that out. [thumbs up]

quote:

Originally posted by Oz_Shadow:
Are you sure the SATA cable was plugged into the exact same socket it came from? Sometimes certain SATA ports are shared with something else or have different controllers.

SATA cables are confirmed to be in correct order. When I was going through the repair steps, I was able to get into a Command Prompt and verify that C: is the installation disk and D: is the data disk. That is the correct order.

quote:

Originally posted by mark123:
Did you add anything? My last build i added a PCI card and I think it took control of the bus that one of my SSDs was on. I could see it in bios but it couldn’t be used.

Did not. Just adding a heatsink/fan that only required to be plugged into a power port. Same power port as the old heatsink/fan.

Real long shot but maybe confirm with a voltmeter that all the power supply voltages are correct? If a change is dragging only one of them down it might cause odd symptoms.

quote:

So my question...IF memory serves, I remember in my former life in IT and desktop support that we would re-install Windows on top of an installation that already existed. When doing that, it fixed the issue and the data and programs you had installed remained intact. Is that a true statement? Is it recommended I go ahead and reinstall Windows on the drive that already has Windows installed on it?

*Make sure you have a viable backup before you do anything.

I think you are beyond a refresh at this point. I have never initiated a refresh on an OS drive that won't boot. Others here might know more about that.

Why not restore your last Acronis backup? If you can't do that you are probably looking at a clean install, reinstalling your apps, and then moving your data back over.

quote:

Originally posted by xantom:
Why not restore your last Acronis backup? If you can't do that you are probably looking at a clean install, reinstalling your apps, and then moving your data back over.

Yup...looking at a way to create a recovery disk from the Acronis website. Just have to find my registration key for that now.

Also looked at a couple of videos of repairing the UEFI partition, which in my old-world speak equates to the Master Boot Record???

Will try the Acronis recovery first and then dive into UEFI recovery.

Sure getting edumicated on new stuff!!! That's my glass is half full approach to this...

You may want to pick up an external USB drive enclosure, Link and install the original HD into that enclosure, since there seems to be an issue with that drive.

I would install a new drive in the computer a quicker SSD and create a new boot drive for the PC, this way you improve speed and capacity, provided the machine will see the new drive and allow that work to proceed.

If it boots with the new drive, and, you can access the old drive through the USB then you should be able to get your data off the old drive, just have to reinstall the applications on the new drive. A benefit may be it will run faster with a clean disk and fresh install,

If you have a spare blank HDD perhaps install it and see if the machine recognizes the drive, if not, you may have a problem with the old MB and as you indicated, time to upgrade, if its as old as you say, it may be time anyway to look at refurbing and upgrading.

Doing this work maybe just allowed an existing time bomb problem to be exposed, feel for your nephew who installed it, probably feels bad that the PC is acting up after he worked on it. Been there done that, always told friends that wanted me to help install things that there is a good chance that a problem will happen and they need to backup all data before the work is done.

^^^^^

Thanks, HRK...I have considered that and I do have a new 2TB SSD sitting in my safe doing nothing.

The BIOS DOES recognize all the drives. Additionally, when I launched the Windows Repair disc, I was able to verify the drives are still intact and all the data is there...ran directories on all the drives. The Repair Disc couldn't repair anything, though.

My brother (nephew's dad) that was here while we were installing the new fan reminded me of something that may have caused the boot disk/record to get corrupted...when the fan was fully installed and the PC put back together, I just turned the PC on to make sure the heatsink fans were working and then shut the system off. This may have corrupted the boot record(s), which is what I'm trying to repair.

Question...when I installed Windows 10 on this system many moons ago, did it create this UEFI directory others have mentioned or did it create the standard Master Boot Record? I'm leaning MBR.

I'm still thinking of booting from the Windows 10 Installation disc to see if I can just re-install the O/S onto my disk without having to format it. As stated...I think I've done that in the past on other systems with older versions of Windows.

And I'm still working on the Acronis System Boot disc to see if I can boot from that and then run a restore from Saturday morning's backup...

quote:

I'm still thinking of booting from the Windows 10 Installation disc to see if I can just re-install the O/S onto my disk without having to format it. As stated...I think I've done that in the past on other systems with older versions of Windows.

I believe what you're looking for is called a "Repair Install"

How to Fix Windows 10 with a 30-Minute Repair Install

quote:

did it create this UEFI directory others have mentioned or did it create the standard Master Boot Record? I'm leaning MBR.

You mentioned your MOBO was an Asus Sabertooth X58. Most likely BIOS and MBR, no UEFI.

GPT vs MBR
https://www.howtogeek.com/1936...artitioning-a-drive/

UEFI
https://www.howtogeek.com/5695...ll-replace-the-bios/

^^^You’re right. The x58 Sabertooth’s manual doesn’t mention UEFI. The manual for the next motherboard, the x79 Sabertooth does.

He'll have to use his Windows DVD to open a command prompt and make sure the correct partitions are marked as active. Then, he may have to rewrite the MBR.

It sure sounds like the boot drive wasn't plugged back in to the SATA port it was unplugged from. I'd unplug every drive except for the boot drive and make sure that drive is the first boot device. Resetting the bios to defaults probably isn't necessary, but may simplify troubleshooting.

is it possible that you have screwed your system boot files?

0-0

quote:

Originally posted by bobtheelf:
It sure sounds like the boot drive wasn't plugged back in to the SATA port it was unplugged from. I'd unplug every drive except for the boot drive and make sure that drive is the first boot device. Resetting the bios to defaults probably isn't necessary, but may simplify troubleshooting.

I screwed up my Master Boot Record. Turned the system on and then shut it off like 6 seconds later without letting it fully boot up.

quote:

Originally posted by 0-0:
is it possible that you have screwed your system boot files?

0-0

That's exactly what I did. My fault...


Here's my fix. Will try it in the morning...



And y'all are correct. This mother board did not yet possess UEFI "architecture". Everything is NTFS and Master Boot Record.

I wouldn't think that would cause it, because there shouldn't be any write actions going on. No data should have been changed.

The fix worked!! I am back up and running on my primary system!

Thanks for all the ideas, tips, and recommendations. I was able to piece all that together to formulate my plan of attack. I now understand what UEFI is! This version of Windows is so old, however, that everything is still under the Master Boot Record "architecture". I had one little hiccup following the video above, but was able to resolve it by referring to that error in another video.

MANY lessons learned!!!!

Good to be back in the 21st Century among the living!!

BTDT.
While reading all the replies my brain was whispering to me that the MBR was FUBAR.
I usually keep a flash drive with the appropiate Windows version to start the repair process.

Glad it worked

0-0

erj_pilot,

Glad to hear you're back up and running. I think many folks don't realize how much they use / rely on their home computer until it goes tits up.

If I had known how old your motherboard was I wouldn't have mentioned UEFI. But given you said that lead you to learn something :thumbsup: