SEL DISK 0 -> DETAIL DISK:
Disk ID: 2BFC2BFB
Type: SATA
Status: Online
Path: 0
Target: 0
LUN ID: 0
Location Path: PCIROOT<0>#PCI<1F02>#ATA<C00T00L00>
Current Read-only State: No
Read-only: No
Boot Disk: No
Pagefile Disk: No
Hibernation File Disk: No
Crashdump Disk: No
Clustered Disk: No
Volume # / Ltr / Label / FS / Type / Size / Status / Info
Volume 1 / C / RAW / Partition / 232 GB / Healthy
****
SEL PART 1 -> DETAIL PART:
Partition 1
Type: 07
Hidden: No
Active: Yes
Offset in Bytes: 1048576
Volume # / Ltr / Label / FS / Type / Size / Status / Info
* Volume 1 / C / RAW / Partition / 232 GB / Healthy
****
SEL DISK 1 -> DETAIL DISK
Disk ID: 000000000
Type: USB
Status: No Media
Path: 0
Target: 0
LUN ID: 0
Location Path: UNAVAILABLE
Current Read-only State: No
Read-only: No
Boot Disk: No
Pagefile Disk: No
Hibernation File Disk: No
Crashdump Disk: No
Clustered Disk: No
There are no volumes.
****
LIST VOL:
Volume # / Ltr / Label / FS / Type / Size / Status / Info
Volume 0 / D / DVD-ROM / 0 B / No Media
Volume 1 / C / RAW / Partition / 232 GB / Healthy
Volume 2 / E / Removable / 0 B / No Media
-------------------
The only device I had plugged in at the time I listed my disks was a USB mouse. Not sure if that would explain Disk 1...just throwing that out there.
As I stated in my original post, neither System Restore nor System Image work (although I'm positive I had System Restore turned on and running when my computer was functioning). When I tried those options, my system couldn't find anything. Ugh.
A friend I asked for help suggested there might a problem with the Windows Boot Manager, so I tried going through the steps listed
here using the Command Prompt option listed in the System Recovery Options menu. But typing C: into the command prompt gave me this message: "This request could not be performed because of an I/O device error." Does anyone know what this means?
And no, I can't pinpoint what the exact update was...I just know that I had gotten the standard "please restart your computer to finish installing updates" message for a few days and decided to run it on Sunday. I'd assume it was whatever batch of updates Windows put out since their last automatic update.