New sfc /scannow Error

  • Thread starter Thread starter HMT
  • Start date Start date
H

HMT

There was a bug reported here in sfc.exe (sfc /scannow at command prompt)
Nov. 27, 2007 at the following Microsoft Discussion Group link:

http://www.microsoft.com/communitie...D18D-FA0E-A366-6E527B0FBA67&lang=en&cr=US&p=1

This bug is not limited to a software conflict with KB941600 as noted in the
link above. I ran sfc.exe after three Vista re-installations: (1) with no
Windows updates, (2) with all Windows updates and (3) with all Windows
updates except KB941600. In all three cases, sfc.exe stops at 99% and
reports: "Verification 99% complete. Windows Resource Protection found
corrupt files but was unable to fix some of them." Examination of the cbs.log
file revealed no files listed as corrupt or missing as described in KB928228
or KB929833. In other reported cases from Google search, sfc.exe stopped at
99%, 98% and 68% with cbs.log reports of files missing or corrupt that could
not be fixed. In some cases, files were listed as missing or corrupt in
cbs.log. In other cases, there were none listed even though they were
reported as such in the command prompt summary.

This is a very important program in my opinion and one that was able to
repair several Windows XP installations in my past experience as a
hardware/software tech. Please try and get a fix for this issue ASAP. If I
can help troubleshoot this further, like providing my cbs.log files, please
advise.
 
My Sony VGN AR Series Notebook crashed frequently (4x day) in Office 2007 and
other apps like Adobe Photoshop. SFC reports errors. I have wasted many
many hours trying to resolve this problem.

Saving a mpeg in quicktime crashed the OS with a blue screen. I spent many
hours on the phone with Microsoft paid 2nd level support. their diagnosis is
that my OS was corrupt. I reinstalled a clean OS (Vista 32 - home premium)
and encountered the exact same problems. I went to best buy and ran several
new laptops (HP, Dell, Sony,.. 64bit & 32bit - some with service pack 1) and
each PC had the exact same error.

After Microsoft closed my case, I reopened it and the frustrated engineer
then told me that HP, Sony, Dell had all corrupted the OS with their
propriatary drivers. Sounds far fetched, but even so, this is a disaster.
MY OEM cannot fix my Laptop and Microsoft has not fixed their Vista OS. I
have a hardware RAID on the MOBO and cannot load XP without the RAID driver.

Microsoft needs to correct the problem and not blame others. With SP1
available and this issue not corrected, I have to wonder what they have been
doing for the last year. How about less bells & whistles and providing an OS
that works correctly.

***
C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 99% complete.Windows Resource Protection found corrupt files
but wa
s unable to fix some of them.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log
***
 
Hello,
Hmm I posted on this several times, don't see my response in this thread
If you are getting that sfc error at 99% and there is nothing in the
cbs.log file, the error is reporting on the removal of some driver files
from a temp folder which would not cause an OS issue, other than this error
being reported. This error should go away with the installation of
Windows Vista SP1.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
|> Thread-Topic: New sfc /scannow Error
|> thread-index: AchjC6RX1fBfA/vTSYurwnt0lym4Uw==
|> X-WBNR-Posting-Host: 207.46.19.168
|> From: =?Utf-8?B?SE1U?= <[email protected]>
|> Subject: New sfc /scannow Error
|> Date: Tue, 29 Jan 2008 22:45:03 -0800
|> Lines: 24
|> Message-ID: <[email protected]>
|> MIME-Version: 1.0
|> Content-Type: text/plain;
|> charset="Utf-8"
|> Content-Transfer-Encoding: 7bit
|> X-Newsreader: Microsoft CDO for Windows 2000
|> Content-Class: urn:content-classes:message
|> Importance: normal
|> Priority: normal
|> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
|> Newsgroups: microsoft.public.windows.vista.performance_maintenance
|> Path: TK2MSFTNGHUB02.phx.gbl
|> Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.performance_maintenance:19031
|> NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
|> X-Tomcat-NG: microsoft.public.windows.vista.performance_maintenance
|>
|> There was a bug reported here in sfc.exe (sfc /scannow at command
prompt)
|> Nov. 27, 2007 at the following Microsoft Discussion Group link:
|>
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=micros
oft.public.windows.vista.performance_maintenance&tid=d0bce3ad-c992-4f2b-8a6f
-5651915fbad5&cat=en_US_9CA88DDB-D18D-FA0E-A366-6E527B0FBA67&lang=en&cr=US&p
=1
|>
|> This bug is not limited to a software conflict with KB941600 as noted in
the
|> link above. I ran sfc.exe after three Vista re-installations: (1) with
no
|> Windows updates, (2) with all Windows updates and (3) with all Windows
|> updates except KB941600. In all three cases, sfc.exe stops at 99% and
|> reports: "Verification 99% complete. Windows Resource Protection found
|> corrupt files but was unable to fix some of them." Examination of the
cbs.log
|> file revealed no files listed as corrupt or missing as described in
KB928228
|> or KB929833. In other reported cases from Google search, sfc.exe stopped
at
|> 99%, 98% and 68% with cbs.log reports of files missing or corrupt that
could
|> not be fixed. In some cases, files were listed as missing or corrupt in
|> cbs.log. In other cases, there were none listed even though they were
|> reported as such in the command prompt summary.
|>
|> This is a very important program in my opinion and one that was able to
|> repair several Windows XP installations in my past experience as a
|> hardware/software tech. Please try and get a fix for this issue ASAP. If
I
|> can help troubleshoot this further, like providing my cbs.log files,
please
|> advise.
|>
|>
 
Back
Top