I was doing a sfc scan and this was what the screen said :
" Verification 45% complete. Windows Resource Protection could not
perform the requested operation " ( end of quote ). Someone please
explain what are the possible reasons of only 45% completion, and what I
should do to correct that.Thank you.


--
davidjchuang

This has been happening to a few people lately with the percentage occurring
at different points.
sfc /scannow will not repair all files and may even report errors after
being 100% successful.
The data where the errors are located can be rather difficult to extract
useful information. (cbs.log)
(Although the event viewer may provide some useful information the two are
not fully tied together.)

So, try the following first:
(All commands are to be run from an elevated cmd prompt
chkdsk /f
sfc /scannow

If it fails again, try the following:
chkdsk c: /f /r
(This will tell you that the drive cannot be locked, do you wish to run
CHKDSK on the next reboot. Answer: Yes.
While you are not trying to recover bad sectors, you are trying to get
chkdsk to run before Vista is running.)
After the reboot, try:
sfc /scannow

If it fails again, boot with your Vista installation DVD and go to the
Repair section.
Select Repair
If successful, go to the command prompt from the Repair section and try:
sfc /scannow

Should this fail again, your options are getting rather limited.
A re-install may be in order. But before you go there, post back and we'll
see if we can't find the trouble spot in your CBS.log.

Good luck!


"davidjchuang" wrote in message
...

I was doing a sfc scan and this was what the screen said :
" Verification 45% complete. Windows Resource Protection could not
perform the requested operation " ( end of quote ). Someone please
explain what are the possible reasons of only 45% completion, and what I
should do to correct that.Thank you.


--
davidjchuang

Mark;658643 Wrote:
This has been happening to a few people lately with the percentage
occurring
at different points.
sfc /scannow will not repair all files and may even report errors after
being 100% successful.
The data where the errors are located can be rather difficult to
extract
useful information. (cbs.log)
(Although the event viewer may provide some useful information the two
are
not fully tied together.)

So, try the following first:
(All commands are to be run from an elevated cmd prompt
chkdsk /f
sfc /scannow

If it fails again, try the following:
chkdsk c: /f /r
(This will tell you that the drive cannot be locked, do you wish to run
CHKDSK on the next reboot. Answer: Yes.
While you are not trying to recover bad sectors, you are trying to get
chkdsk to run before Vista is running.)
After the reboot, try:
sfc /scannow

If it fails again, boot with your Vista installation DVD and go to the
Repair section.
Select Repair
If successful, go to the command prompt from the Repair section and
try:
sfc /scannow

Should this fail again, your options are getting rather limited.
A re-install may be in order. But before you go there, post back and
we'll
see if we can't find the trouble spot in your CBS.log.

Good luck!


"davidjchuang" wrote in
message
...

I was doing a sfc scan and this was what the screen said :
" Verification 45% complete. Windows Resource Protection could not
perform the requested operation " ( end of quote ). Someone please
explain what are the possible reasons of only 45% completion, and
what I
should do to correct that.Thank you.


--
davidjchuang

Mark, thank you for the reply. My system responded slightly differently
than you indicated, but that's minor. I entered the disk check command
chkdsk /f , then Enter, and I was asked to reboot. I did and the system
started checking, during which I was told " One of your disks needs to
be checked for consistency". It went on and finished the checking and
rebooted automactically ( I didn't have a chance to see what's on the
screen). I keyed in the sfc /scannow again and I got 100% completion.
BUT it said the following :
"Windows Resource Protection found corrupt files but was unable to fix
them. Details are included in the CBS.Log windir\CBS\CBS.log for example
C:\Windows\Logs|CBS\CBS.log "(end of quote)
I tried to key in the C:\Windows\Logs\CBS\CBS.log it said access
denied. So, now I have 2 things to do : 1.) Which disk is not
consistent. 2.) what to do with the corrupt files.
Can I trouble you to show me the way ? Thank you.


--
davidjchuang

Since it made it to 100%, I'd suspect you do not have a problem. SFC has
been reported as being a bit flaky in reporting problems.
Checking CBS.log will probably show you nothing since it made it to 100%,
but the best way to look at it is as follows:
http://support.microsoft.com/kb/928228

