[DR M]

Drive X is what is shown in the recovery environment. It's not the C drive.

 

Be careful: there is a space between the slashes. No other spaces in the command.

 

CHKDSK C:\ /R

[Advertisements]

Hi tried again, same result (as attached).

 

I've copy/pasted your command into Word to check the characters and spaces, I'm sure I've got it right.

 

Is drive C no longer with us?

Attached Thumbnails

• 

[RedSuedePump]

Hi tried again, same result (as attached).

 

I've copy/pasted your command into Word to check the characters and spaces, I'm sure I've got it right.

 

Is drive C no longer with us?

Attached Thumbnails

• 

[DR M]

Let's be sure about the OS drive letter.

 

In the command prompt type BCDEDIT | Find "osdevice" 

 

Enter

 

Take a screenshot of what you get. 

[RedSuedePump]

Hi,

 

It doesn't appear to have found anything (see attached).

 

RSP

Attached Thumbnails

• 

[JSntgRvr]

Drive X is what is shown in the recovery environment. It's not the C drive.

 

Be careful: there is a space between the slashes. No other spaces in the command.

 

CHKDSK C:\ /R

Don't use the back slash.

 

CHKDSK C: \R

[RedSuedePump]

Hi, it's running the CHKDSK now, will get back when it's done.

 

Thank you for your patience.

 

RSP

[DR M]

Thanks, JS. I should remove that slash! 

[JSntgRvr]

Is that a GPT drive on an EFI Mode?

[JSntgRvr]

Why BCDEDIT wont work?

[RedSuedePump]

Hi,

 

and here's the results.

 

Regards

 

RSP

Attached Thumbnails

• 
• 

[DR M]

From what I can see, there is no problem with the disk. 

 

However, let's wait JSntgRvr, who is an expert on un-bootable systems. 

[JSntgRvr]

The disk looks fine.

 

At the prompt type the following:

 

BCDEDIT /ENUM ALL

 

Take a screenshot and post it for us to see.

[RedSuedePump]

Hi,

 

I couldn't get anything to happen with that command (see attached).

 

I checked the command closely and I'm pretty sure I got it right.

Attached Thumbnails

• 

[JSntgRvr]

• Copy the entire contents of the Quote Box below to Notepad.
• Name the file as Fixlist.txt
• Change the Save as Type to txt
• and Save it in the location FRST (FRST64.exe) is saved
• Run FRST (FRST64) as you did before. This time around click on the Fix button and wait
• A Fixlog.txt will be produced and saved where FRST (FRST64) is saved. Please Post its contents in your reply.

CMD: Dir /a C:\
CMD: Dir /a c:\boot
CMD: Dir /a C:\Windows
CMD: Dir /a C:\Windows\System32
CMD: Dir /a C:\Windows\System32\Config

[RedSuedePump]

Hi,

 

Please see attached.

 

RSP

Attached Files

•  Fixlog.txt   850bytes   9 downloads