How to fix corrupted boot up

BretMan · 5 Days Ago

Been fighting this problem since it happened over week ago and I'm out of ideas since I don't have your knowledge. Need your help now.

My Dell XPS8910 running Windows 10 v22H2 was running fine and I did a routine sfc /scannow which fixed a few things and then I rebooted, then Windows did what seemed to be an update stating " ... 33% complete" on the way out. On the way back, reboot never happened. I do get the blue screen with all the repair options, repair attempts, diagnosing, stopcodes. I can access CMD, advanced tools etc. although the CMD prompt always starts with system32>x: and not c: - not sure what that's about. I can't get into Safe Mode and SFC just fails.

Years ago this forum helped be with a big fix by doing a repair/install in-place and I still have the Windows v1607 disk for that but for it to work and fix the boot problem I need to get into Windows.

I backed up my data. I've been trying to create a bootable USB to put v1607 on it or v1703 but I can't find where to get a clean one to download of that one. I can get into the BIOS but there's no option to boot from USB. Maybe the disk will work if I can select for it.

One small success in trying to repair the boot today in CMD with x: is I was trying the fix the boot issue with bootrec /fixboot and got "Access denied". Then entered bootsect/nt60 sys and that was successful stating it updated the fat23 filesystem boot code on all targeted volumes. Not sure how that helped as it seems to be the same otherwise.

My goal has been to get the boot issue fixed, then run the in-place repair. I need to fix the boot through the CMD somehow, unless there's a better way.

Please advise.
Thank you

spunk · 4 Days Ago

