[HMiddleton]

System restore did not work. No create point.
When running SeaTools, I believe it said logging test failed on the long test. When prompted, I chose repair.
holly

[Advertisements]

Go back to the advanced boot options.
Choose
Repair your computer
Then the cmd prompt.

At the prompt type this

sfc /scannow /offbootdir=C:\ /offwindir=C:\windows

That will if it runs check the system files.
If it does run and reports it has found errors and corrected them.
Then RUN it again.
If it then reports it HAS NOT FOUND any errors exit the cmd windpw
by typing exit and keying enter.

Then click restart.

NOTE - Please attempt to post the exact messages seen in the cmd window.

[Macboatmaster]

Go back to the advanced boot options.
Choose
Repair your computer
Then the cmd prompt.

At the prompt type this

sfc /scannow /offbootdir=C:\ /offwindir=C:\windows

That will if it runs check the system files.
If it does run and reports it has found errors and corrected them.
Then RUN it again.
If it then reports it HAS NOT FOUND any errors exit the cmd windpw
by typing exit and keying enter.

Then click restart.

NOTE - Please attempt to post the exact messages seen in the cmd window.

[HMiddleton]

Im not really sure what to look for so I will include what happened.
/scannow /verifyonly /scanfile /verifyfile /offbootdir /offwindir (all state what they do.)
offbootdir and offwindir say: for offline repair specify the location of the offline directory.

sfc /scannow
sfc /verifyfile=c:\windows\system32\kernel132.dll
sfc /scanfile=d:\windows\system32\kernel132.dll /offbootdir=d:\ /offwindir=d:\windows
sfc /verifyonly

x:\windows\system32>

That is all it did. I exited and restarted the computer.

[Macboatmaster]

I THINK, but I am not certain that you may be inserting the wrong cmd.
YOU TYPE the whole cmd as I have given it to you.
TRY AGAIN PLEASE -

Does this help - if it does NOT work with the cmd I gave you substute the drive letter C with the drive letter D - as shown in the IMAGE

sfc /scannow /offbootdir=d:\ /offwindir=d:\windows

To scan the integrity of all system files and repair them, run this command:



If this does not work this time - we will move to the next cmd.
Please do realise THAT you are doing well.
The few hiccups are to be expected.

[HMiddleton]

Tried again, both ways, and still did not work.
Holly

[Macboatmaster]

When you open the cmd window - what please is the prompt at which you are typing it.
See my image please on my post 49.


and when you did type it ALL the command at once and then press enter

what message did you receive please

/scannow /verifyonly /scanfile /verifyfile /offbootdir /offwindir (all state what they do.]

as you tend to suggest in your post 48 that it was this one. - in the quote above.

[HMiddleton]

the prompt is x:\windows\system32>

/scannow scans integrity of all protected system files and repairs files with problems when possible.
/verifyonly scans integrity of all protected system files. No repair operation is performed.
/scanfile scans integrity of the referenced file, repairs file is problems are identified. Specify full path <file>

/offbootdir for offline repair specify the location of the offline boot directory
/offwindir for offline repair specify the location of the offline windows directory
e.g.

sfc /scannow
sfc /verifile=c:\windows\system32\kernel132.dll
sfc /scanfile=d:\windows\system32\kernel132.dll /offbootdir=d:\?offwindir=d:\windows
sfc /verifyonly

[Macboatmaster]

the prompt is x:\windows\system32>

type

cd /

and key enter.
That should take you to an X prompt.

See once more the image on my post 49

You can see the result showing the scan starting.

The / key has ? on the shift key - you are not by any chance typing the ? are you - for sfc /scannow AND then the ? instread of the next /.



If this does not work this time after ensuring you are at that prompt and typing the cmd correctly - with the spaces and the slashes those are clearly shown on the image.

Then at the prompt
type

dir C:

that is dir (space) C:

does that show a list of items including the Windows directory.

This cmd is typed at the X prompt NOT the X system 32 etc.

If that does not list items including the Windows.

type

dir D:


Signing off - goodnight 0201 hrs in UK back 1900hrs

[HMiddleton]

At the x:\> prompt, it said windows resource protection could not start the repair service. I tried with both c: and d: and d: is the only one that got this response.

when typing dir c: windows directory was listed
Holly

[Macboatmaster]

I am sorry to labour the point yet again - were you typing

The / key has ? on the shift key - you are not by any chance typing the ? are you - for sfc /scannow AND then the ? instread of the next /.

as the result YOU say you got is exactly the result you would get if you DID type the ? instead of the /
The ? means please tell me the available commands on sfc /scannow..

If you WERE do not worry - it is an easy error to make. It seems that you may have been - as the message now you say is Windows resource protection could NOT start the repair service..

I think the only way that message can have changed is if the first time you were typing the ?.

Before we proceed further - we really need to address this issue - as the opening post on your thread - was I have been getting dll errors.

[HMiddleton]

I absolutely did not type a ?. I typed it exactly as you stated. I double-checked it each time to ensure it was typed as you asked. I put the spaces where indicated as well. I tried several times each using c: and d: in the command.
The message immediately changed when I was able to change the initial X:\windows\system32> to x:
Holly

[Macboatmaster]

Thanks.

Sorry - it must be something I am missing - I have never had that message except as a result of the ? - if you were to type it - that is the message you would receive.
For instance believe it or not you would type
sfc /scannow? and then after the question mark you could type pink elephants or any word you wanted - as the cmd has been completed by the ? and whatever else you type is irrelevant.


Anyway - I am sorry to have laboured the point, but I can assure you it was important.
It was my error in not spotting the exact cmd prompt.

PLEASE type NOW at the X prompt
C:

then at that prompt type
bootrec /fixboot

If that runs you should receive a message.
Please POST the exact message.

[HMiddleton]

No need to apologize.
The message was "The operation completed successfully."
Holly

[Macboatmaster]

HOLD YOUR BREATH - but not too deeply.


TRY a normal boot.

[HMiddleton]

No luck. Boo... Hiss...
Holly