[Macboatmaster]

Go back please to post 34 - I asked you for the chkdsk results - I do not think you ever posted a reply.
We then ran the SMART check on the disc and it failed.
We then ran Seatools and you say it failed the extended and you clicked on repair.

If I am correct please go back to the Repair your computer that you have been using for the last few posts and this time
type at the X prompt

chkdsk C: /r

Agree any message and then WATCH please the screen so that you can post me details of the results, if you see them.
We are concerned with any report of a failure to run OR the report of bad sectors - OR a report of File errors COULD not be repaired.

[Advertisements]

When trying to run chkdsk, I got this:
Chkdsk cannot run because the volume is in use by another process. chkdsk may run if this volume is dismounted first. ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID. Would you like to force a dismount on this volume? (Y/N)
Holly

[HMiddleton]

When trying to run chkdsk, I got this:
Chkdsk cannot run because the volume is in use by another process. chkdsk may run if this volume is dismounted first. ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID. Would you like to force a dismount on this volume? (Y/N)
Holly

[Macboatmaster]

as before Y

[HMiddleton]

Windows has made corrections to file system. AND...
Failed to transfer logged message to the event log with status 50.
Holly

[Macboatmaster]

We tried earlier the system file checker in what is known as offline mode.
That refers to the fact that you are not initiating the cmd from Windows.

As you know it did not run.

Try this please -
Go back to the cmd prompt.

Type
cd C:\Windows\System32.
Key enter
check that you are now at that cmd

Type
sfc /scannow

Key enter

Please tell me exactly what message you receive.

[HMiddleton]

States:
There is a system repaire pending which requires reboot to complete. Restart window and run sfc again.

I rebooted computer and tried to run sfc again, and got same message.
Holly

[Macboatmaster]

The next attempt at repair is more complicated than anything you have done.

I have no way of knowing if it will work.

Indeed NO ONE at this stage can have any way of knowing if this is repairable.
OR if you are facing a reinstall.

EVEN then we may find out when we attempt the reinstall or recovery from the partition of the hard drive, that the HARD drive is failing and all will be down to a NEW hard drive.

When I say it is more complicated I mean the commands are more involved - they just require great care in typing them correctly.
That said you are doing GOOD.

Are we carrying on with the attempt to solve on the cmd prompt please.

[HMiddleton]

Yes, sir.
Holly

[Macboatmaster]

cmd prompt

Go to C: prompt
type

bcdedit /v

please tell me how many blocks of entries appear and the title of them

The first line after the title is Identifier - I do not need it
The second line is device = please tell me what
The third line is likely to be path - please tell me - or whatever line that is on.
The others I need are O/S device and
System root

TYPE the details please of each entry I have asked for.

[HMiddleton]

The second line is device = partition=c:
The third line is likely to be path - \Windows\system32\winload.exe
The others I need are O/S device - partition=c:
and System root - \Windows

[Macboatmaster]

Take it a little more slowly it will save time in the long run - please

please tell me how many blocks of entries appear and the title of them

I have signed off - goodnight.

[HMiddleton]

Windows Boot Manager
Windows Boot Loader

[Macboatmaster]

Windows Boot Manager - device - partition C as well

Run this please back on the cmd prompt at the C:\ prompt

tasklist /fi "status eq not responding"

as shown here including the quote marks.

[HMiddleton]

was very careful in checking...
at the c: prompt I typed tasklist /fi "status eq not responding"
this is the response:
'tasklist' is not recognized as an internal or external command, operable program or batch file

[Macboatmaster]

The difficulty we face is that, in the absence of knowing what type of file corruption has occurred, we do not know what exactly to attempt to repair.

Indeed as I have said before it may be that the whole problem has been caused by the errors on the hard drive and this was the original reason for the dll.error messages.

Try this and if this does not help I feel we will have to proceed to a recovery or reinstallation of the operating system, even that may fail if the disc itself is failing.
Go to command prompt
Change directory so you are in the \windows\system32 folder
To get to that directory at the C:\> prompt type
cd Windows\system32
Key enter
You will then be at that prompt
Now type each of these commands, and enter after each command.
ren system system.bak
ren software software.bak
ren sam sam.bak
ren security security.bak

Then type each of these commands and enter after each command.
copy c:\windows\system32\config\regback\system
copy c:\windows\system32\config\regback\software
copy c:\windows\system32\config\regback\sam
copy c:\windows\system32\config\regback\security

The first set of commands rename the entries.
The second set of commands replace the entries with those from a backup location.
If the problem is registry corruption this MAY solve it.