This will narrow the huge file down to those entries produced by sfc only.
If there is a file that could not be repaired listed here, then you have
something to work with and you should list those entries on your next post.
If not, don't get too concerned... that would be the flaky nature of sfc.
If you have KB941600 installed, you are more likely to see SFC end
successfully, yet report corrupt files.
http://www.vistax64.com/vista-perfor...e-scannow.html

If you'd like to go further, try the Repair option from the installation DVD
and verify that all your updates have successfully installed as indicated in
the Update History.

You should review Event Viewer for any SXS errors.

Most likely these are clean and you don't have any real problems to worry
about.


"davidjchuang" wrote in message
...

Mark;658643 Wrote:
This has been happening to a few people lately with the percentage
occurring
at different points.
sfc /scannow will not repair all files and may even report errors after
being 100% successful.
The data where the errors are located can be rather difficult to
extract
useful information. (cbs.log)
(Although the event viewer may provide some useful information the two
are
not fully tied together.)

So, try the following first:
(All commands are to be run from an elevated cmd prompt
chkdsk /f
sfc /scannow

If it fails again, try the following:
chkdsk c: /f /r
(This will tell you that the drive cannot be locked, do you wish to run
CHKDSK on the next reboot. Answer: Yes.
While you are not trying to recover bad sectors, you are trying to get
chkdsk to run before Vista is running.)
After the reboot, try:
sfc /scannow

If it fails again, boot with your Vista installation DVD and go to the
Repair section.
Select Repair
If successful, go to the command prompt from the Repair section and
try:
sfc /scannow

Should this fail again, your options are getting rather limited.
A re-install may be in order. But before you go there, post back and
we'll
see if we can't find the trouble spot in your CBS.log.

Good luck!


"davidjchuang" wrote in
message
...

I was doing a sfc scan and this was what the screen said :
" Verification 45% complete. Windows Resource Protection could not
perform the requested operation " ( end of quote ). Someone please
explain what are the possible reasons of only 45% completion, and
what I
should do to correct that.Thank you.


--
davidjchuang

Mark, thank you for the reply. My system responded slightly differently
than you indicated, but that's minor. I entered the disk check command
chkdsk /f , then Enter, and I was asked to reboot. I did and the system
started checking, during which I was told " One of your disks needs to
be checked for consistency". It went on and finished the checking and
rebooted automactically ( I didn't have a chance to see what's on the
screen). I keyed in the sfc /scannow again and I got 100% completion.
BUT it said the following :
"Windows Resource Protection found corrupt files but was unable to fix
them. Details are included in the CBS.Log windir\CBS\CBS.log for example
C:\Windows\Logs|CBS\CBS.log "(end of quote)
I tried to key in the C:\Windows\Logs\CBS\CBS.log it said access
denied. So, now I have 2 things to do : 1.) Which disk is not
consistent. 2.) what to do with the corrupt files.
Can I trouble you to show me the way ? Thank you.


--
davidjchuang

Mark;659096 Wrote:
Since it made it to 100%, I'd suspect you do not have a problem. SFC has
been reported as being a bit flaky in reporting problems.
Checking CBS.log will probably show you nothing since it made it to
100%,
but the best way to look at it is as follows:
'How to analyze the log file entries that the Microsoft Windows
Resource Checker (SFC.exe) program generates in Windows Vista'
(http://support.microsoft.com/kb/928228)

This will narrow the huge file down to those entries produced by sfc
only.
If there is a file that could not be repaired listed here, then you
have
something to work with and you should list those entries on your next
post.
If not, don't get too concerned... that would be the flaky nature of
sfc.
If you have KB941600 installed, you are more likely to see SFC end
successfully, yet report corrupt files.
http://www.vistax64.com/vista-perfor...e-scannow.html

If you'd like to go further, try the Repair option from the
installation DVD
and verify that all your updates have successfully installed as
indicated in
the Update History.

You should review Event Viewer for any SXS errors.

Most likely these are clean and you don't have any real problems to
worry
about.


"davidjchuang" wrote in
message
...

Mark;658643 Wrote:

Mark, thank you for the reply. My system responded slightly
differently
than you indicated, but that's minor. I entered the disk check
command
chkdsk /f , then Enter, and I was asked to reboot. I did and the
system
started checking, during which I was told " One of your disks needs
to
be checked for consistency". It went on and finished the checking and
rebooted automactically ( I didn't have a chance to see what's on the
screen). I keyed in the sfc /scannow again and I got 100% completion.
BUT it said the following :
"Windows Resource Protection found corrupt files but was unable to
fix
them. Details are included in the CBS.Log windir\CBS\CBS.log for
example
C:\Windows\Logs|CBS\CBS.log "(end of quote)
I tried to key in the C:\Windows\Logs\CBS\CBS.log it said access
denied. So, now I have 2 things to do : 1.) Which disk is not
consistent. 2.) what to do with the corrupt files.
Can I trouble you to show me the way ? Thank you.


