Results 1 to 10 of 25

Thread: On my XP Pro SP2 PC's, chkdsk c: verified that ZAISS 7.0.377 seems to be causing file corruption.

Hybrid View

  1. #1
    wstern Guest

    Default On my XP Pro SP2 PC's, chkdsk c: verified that ZAISS 7.0.377 seems to be causing file corruption.

    Hi,

    I have 4 home computers, all running XP Pro SP2 with ZAISS 7.0.377.
    I ran the following command on each of my 4 computers: chkdsk c:
    In all 4 cases there were index and bitmap problems that chkdsk reported and fixed.

    I then disabled ZAISS 7 auto load at startup, and rebooted.
    I ran chkdsk c:, no problems. Rebooted again, ran chkdsk c:, no problems.
    Then I turned on ZAISS 7 to load at startup, rebooted, and ran chkdsk c: and sure enough,
    chkdsk reported index and bitmap corruption. This happened on all of my 4 home computers.

    I would appreciate it if anyone else can try this experiment.
    I also have the ZAISS 7 privacy cache cleaner set to run every day, which cleans out the temp folder.
    I wonder if the problem might be that ZAISS 7's cache cleaner is cleaning out the Windows
    temp folder everyday at startup, and this deletion of temporary files during startup might be
    causing the chkdsk index and bitmap errors in the NTFS file system.

    If anyone could run chkdsk c: and report back if they have index or bitmap errors,
    it would be very helpful.

    Thanks

    Bill

    Message Edited by wstern on 04-26-200712:20 AM

    Operating System:Windows XP Pro
    Product Name:ZoneAlarm Internet Security Suite
    Software Version:7.0

  2. #2
    jdoliver Guest

    Default Re: On my XP Pro SP2 PC's, chkdsk c: verifited that ZAISS 7.0.377 has caused file corruption.

    ZoneAlarm Security Suite version:7.0.337.000
    TrueVector version:7.0.337.000
    Driver version:7.0.337.000
    Anti-virus engine version:3
    Anti-virus signature DAT file version:20070425112000
    Anti-spyware engine version:5.0.162.0
    Anti-spyware signature DAT file version:01.200704.1455
    AntiSpam version:4.9.1.8211
    I just ran chkdsk on c: and found no errors.
    I have the windows swap file on e: but haven't run chkdsk on that.

  3. #3
    Join Date
    Nov 2004
    Location
    localhost
    Posts
    17,286

    Default Re: On my XP Pro SP2 PC's, chkdsk c: verifited that ZAISS 7.0.377 has caused file corruption.

    Hi!No chkdsk disk errors here too... not sure what is your problem...Are you running any disk defrag tools? It may be that one.Fax

    Click here for ZA Support
    Monday-Saturday 6am to 10pm Central time
    Closed Sundays and Holidays

  4. #4
    wstern Guest

    Default Re: On my XP Pro SP2 PC's, chkdsk c: verifited that ZAISS 7.0.377 has caused file corruption.

    Hi,

    I have carefully run unit tests with ZAISS 7 turned on and off under very controlled conditions on each
    of my 4 computers (They are all running Windows XP Pro SP2). ZAISS7 is definitely causing my issue.
    These chkdsk errors mean the integrity of the NTFS file system is being corrupted.

    I love ZAISS 7, as its many features and its combination with Kaspersky give me the ultimate security,
    but I am concerned about these chkdsk errors. I don't want it to corrupt the operating system or any valuable files I have.

    If you are not getting these chkdsk errors, maybe its something with the way I'm customizing ZAISS 7.
    Under privacy settings, I turned on the Cache cleaner, and enabled the cleaning out of the Windows temp folder every day.
    Maybe this could be deleting files from the temp directory during Windows startup,
    while other things are trying to load, and this could be causing NTFS index and bitmat issues.

    I did a search on this support list, and I saw other people raising this same issue (about 2 weeks ago),
    so I'm not the only one with this problem.

    I would encourage anyone who reads this post to do the following and respond back if you have chkdsk errors:

    Start, run, cmd (Open up command prompt).
    chkdsk c:

    It will take about 10 minutes to run. If you see index or bitmat error messages, then you may have the same issue I have.
    If you could respond back with your results, I would greatly appreciate it.

    Bill

  5. #5
    Join Date
    Nov 2004
    Location
    localhost
    Posts
    17,286

    Default Re: On my XP Pro SP2 PC's, chkdsk c: verifited that ZAISS 7.0.377 has caused file corruption.

    Hi!checked, no errors... I have see this chksdk issue popping up on the Kaspersky from time to time but at the end no real facts are tabled to attribute this issue toKAV...Fax

    Click here for ZA Support
    Monday-Saturday 6am to 10pm Central time
    Closed Sundays and Holidays

  6. #6
    wstern Guest

    Default Re: On my XP Pro SP2 PC's, chkdsk c: verifited that ZAISS 7.0.377 has caused file corruption.

    Hi Fax,

    Thank you for your reply.

    I would like to compare my ZA settings to your settings.

    Are you using ZAISS7 or ZAPro7?
    Have you turned on the Zone Alarm Anti-virus (Kaspersky engine) and Zone Alarm Anti-Spyware?
    Have you turned on the Privacy cache cleaner to clean out your Windows Temp folder - If so, did you set it to do it daily?
    Have you turned on Program Control to high setting, with top 2 out of 3 program control choices checked on next screen?

    Any other details you could provide about your customizations would be helpful.
    What I could do is to configure my ZAISS7 the same as yours, and see if the chkdsk NTFS corruption error messages go away.

    Thanks,

    Bill

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •