title
Products            Buy            Support Forum            Professional            About            Codec Central
 

Norton rejecting r14.3 download as unsafe! Malware aboard?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • wondermouse

    • Sep 2009
    • 39

    Norton rejecting r14.3 download as unsafe! Malware aboard?

    Just tried to download my registered copy of dBpoweramp Reference R14.3 (Family Pack Upgrade) only for Norton (up to date 360) to delete it saying it's infected with WS.Reputation.1

    Is this correct? If so could it please be replaced by a clean copy?

    Thanks

    Mark
  • bhoar
    dBpoweramp Guru

    • Sep 2006
    • 1173

    #2
    Re: Norton rejecting r14.3 download as unsafe! Malware aboard?

    Mark: this is a special case flag with Norton, the WS.Reputation.1 notification isn't technically a malware notification, but rather an alarm that the software does not recognize Illustrate's installer.

    See here for more information: http://community.norton.com/t5/Norto...on/td-p/232155

    Brendan

    Comment

    • wondermouse

      • Sep 2009
      • 39

      #3
      Re: Norton rejecting r14.3 download as unsafe! Malware aboard?

      Originally posted by bhoar
      Mark: this is a special case flag with Norton, the WS.Reputation.1 notification isn't technically a malware notification, but rather an alarm that the software does not recognize Illustrate's installer.

      Brendan
      Ive never had a problem before, and I didn't have any problem installing the Beta version, but I can't see how to make Norton allow me to run 14.3 before it deletes it!

      I believe that you can contact Norton to ensure they don't throw up fake positives, but in the meantime, is there a workaround?

      Mark
      Last edited by wondermouse; January 25, 2013, 05:03 PM. Reason: Correct typo

      Comment

      • bhoar
        dBpoweramp Guru

        • Sep 2006
        • 1173

        #4
        Re: Norton rejecting r14.3 download as unsafe! Malware aboard?

        The workaround is linked from the link I posted.

        Brendan

        Comment

        Working...

        ]]>