It's a spurious error reported by Norton. Symantec hasn't fixed it although
they've known about it for years. Heck, there's even a KB article about it
now:
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.