--
davidjchuang

Thank you, Mark. Went to that microsoft site you suggested. I was
unable to execute the command
" findstr \c:"[SR]" %windir%\logs\cbs.log\sfcdetails.txt "
System said it could not open it. Is it possible that my 32 bit home
premium is unable to execute such command?


--
davidjchuang

Running this command from an elevated prompt:
It should have looked like this:
findstr /C:"[SR]" %windir%\logs\cbs\cbs.log sfcdetails.txt
Not:
findstr \c:"[SR]" %windir%\logs\cbs.log\sfcdetails.txt

Try this one if you want to weed out all the Verified files. (You just want
the problem files.)
findstr /C:"[SR] Cannot repair member file" %windir%\logs\cbs\cbs.log
sfcdetails.txt

I believe the command is available in all versions of Vista.
I think the command you typed in was missing the \cbs directory path and you
made sfcdetails.txt part of the path instead of the piped file.

Once the command is completed running, just enter: sfcdetails.txt in the
Start button Search box and click the file to open.
This article talks about how to replace files sfc could not repair.
http://support.microsoft.com/kb/929833



"davidjchuang" wrote in message
...

Mark;659096 Wrote:
Since it made it to 100%, I'd suspect you do not have a problem. SFC has
been reported as being a bit flaky in reporting problems.
Checking CBS.log will probably show you nothing since it made it to
100%,
but the best way to look at it is as follows:
'How to analyze the log file entries that the Microsoft Windows
Resource Checker (SFC.exe) program generates in Windows Vista'
(http://support.microsoft.com/kb/928228)

This will narrow the huge file down to those entries produced by sfc
only.
If there is a file that could not be repaired listed here, then you
have
something to work with and you should list those entries on your next
post.
If not, don't get too concerned... that would be the flaky nature of
sfc.
If you have KB941600 installed, you are more likely to see SFC end
successfully, yet report corrupt files.
http://www.vistax64.com/vista-perfor...e-scannow.html

If you'd like to go further, try the Repair option from the
installation DVD
and verify that all your updates have successfully installed as
indicated in
the Update History.

You should review Event Viewer for any SXS errors.

Most likely these are clean and you don't have any real problems to
worry
about.


"davidjchuang" wrote in
message
...

Mark;658643 Wrote:

Mark, thank you for the reply. My system responded slightly
differently
than you indicated, but that's minor. I entered the disk check
command
chkdsk /f , then Enter, and I was asked to reboot. I did and the
system
started checking, during which I was told " One of your disks needs
to
be checked for consistency". It went on and finished the checking and
rebooted automactically ( I didn't have a chance to see what's on the
screen). I keyed in the sfc /scannow again and I got 100% completion.
BUT it said the following :
"Windows Resource Protection found corrupt files but was unable to
fix
them. Details are included in the CBS.Log windir\CBS\CBS.log for
example
C:\Windows\Logs|CBS\CBS.log "(end of quote)
I tried to key in the C:\Windows\Logs\CBS\CBS.log it said access
denied. So, now I have 2 things to do : 1.) Which disk is not
consistent. 2.) what to do with the corrupt files.
Can I trouble you to show me the way ? Thank you.


--
davidjchuang

Thank you, Mark. Went to that microsoft site you suggested. I was
unable to execute the command
" findstr \c:"[SR]" %windir%\logs\cbs.log\sfcdetails.txt "
System said it could not open it. Is it possible that my 32 bit home
premium is unable to execute such command?


--
davidjchuang