Other Norton Products

[Nate_C]

If you are using IE, could you try downloading with another browser to see if the full file comes down?

[Nerimash Spyware Scolder]

Today I've noticed that NPE-beta got updated to 2.5.36(26 was previous build). 

There are any changes in this beta build? 

[Nate_C]

These are the changes in the new build. I will be announcing these changes on the forum as well.

Key changes in this release: 

• Norton Live Banner

At the bottom of the Main UI  there is a banner with a link to a Norton Live page that reads-

“Need help with a virus or spyware? A live expert can remotely remove it for you. Learn more about this paid service”

• Rootkit Scan enabled by default

The Rootkit scan will run by default. There is an option in settings to disable this.

• Improved usability scan results screen

‘Unknown’ files now have an info dialog pop-up to provide more information about the detection.

In order to remove an ‘Unknown’ file users will first need to click the ‘enable action on the file’ button found on the info pop-up dialog .

The Cloud Scan flow has been changed to a cloud shaped button.

[NUser Symantec Employee]

Thanks rcsptdisi,

The error was due to the corrupted NPE.exe;

As Nate has suggested, Can you please try downloading on a different browser?

If it fails, can you please use the Norton Bootable Recovery Tool by visiting the following page http://security.symantec.com/nbrt/nbrt.aspx?

Regards!

[confusedxvii]

I just recently used power eraser and it came up with physicaldrive0. So I continued to fix and now I cannot boot. I've tried several times to recover from multiple different recovery points to no success. There is NOTHING in support about power eraser and I've found nothing else anywhere

[Quads]

Sounds like Norton Power Eraser (NPE) has detected the Boot Record (MBR) and has either deleted it or incorrectly disinfected the MBR, when this happens you on booting the PC will usually get a black screen with a white flashing underscore.

Depending on the Windows you have of course for which command to use, but use the recovery disc or installation disc etc, then use the command prompt to fix the MBR

Quads

[confusedxvii]

It gets to the loading screen then takes me to startup repair. I'm running windows 7 and tried restoring to the point set by norton just before I tried to fix it and even earlier ones but no luck.

[Quads]

Your Startup Repair is kicking in first,

For Vista / Windows 7 you have to use the bootrec tool in command prompt to fix the MBR

bootrec /[command]

examples,  

bootrec /RebuildBcd

bootrec /Fixmbr

bootrec /Fixboot

bootrec /ScanOs

Quads

[JorgeA]

Hi,

I'm getting contradictory results from different aspects of NPE Beta.

When I run a scan, two "bad" results come back, as in the screenshot below:

When I click on the cloud scan, both of them still come back as "bad." Clicking on the info button, I get something like this:

However, if I click on the individual files on the left, I get the following screens, in which the files are considered "favorable" despite the "bad" rating they just received:

Obviously both of these ratings can't be correct -- a file can't be both "bad' and "favorable." Which assessment should I trust?

More generally, this kind of discrepancy is perhaps an area where NPE can be improved while still in beta.

Also, an inline explanation of the reason why the file in question is considered unsafe, would be welcome.

--JorgeA

[Nate_C]

Jorge,

Thank you for the valuable feedback.

While the reputation of the file is one factor used in determining if the file is a threat , Norton Power Eraser uses a combination of heuristic techniques to identify potential threats.

To combat new and evolving threats, Norton Power Eraser is specifically engineered to be more aggressive when detecting threats. The threshold for which a file is considered 'Favorable' , does not provide enough certainty for NPE to consider the file safe.

We present the individual file reputation data so that users can review this when deciding how to address the file.

We recognize that for ‘Favorable’ files this is confusing and are looking at ways we can refine the flow in an update.