Norton AntiVirus (2014)

Early computer viruses under MS-DOS were simple things, chunks of code appended to executable COM files. Norton Antivirus was there, starting in 1990, working to wipe out these nasty infections. Norton AntiVirus (2014) continues to do the job, growing and evolving to face ever more complex types of malicious code.

Like Bitdefender, Kaspersky, and a few others, Symantec has stopped using a year or version number for its Norton product line. I've appended "(2014)" for the simple purpose of distinguishing this product from earlier versions.

View all Photos in Gallery

Big, touch-friendly buttons on the main window let you quickly launch a scan or check for updates. An info panel monitors CPU usage (overall and specifically by Norton). The product comes configured for the best balance between security and performance, so most users won't need to dig into the product's settings.

A New Technique
When I met with Symantec representatives prior to this review, they explained a truly impressive new feature that's been added to the current version. Sometimes malware infests essential Windows components, in effect taking them hostage. The antivirus can't quarantine the infected file without disabling Windows. The best solution would be to replace the file with a clean copy of the original, but licensing issues prevent doing so directly.

To clean up this kind of problem, the product first consults the immense Norton Insight database to locate the corresponding clean file, then runs a cloud-based comparison against the infected edition. It supplies the local Norton installation with a file that represents the difference between the two—in effect, a set of instructions for changing the corrupted file back to its clean equivalent. Once the clean file has been verified, the cleanup is complete.

I frequently run into big problems with antivirus products that get too aggressive and delete important Windows files. I'm really impressed with the cleverness of this technology.

Installation Ups and Downs
The installer for Norton AntiVirus checks for problems and, when possible, solves them. For example, on one test system it detected an illegitimate proxy installation and offered to remove it. Doing so saved it from a host of post-install connection troubles.

When malware has rendered a system unbootable, or when ransomware actively blocks access to the system, the Norton Bootable Recovery Tool offers two ways to save the day. You can run Norton Power Eraser, an aggressive malware-killing tool, or run an advanced recovery scan. This tool easily wiped out ransomware on one test system, allowing installation of the full product.

On the flip side, the new cleanup technology I described didn't prevent Norton from damaging two test systems to the point they would not boot. On one system, Norton's Auto-Protect flagged a number of files immediately after installation and requested a reboot to finish cleanup. After reboot, it went into an endless logon/logoff loop. The other system couldn't update, activate, or call on its built-in support. On advice from tech support I tried Norton Power Eraser, and when that didn't help, Norton Bootable Recovery Tool. This system ended up in the same kind of logon/logoff loop.

Getting these problems fixed required several hours of interaction with tech support, including remote-access diagnostics and repair, which was rather disappointing. Both systems did eventually get fixed, but it took a lot of work. I rate the installation experience at two stars.

About Our Expert

Neil J. Rubenking

Principal Writer, Security

My Experience

When the IBM PC was new, I served as the president of the San Francisco PC User Group for three years. That’s how I met PCMag’s editorial team, who brought me on board in 1986. In the years since that fateful meeting, I’ve become PCMag’s expert on security, privacy, and identity protection, putting antivirus tools, security suites, and all kinds of security software through their paces.

Before my current security gig, I supplied PCMag readers with tips and solutions on using popular applications, operating systems, and programming languages in my "User to User" and "Ask Neil" columns, which began in 1990 and ran for almost 20 years. Along the way, I wrote more than 40 utility articles, as well as Delphi Programming for Dummies and six other books covering DOS, Windows, and programming. I also reviewed thousands of products of all kinds, ranging from early Sierra Online adventure games to AOL’s precursor Q-Link.

In the early 2000s, I turned my focus to security and the growing antivirus industry. After years of working with antivirus, I’m known throughout the security industry as an expert on evaluating antivirus tools. I serve as an advisory board member for the Anti-Malware Testing Standards Organization (AMTSO), an international nonprofit group dedicated to coordinating and improving testing of anti-malware solutions.

The Technology I Use

Much of the testing I do, particularly testing with real-world ransomware, is just plain dangerous. To perform such tests safely, I sequester them inside virtual machines managed by VMWare Workstation. For cross-platform testing, I use a MacBook Air, a Google Pixel 4, and a 6th-generation iPad.

I rely on my Delphi coding skills to create and maintain small applications. These include programs to check whether an antivirus correctly handled the malware it detected, launch dangerous URLs and record the security program’s reaction, and analyze the malware that I collect for use in testing. I also wrote a tiny browser and text editor for use in testing security apps that have predefined reactions for known products.

I do my writing and research on a Dell OptiPlex desktop, relying on Microsoft Word (my fingers know all the shortcuts). Many of my articles include charts and analysis; Excel is my go-to for those. When work hours end, though, I escape the bounds of Microsoft and Windows. There’s an iPhone in my pocket, I relax with my oversized iPad, and my Kindle Oasis is always loaded with the best science fiction and fantasy.

Read the latest from Neil J. Rubenking

Read full bio