I ran the system file checker from an Admin command prompt and all showed well except for a reported "violation" in the %windir%/Logs/CBS/CBS.log file. This is a TEXT file! Why would SFC find it as a violation? My Vista system works great except for the seemingly common 0x80240029 error code with updating Defender definition files. (there "may" be a connection...?) This problem is not unique to me others have asked the same question. Is this cbs.log file anything to lose sleep over? Thanks.

Hello, Where are you seeing the violation message? Can you capture the exact text of the message? It may be because there are multiple things attempting to write to the cbs.log file at the same time. SFC logs all it's entrys to the CBS.log file, as does CBS and CSI Have you gone through the steps in this article already? 934562 Error message when you try to update Windows Defender on a Windows Vista-based computer: "Error found: Code 0x80240029" support.microsoft.com/default.aspx?scid=kb;EN-US;934562
Thanks, Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights |>Thread-Topic: "SFC /verifyonly" violation in cbs.log file?? |>thread-index: AceITfYpJ2d0TFoUTCSR0H/1O96YQw== |>X-WBNR-Posting-Host: 74.60.225.140 |>From: =?Utf-8?B?RVc=?= |>Subject: "SFC /verifyonly" violation in cbs.log file?? |>Date: Thu, 26 Apr 2007 14:58:02 -0700 |>Lines: 7 |>Message-ID: |>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.2826 |>Newsgroups: microsoft.public.windows.vista.performance_maintenance |>Path: TK2MSFTNGHUB02.phx.gbl |>Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.vista.performance_maintenance:5506 |>NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148 |>X-Tomcat-NG: microsoft.public.windows.vista.performance_maintenance |> |>I ran the system file checker from an Admin command prompt and all showed |>well except for a reported "violation" in the %windir%/Logs/CBS/CBS.log file. |> This is a TEXT file! Why would SFC find it as a violation? My Vista system |>works great except for the seemingly common 0x80240029 error code with |>updating Defender definition files. (there "may" be a connection...?) |>This problem is not unique to me others have asked the same question. |>Is this cbs.log file anything to lose sleep over? Thanks. |>

Darrell, The violation message is within the Command Prompt window (black screen) and shown below my "sfc /verify only" command after sfc runs for about 7 minutes. It simply reads something like :....violation in CBS.log file.......... Nothing more explanatory. It may have nothing to do with the Defender error code (which you mentioned and which I did "fix" according to the kb article).
As I said, others have had this violation code too but there have been no followups. Perhaps it's just nothing to worry about. My Dell Vista runs like a charm and I may be looking at insignificant items. I reckon I just won't run SFC any more and just press on!
However, if you have any ideas....... Bottom line: I don't understand yet how a .log file can have a violation (or be corrupted!).

""Darrell Gorter[MSFT]"" wrote: