Understanding VCPREF Issues
Troubles Opening VCPREF Files
Norton Security Isn't There
You encounter an error message such as "%%os%% Can't Open VCPREF Files" when trying to open your VCPREF. Customarily, this means that Norton Security is not installed on %%os%%. You won't be able to double-click to open your VCPREF because your OS doesn't know what to do with it.
Tip: When another VCPREF application is installed, you can choose to open it by selecting "Show Apps" and using that program.
Norton Security is Out-of-Date
Your Norton Antivirus Preferences File file is incompatible with Norton Security because you might have the wrong version installed. You will need to download a newer version of Norton Security if you don't have the right version. This problem is most common when you have an older version of the software application, and your file was created by a newer version that it cannot recognize.
Tip: Right-clicking on your VCPREF, then clicking "Properties" (Windows) or "Get Info" (Mac), can provide clues about your file version.
Ultimately, most of the difficulties opening VCPREF files are due to having the wrong version of Norton Security installed.
Other Causes of VCPREF File Opening Problems
Errors opening Norton Antivirus Preferences File files can still occur even with the latest Norton Security software installed on your computer. There can be external issues inside of %%os%% that are causing these errors when opening VCPREFs. Other contributing causes:
- Windows Registry VCPREF file paths that are incorrect
- Accidental deletion of the description of the VCPREF file in the Windows registry
- Norton Security or another VCPREF application experienced a flawed installation
- Your VCPREF can't be loaded properly (file corruption)
- The VCPREF is infected with a virus
- VCPREF-related hardware has device drivers that obsolete
- Your PC doesn’t have enough available resources to open the Norton Antivirus Preferences File file
Quiz: How many characters long can a filename be?
That's Correct!
The sum of the individual components of a filename (eg. subdirectory / path and the final filename) are limited to 255 characters in total.
Close, but not quite...
The sum of the individual components of a filename (eg. subdirectory / path and the final filename) are limited to 255 characters in total.