When you are in the RE (recovery environment) the Command Prompt loads to the virtual drive X:
To run any commands, you have to change the Drive letter to the Windows OS drive by typing the drive letter (ie) C: or whatever and pressing Enter, before you can run a command.
To find out the Windows OS drive letter,
At command prompt (x:\sources) type this exactly as written:
bcdedit |find “osdevice”
(Must include "and the | ), the | before Find is the Upper case \ key) press enter. This will tell you what drive letter the OS is on. It may not be on the C: drive.

It sounds like your drive may be failing.
At the x sources type: chkdsk c: /r press enter, 5 stages of check disk will run. It will test the HDD for errors. it may take a while. If it takes overnight, then that is a sign the drive needs to be replaced.

If your drive is healthy, We do not suggest doing a Repair Install with versions 1607 or 1703. These are no longer supported. The latest version of Windows 10 Is 22H2. Download the Windows 10 ISO and burn it to a USB Flash drive using the Media Creation Tool on the same page.
You can boot off of the Windows installer, chose your Language, then Repair Your Computer. The Troubleshooting menu will come up and you can immediately press Shift+F10 to take you to the command Prompt where after Changing to the Windows OS drive, you can run the command bootrec /rebuildbcd and press enter.

SIW2 · 4 Days Ago

At command prompt (x:\sources)

why? the default prompt should be ok as far as I know.

FreeBooter · 4 Days Ago

The boot error message will be helpful.

dalchina · 4 Days Ago

then I rebooted, then Windows did what seemed to be an update stating " ... 33% complete"

Depending on what the message was that could have been an update being processed, or maybe chkdsk...

I would start with absolute basics- check your disk.

You have at least 2 options.
a. Option 1:
How to Check Drive Health and SMART Status in Windows 10
- command prompt at boot in your case.

Note: blue text in tutorials is a link.

This would give you an idea of the SMART status of your drives.

I note you have 3. Check all.

b. On another PC create a live boot disk (on a flash drive e.g.). Google if unsure.
Download the iso file e.g. Bob Omb's, Hiren's, then use e.g. Rufus and instructions from the tutorial on creating a bootable drive to install Win 10 but using this iso file.

Such boot disks usually include disk check tools e.g. Crystal Diskinfo

As said above, forget your 1607/1703 disks. Whilst you could boot your PC from them and hence into a command prompt, and perhaps use Startup Repair, far better to create a current one on another PC.

Booting from USB drive. Google can help:

SIW2 · 4 Days Ago

from winre you could try

troubleshoot>advanced options>uninstall update

or reset pc.

If the above doesnt help, then you could try using a bootable usb.

I can get into the BIOS but there's no option to boot from USB.

that might not appear unless there is a bootable usb already plugged in.

dalchina · 4 Days Ago

that might not appear unless there is a bootable usb already plugged in.

The method for Dell booting from a USB by pressing F12 on POST is in my previous post..

BretMan · 3 Days Ago

Thanks for your replies and suggestions. I'll try to give quick answers to each of you and some answers may overlap with similar suggestions.
spunk: I ran chkdsk c:s /r and although the original "ETA" was over 12 hours, it adjusted as it went along and it completed the 5 stages in 1:3 hrs resulting with "... found no problems".

I'm replying here using my old Asus laptop which has some failing keys on the keyboard. I have to tap some keys repeatedly for them to type a character. My workaround is a wireless keyboard. However, it so happens the "esc" key is the Asus hotkey for entering into the boot menu at startup and isn't working at all. My wireless keyboard doesn't connect until the boot happens. I mention this because I created the Windows .iso with the Media Creation tool into a 128GB SC in a USB adapter - I think. I say I think because I can't confirm it by checking what's on the SD card in the USB port because although I hear the plug n play ok tone when I plug it in, it doesn't list in File Explorer. Is there a way to see the contents via CMD? Will a USB wired keyboard resolve this? Also, say the .iso is in there ok, what's supposed to happen when I plug it in - does it autoplay or do I have to find an ".exe" or the like to launch the .iso? Does the term "mount" mean when an .iso "extracts" the folders and files into the same space, similar to unzipping a zip file? Should I see a single ".iso" file or several files and folders?

SIW2: I'm still not clear if it matters whether I'm in X: or C:, as the commands still seems to work in either one.

FreeBooter: If you mean the Stop Codes that usually have come up after every boot attempt fail cycle, I wrote some down before they disappeared when it went on to Advanced options page. They are: irql...unexpected_store_exception, system_thread_account_cant_handle, driver irql_not_less_or_equal, kmode_exception_not_handled, unexpected_store_exception. After the bootrec /fixboot success, I got another one: page_fault_in_non_page_area. These may not be exactly correct as I was rushing to write them down.

DalChina: Sounds good to try. First I need to learn how to confirm what's on the USB drive (see above). FYI - BretMan bonus: I went to Office Depot to get another USB drive and they have a good deal for a PNY pack of three 64GB USB 3.0 for $40!

dalchina · 3 Days Ago

a. I say I think because I can't confirm it by checking what's on the SD card in the USB port because although I hear the plug n play ok tone when I plug it in, it doesn't list in File Explorer.
b. Is there a way to see the contents via CMD? Will a USB wired keyboard resolve this?
c. Also, say the .iso is in there ok, what's supposed to happen when I plug it in - does it autoplay or do I have to find an ".exe" or the like to launch the .iso?
d. Does the term "mount" mean when an .iso "extracts" the folders and files into the same space, similar to unzipping a zip file? Should I see a single ".iso" file or several files and folders?

a. What's a SD card doing on a USB port.. do you mean you have an adaptor? Not sure what how an SD card relates to this.. maybe someone has put the puzzle together...

b. As you know if you plug in a valid disk you should be able to see it in file explorer. If not, I can't see how a command prompt would help.

Rather than looking at your old disks, as you have huge new ones, use the media creation tool to create a current Win 10 bootable disk.

c. When you plug in a USB disk, Autoplay should do whatever you set it up to do. Have a look at your Autoplay settings.

d. When you rt click and Mount an iso file, a new drive letter is created and opening that, you can see the content of the iso file.

BretMan · 3 Days Ago

a. - I searched about how to use the Media Creation Tool and found it didn't matter if a USB thumbdrive or an SD card in a USB flash card adapter was for used for this. When I plug it into the laptop that created it, to check its contents, the USB adapter blinks and I get the PnP ok tone but nothing else happens and I don't see it come up in File Explorer.

b. - Ok. How then do I check the contents of the drive which is supposed to now have the .iso file in it that was just created?

c. - How do I find and adjust the autoplay settings?

d.- What do I r-click on? I can't see what's in the USB drive. " I can't see how a command prompt would help." Your'e saying CMD can't show the contents of USB drives?

Also, the Windows on the Media Creation Tool, if it's to fix the corrupted files I have, that will be great. However, to do that, I don't want to lose my installed apps or settings, just fix what's corrupted. It has that option, correct?