Please Sign In with Norton Account to Ask a Question or comment in the Community
Product Announcement: Norton Security 22.23.4.6 for Windows is now available!
Posted: 28-Aug-2014 | 6:39AM · 15 Replies · Permalink
I do got those "unknown installation repairs" in the past but not everytime I ran "get support".
Posted: 28-Aug-2014 | 9:38PM · Permalink
Hi. Currently when you run Autofix, it won't tell you specifically what has been repaired.
If there is an ongoing problem with the Norton installation, we'd normally recommend the Norton Remove and Reinstall Tool, which will give you a clean copy.
Links can be provided, if needed.
Posted: 28-Aug-2014 | 10:33PM · Permalink
Same issue with me. You can run the get support multiple times in succession and keep getting notified that an install repair has been done.
Posted: 29-Aug-2014 | 3:16AM · Permalink
I'm seeing the same thing. It's most likely related to the recent changes with Norton Vulnerability Protection (or some other Norton changes made at the same time). The same time that NVP was removed from Firefox and disabled in IE was when I saw the 'get support' loop begin.
Posted: 29-Aug-2014 | 3:51AM · Permalink
Yeah every since this last update. It keeps doing the same thing to me as well.
Posted: 29-Aug-2014 | 9:00AM · Permalink
Hi,
I tried to reproduce this issue, but 5 times out of 5, even in different times and conditions, Support ends with no errors found.
Like you, I'm with NIS 21.5 and have already got the patch.
Sandro
Posted: 29-Aug-2014 | 9:12AM · Permalink
" I do got those "unknown installation repairs" in the past but not everytime I ran "get support"."
You can safely ignore these warnings, as long as an error code is not showing, it's nothing.
Regards,
Posted: 29-Aug-2014 | 12:40PM · Permalink
5 people wrote:
> You can run the get support multiple times in succession and keep getting notified that an install repair has been done.
[or siimilar]
Make me number 6.
apostolos:
> You can safely ignore these warnings,
> as long as an error code is not showing, it's nothing.
That's not exactly correct. It's not _nothing_.
No well written program should ever return an error message unless something is actually wrong. Particularly one which is used to protect millions of computers from malware.
If you are trying to say that the message itself is wrong -- that there is in fact nothing wrong -- then:.
It's wrong for NIS to generate the error message.
Because, obviously, NIS users, whether they're begginers or experienced, will wonder if there's something wrong with the program that is protecting their computer from malware.
NIS GUI --> Advanced --> Recent history shows:
Norton autofix results
Issues found 1
Issues fixed 1
NIS explicitly says that an issue was found (and fixed).
NIS didn't just spontaneously decide to create a random message.
It did it in response to something.
If the something was real, the history log should say just what was wrong. Even if it's some vague Norton error message ("error 84097"). That would allow users to report it and Norton to get a handle on how often it's occurring and why.
If the something was false (as you imply), it shouldn't have happened at all, and NIS should be fixed so that it stops generating false messages.
win 7 + SP1
nis 21.5.0.19
Posted: 29-Aug-2014 | 12:45PM · Permalink
"
> You can safely ignore these warnings,
> as long as an error code is not showing, it's nothing.
That's not exactly correct. It's not _nothing_."
I've seen this on different occasions, but pretty much rarely since version 19, it has not been fixed, if it was that important I believe it would have been fixed by now.
What makes you think that it will be fixed?? (maybe with NS & NSB??)
I stopped running Get Support a long time ago, Norton is working ok and I tend to believe that the more one user runs Get Support, the more there are chances to corrupt the installation...
I ignore it and never encountered an issue.
If something was wrong in the way Norton interacts with Windows, there would be logs in Event Viewer, and speaking for me, there are zero errors or warnings.
Just my opinion.
Posted: 29-Aug-2014 | 1:40PM · Permalink
This is due to the recent change in the NVP add on for Firefox in an Intrusion Protection update that was just released.
The old method of injecting into the Firefox browser was using an "add-on". The update that went out this week removed that add-on and we inject directly into IE or Firefox. This makes it easier to support new Firefox and IE versions going forward and provides better protection that the old method of injecting.
What is being repaired and why it doesn't seem to stay repaired:
- Upon installation of NIS 21 we register the NVP Firefox add-on in the firefox registry.
- Now the update for Intrusion Prevention removes the entry in the Firefox registry (because the add-on is no longer needed or used)
- When you click "get support" NIS 21 scans the original install code vs what is currently on the system. Since the registry key for the Firefox add-on is now gone, it re-creates it and you see "installation success".
- Then almost immediately, our Intrusion Prevention component removes the registry key (as it is not needed)
- If you click "get support" again, it re-creates the key again, and so on...
Posted: 29-Aug-2014 | 1:58PM · Permalink
Hi Miket,
Good explanation, one more reason, as I stated earlier, not to run frequently Get Support, as it creates/deletes a registry key each time.
However, it will be fixed in a future patch.
Thank you for your very detailed post/explanation.
One question, since IPS defs are directly injected into the browser, does it mean that we can safely use IE 11 64-bit browser? (EPM enabled).
Regards,
Posted: 29-Aug-2014 | 2:24PM · Permalink
We do not inject into 64bit Internet Explorer, support is still 32bit only for Browser Protection.
But we do support EPM (with 32bit IE).
Posted: 29-Aug-2014 | 4:25PM · Permalink
Hello miket,
Do you have any idea if NS & NSB aka v.22 will support 64-bit browsers?? (IE etc).
Thank you.
Kind regards,
There are currently 0 users online.
Re: Everytime I run "get support" in my NIS 21.5 I get an "installation repair" since today.
Posted: 29-Aug-2014 | 1:40PM · Permalink
This is due to the recent change in the NVP add on for Firefox in an Intrusion Protection update that was just released.
The old method of injecting into the Firefox browser was using an "add-on". The update that went out this week removed that add-on and we inject directly into IE or Firefox. This makes it easier to support new Firefox and IE versions going forward and provides better protection that the old method of injecting.
What is being repaired and why it doesn't seem to stay repaired:
- Upon installation of NIS 21 we register the NVP Firefox add-on in the firefox registry.
- Now the update for Intrusion Prevention removes the entry in the Firefox registry (because the add-on is no longer needed or used)
- When you click "get support" NIS 21 scans the original install code vs what is currently on the system. Since the registry key for the Firefox add-on is now gone, it re-creates it and you see "installation success".
- Then almost immediately, our Intrusion Prevention component removes the registry key (as it is not needed)
- If you click "get support" again, it re-creates the key again, and so on...