Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customise your settings, hit “Customise Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

Rogue CA update bricks Win XP systems

Sky not really falling


A rogue security definition update to anti-virus software from CA hobbled Windows systems earlier this week, sparking howls of protests from users.

The update, issued on Wednesday, falsely labeled important Windows system files as potentially malign, dispatching them into quarantine. The action prevents Windows XP systems from booting properly.

A discussion thread on CA's support forum reflects widespread frustration over the problem, echoed in email tips from Reg readers.

"My phones are ringing off the hook as CA Antivirus is quarantining genuine windows files left, right and centre," writes one of our correspondents. "Anyone else ripping their hair out?"

In a statement (below), CA said it issued a revised update on Thursday that resolved the problem.

On July 8, 2009 at 11:00am EST, a CA DAT file release contained improperly formed malware detections that errantly detected clean files from Microsoft Windows Service Pack 3 and from the commercial Cygwin application. Affected files were detected as "Win32\Amalum" variants with extensions such as ZZNRA, ZZOFK, ZZNPB, and ZZNRA.

All files falsely detected as malware by these errant signatures were quarantined and renamed with the following text added to the file name "*.AVB". This prevented the affected files from running as the ".exe" file. It's important to note that the affected files remain fully intact, only the file extensions were modified.

On July 9, 2009 at 3:30am EST the file was corrected and released.

False positives involving anti-virus scanners are an industry-wide problem. Users are worst affected when, as in the current case with CA, core system files (rather than simply the components of regular applications) are labeled as potentially malign. Solving the problem involves rolling back to previous definition or issuing new updates that avoid Chicken Little-style false alarms. ®

Similar topics


Other stories you might like

Biting the hand that feeds IT © 1998–2021