BSOD - no access to Windows or safe mode - Bad System Config Info

Windows 10 1803 started having problems with October 2018 Update. Would not upgrade to 1809 and so had several updates pending. Contacted Microsoft support. They said they would just disable updates and I could carry on with 1803. A few days later the updates message started again and I put it off. Then one morning I had to restart my computer and there was the Blue Screen of Death! I assume the update tried again.
Tried manual updates, tried to remove previous updates, tried to reset config to default, tried to rebuild bootrec, tried to reinstall Windows from ISO file. All I have access to is command prompt.
At the very least, I need to get my files off of this hard drive before I wipe the drive and start over. I don't know what to do next.

My C: drive says it is System Reserved. Is there a way around that? C is where all my personal files are.

- - - Updated - - -

Tried Kyhi's recovery disk. Booted the computer and it went to automatic repair...again. I cannot get to any Windows tools. I only have access to command prompt.

AmityJane said:

Tried Kyhi's recovery disk. Booted the computer and it went to automatic repair...again. I cannot get to any Windows tools. I only have access to command prompt.

1) When you power on the computer what do you see?

2) Did you use the hardware method (three power ons) to boot to the computers windows advanced troubleshooting menu?

3) Had you seen options for either reset, startup repair, or system restore?

4) Was there a srttrail.txt report?

5) Had you created a bootable windows 10 iso?




6) Consider using a bootable Ubuntu flash drive as another option to backup files and to test the drive.

Create a bootable USB stick on Windows | Ubuntu tutorials

Linux to the rescue! How Ubuntu can help a computer in distress | PCWorld

Hard Disk Sentinel - Free Linux version

1) When you power on the computer what do you see? The computer goes immediately into automatic repair mode.

2) Did you use the hardware method (three power ons) to boot to the computers windows advanced troubleshooting menu? I have done that but it goes to the same menu as when I first start it up.

3) Had you seen options for either reset, startup repair, or system restore? Yes, within the Automatic Repair and going to Advanced Options and Troubleshooting and Advanced Options.

4) Was there a srttrail.txt report? After trying one of the methods, I got Logfile: E:\windows\system32\Logfiles\Sct\SctTrail.txt But no data. I don't know if it will help, but after trying to copy using Notepad, I got the Error 0x80004005 and somewhere along the way, I also got Error 0x80070003

5) Had you created a bootable windows 10 iso? Yes and when I get to the part where I should be installing, it tells me selected "Windows cannot be updated to this disk. The selected disk has an MBR partition table. On EFI systems, Windows can only be installed to GPT disk."



6) Consider using a bootable Ubuntu flash drive as another option to backup files and to test the drive. I will download Ubuntu to a flash drive and try that.

1) Find two flash drives that you can format (> or = 8 GB)

2) On a working computer create a new bootable windows 10 iso:
Download Windows 10 ISO File | Tutorials
Download Windows 10

3) Create a new Kyhi boot rescue flash drive:
Windows 10 Recovery Tools - Bootable Rescue Disk Solved - Windows 10 Forums

4) Click system restore > start with the oldest restore point and keep repeating until there are no longer any restore points

5) Click startup repair and see if there is a new srttrail.txt

6) open command prompt and type:

Code:

bcdedit | find "osdevice"
bcdedit /enum all
diskpart
lis dis
lis vol
sel dis 0
det dis
lis par
sel par 1
det par
sel par 2
det par
sel par 3
det par 
sel par 4
det par
sel par 5
det par
sel dis 1
det dis
lis par
sel par 1
det par
sel par 2
det par
sel par 3
det par 
sel par 4
det par
sel par 5
det par

7) Use a camera or smartphone camera to take pictures and post images into the thread

Attachment 232859Attachment 232860Attachment 232862Attachment 232864Attachment 232865Attachment 232866Attachment 232867Attachment 232868Attachment 232869Attachment 232870

There were missing commands and results:
bcdedit | find "osdevice"
sel par 1
det par
sel par 3
det par


Run these commands and post images into the thread:

Code:

bcdedit | find "osdevice"
c:
dir
d:
dir
e:
dir
f:
dir
diskpart
lis dis
lis vol
sel dis 0
lis par
sel par 1
det par
sel par 3
det par
sel dis 6
det dis
lis vol
lis par

(take a picture)

exit

Dism /Image:F:\ /Cleanup-Image /RevertPendingActions
(reboot)


bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

Caledon Ken
How did you create Kyhi's recovery disk, USB or CD/DVD. If you got repair or other window message your recovery boot media or the process you are using to boot is incorrect. I see zbook is also recommending recreating media.

I formatted a flash drive, downloaded Kyhi to my laptop and then copied it to the flash drive. Do you think my flash drive isn't working right?

- - - Updated - - -

Sorry I missed those. I've attached photos under each one to keep them straight.

zbook said:

There were missing commands and results:
bcdedit | find "osdevice"
sel par 1
det par
sel par 3
det par


Run these commands and post images into the thread:

Code:

bcdedit | find "osdevice"
Attachment 232904
c:
dir
Attachment 232905
d:
dir
Attachment 232906
e:
dir
Attachment 232907
f:
dir
Attachment 232908Attachment 232909
diskpart
lis dis
Attachment 232910Attachment 232910
lis vol
Attachment 232911
sel dis 0
lis par
Attachment 232912
sel par 1
det par
Attachment 232913
sel par 3
det par
Attachment 232916
sel dis 6
det dis
Attachment 232917
lis vol
Attachment 232918
lis par
Attachment 232919

(take a picture)

exit

Dism /Image:F:\ /Cleanup-Image /RevertPendingActions
Attachment 232920
(reboot)

I did not perform these bootrec commands because of the error on the image clean up. Should I continue with these anyway?

bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

- - - Updated - - -

I posted a lot more pics than what came up in my post. I'll try again in a few posts. Maybe it was too much at once.

Attachment 232921Attachment 232922Attachment 232923

- - - Updated - - -

Attachment 232924Attachment 232925Attachment 232926