I’m compelled to present my experience.
15 Mar 19 I inadvertently clicked the update balloon for my CIS v5.12.256249.2599 on my Win2003 R2 system. Obviously my system became useless after that point; CIS being hopelessly corrupted. No recourse was available other than restoration of %SystemDrive% image dated 15 Jan 19. :-[
After dealing with the obvious ramifications / repercussions of non-sector, i.e., MFT, based partition image-restore , and necessity for HDD NTFS metafile / layout optimization / free-space consolidation, et ali, CIS update to A/V defs with a bulk download occured successfully and uneventfully. A/V updates were attempted subsequently 15 Mar 30 that failed w/ out recourse; the CIS inherent Dx Util stated: NPF.
The then current A/V def file was downloaded from Comodo Anti Malware Database Latest Version & Additions 2022. In Safe Mode I archived - with NTFS security - the currently working A/V def file and copied the downloaded aforementioned A/V defs file, rebooted and subsequently CIS A/V update failed.
Subsequently the CIS /repair A/V def file was archived - in Safe Mode - and the aforementioned A/V defs file was implemented to CIS /repair, and /scanners was deleted. Upon reboot CIS A/V update failed.
I’ve found that CIS Quarantine folder has been a sore point WRT defragging, i.e., the folder, subfolder and files contained therein are ‘locked’ and inherently fragmented will cause prollems with the HDD layout / defrag. It should be known that in all of my previous attempts, the CIS Quarantine folder was ‘poofed’ every single time.
O.k.
If you’re following: where’s the stinkin’ prollem?
It has to be on the drive, eh?
So I chkdsk %sysDrive% /x’d it and the Event Log said this about that:
Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 3/30/2015
Time: 2:20:30 PM
User: N/A
Computer: Colossus
Description:
Checking file system on %SysDrive%:
The type of the file system is NTFS.
Volume label is HAL9000
A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
CHKDSK is recovering lost files.
Cleaning up 103 unused index entries from index $SII of file 0x9.
Cleaning up 103 unused index entries from index $SDH of file 0x9.
Cleaning up 103 unused security descriptors.
CHKDSK is verifying Usn Journal…
Usn Journal verification completed.
Correcting errors in the master file table’s (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
12289693 KB total disk space.
11165296 KB in 43416 files.
17240 KB in 7358 indexes.
0 KB in bad sectors.
134845 KB in use by the system.
63504 KB occupied by the log file.
972312 KB available on disk.
4096 bytes in each allocation unit.
3072423 total allocation units on disk.
243078 allocation units available on disk.
Attempt to update CIS A/V again with failure as result. I must go to CIS forum; I be stupid. :-[
I read and read. I read many many very mad people. I read thread post more and more people mad and threaten to go away and not bother people like me reading any more. I’m very happy; they’re going away.
I think and realize that I’m not any happier because they went away; I still have this problem.
So now I read more.
I read this:
bases.$$$
Oh, what’s that? I see that I have bases.$$$ with 36MB. Huh. Really.
So I make bases.$$$ go away to a very bad place - tormented by myself perpetually -and leave the existing A/V defs I downloaded in both /scanners & /repair, and I ■■■■ away Quarantine and then reboot out of Safe Mode and CIS A/V defs update w/ out a single hitch.
I waited until now to post; I wanted to see how re-update works. It works; AFTER the BSOD err=77 that occurred during the A/V def update process. That notwithstanding, after dealing with the frag’d Swap File that’s always consequent to ERR=77 BSOD, CIS A/V updeated flawlessly.
I believe there’s a little dragon lookin’ for its Mommy in the CIS A/V def files.
:o
:-\