Problems with C:\System Volume Information\tracking.log

Follow-up Post:
After reinstalling Windows, I had no further problem until the end of
December (2007) when the same thing happened, for no known reason. This time,
I simply did a clean re-install, since I haven't found any other
posts/solutions from people who've had this problem.

"Xiaomai" wrote:

> Followed instructions & the Repair Install itself went fine. That was the
> good part.
>
> Unfortunately, the system encountered an error attempting to install the 82
> most essential windows update. (The error message appeared as soon as XP
> tried to install the first of 82, and all 82 failed simultaneously.)
>
> STILL no new entries in the Event Viewer logs. You'd think a Repair Install
> would get noted, right? Not this time.
>
> The failed updates was the last straw for me. I did a clean install and am
> currently re-installing my software. At this point, that's probably the most
> time-efficient option, and everything I have is backed up anyway.
>
> Will monitor the Event Viewer and the tracking.log file. My main
> disappointment at this point is that the cause of the problem was never
> definitevely identified. But given that my my old laptop had no problems and
> the only difference in software installed was:
>
> A. I installed more Windows Powertoys (I doubt these would be the problem) and
> B. the Super (c) audio program, and the last event logged was about the same
> time I installed it,
>
> I think it's quite reasonable to believe that the Super (c) was the cause of
> it. And if it does turn out to be Zone Alarm, this saga will continue on
> their message board.
>
> Thanks for your help!
>

What is "this problem"?

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Xiaomai wrote:
> Follow-up Post:
> After reinstalling Windows, I had no further problem until the end of
> December (2007) when the same thing happened, for no known reason.
> This time, I simply did a clean re-install, since I haven't found any
> other posts/solutions from people who've had this problem.
>
> "Xiaomai" wrote:
>
>> Followed instructions & the Repair Install itself went fine. That
>> was the good part.
>>
>> Unfortunately, the system encountered an error attempting to install
>> the 82 most essential windows update. (The error message appeared as
>> soon as XP tried to install the first of 82, and all 82 failed
>> simultaneously.)
>>
>> STILL no new entries in the Event Viewer logs. You'd think a Repair
>> Install would get noted, right? Not this time.
>>
>> The failed updates was the last straw for me. I did a clean install
>> and am currently re-installing my software. At this point, that's
>> probably the most time-efficient option, and everything I have is
>> backed up anyway.
>>
>> Will monitor the Event Viewer and the tracking.log file. My main
>> disappointment at this point is that the cause of the problem was
>> never definitevely identified. But given that my my old laptop had
>> no problems and the only difference in software installed was:
>>
>> A. I installed more Windows Powertoys (I doubt these would be the
>> problem) and B. the Super (c) audio program, and the last event
>> logged was about the same time I installed it,
>>
>> I think it's quite reasonable to believe that the Super (c) was the
>> cause of it. And if it does turn out to be Zone Alarm, this saga
>> will continue on their message board.
>>
>> Thanks for your help!

The problem was the C:\System Volume Information\tracking.log file. The whole
issue began because any attempt to access the file (such as anti-virus
software doing a routine scan) would hang up. Even trying to access the
Properties tab for this file would cause a hung app - in fact, I can't
remember that far back, but I might have had to do a force power off when the
system hung up that way. All this for a file only 20kb.

Attempts to diagnose the cause of the problem failed, so not surprisingly, I
wasn't able to fix it short of erasing the hard drive and doing a clean
re-install. At the time, Bert and I suspected a freeware program called Super
(c) was the culprit.

This problem happened again on Dec 28 but there was culprit I could suspect
- that time I found it easier just to do the clean re-install and be done
with it within 24 hours.

I have now found the past history of your problem as recorded in Google:
http://groups.google.com/group/micro... 2098a431c0fc

I see we also corresponded just before the new year on a problem with a
defragmenter. Did the solution suggested work?

Your problem is with Zone Alarm. The solution for you is described here:
http://forums.zonealarm.com/zonelabs...ssage.id=24929

However, there may be some doubt as to whether it resolves the problem.

When does your Zone Alarm subscription expire?


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Xiaomai wrote:
> The problem was the C:\System Volume Information\tracking.log file.
> The whole issue began because any attempt to access the file (such as
> anti-virus software doing a routine scan) would hang up. Even trying
> to access the Properties tab for this file would cause a hung app -
> in fact, I can't remember that far back, but I might have had to do a
> force power off when the system hung up that way. All this for a
> file only 20kb.
>
> Attempts to diagnose the cause of the problem failed, so not
> surprisingly, I wasn't able to fix it short of erasing the hard drive
> and doing a clean re-install. At the time, Bert and I suspected a
> freeware program called Super (c) was the culprit.
>
> This problem happened again on Dec 28 but there was culprit I could
> suspect - that time I found it easier just to do the clean re-install
> and be done with it within 24 hours.

I wish I'd seen your reply back in January! (It's May now, and I just renewed
my ZA license last month), and I just got the same problem today (May '08).
Any application that tried to access tracking.log. The system locked up when
I tried viewing File Properties or opening it.

Nonetheless, the link to ZA Forum that you posted enabled me to solve the
problem, thanks! It appears to be a minor issue that I can easily live with.

The actual post with the solution that I used is here:
http://forums.zonealarm.com/zonelabs...ssage.id=27909
(I have both Zone Alarm Internet Security Suite and Spyware Doctor 5.5.0~
installed.)

The solution is simple: I restarted my computer in Safe Mode. From there, I
could view File Properties for tracking.log and open the file. I deleted the
file and restarted normally. (XP automatically creates this file during
startup.) When I tried accessing the file just now, I was able to open it and
view the File Properties tab with no problem. Sure beats having to reinstall
XP and all my files from scratch for the 3rd time in 8 months!

Hopefully, this whole issue is now resolved and other people can benefit
from my experience. If that is NOT the case, I'll update this post.