• All Community
    • All Community
    • Forums
    • Ideas
    • Blogs
Advanced

Not what you are looking for? Ask the experts!

Kudos0

Issues since recently updating 360

Hi everyone...hopefully somone can provide some insight.  First....Since I updated, the Norton icon in the bottom right tray takes close to a minute for it to show up.  Prior to the update,version 6 showed immidiatley.  I have already made sure that Boot Time Protection is on. 

My second issue pertains to registry issues that cannot be corrected.  There are three persistant Norton registry entries that I cannot get rid of.  CCleaner will clean them, but they just reappear after a reboot.  Here are the entries:

Unused File Extension Symantec.Norton.SystemStatus HKCR\Symantec.Norton.SystemStatus

Unused File Extension Symantec.Norton.SystemStatus.1 HKCR\Symantec.Norton.SystemStatus.1

ActiveX/COM Issue InProcServer32\C:\Program Files (x86)\Norton 360\Engine64\20.1.1.2\McStatus.dll HKCR\CLSID\{09D32393-10DA-4eca-91AA-AD11C69DB966}

What is causing this?  Thank you in advance for any help.

Phil

Replies

Kudos0

Re: Issues since recently updating 360

Yes the Norton Icon can take time to show.

You must be using some registry checker I guess. I dont advise this for the inexperienced.

The two registry settings are perfectly normal and you should leave them alone.

They reappear because they are generated by the product. Your cleaner may consider them unused because they have no entry against them but that does not mean they are not required or not to be used in some circumstance. If you are cleaning registry to this extent you are bound to get problems now or in the future.

Kudos0

Re: Issues since recently updating 360

Hi cgoldman,

Thank you for the response. It Is good to know that those are not issue entries. You said that the first two are not an issue, but what about the activex issue regarding the mcstatus.dll?? In fact I went to that location and that file isn't even there.

Phil
Kudos0

Re: Issues since recently updating 360

I had this issue too. What I did was disable Norton Product Tamper Protection. Run CCleaner and fix the registry. Then re-enable Norton Product Tamper Protection.

Hasn't happened again.

Windows 10 Pro 64-bit / Norton Security v.22.19.x
Kudos0

Re: Issues since recently updating 360

Apparently CCleaner issue was meant to be fixed with new release 20.2.0.19.  BUT.....

Not in my case, I now get 4 exceptions for Norton CCleaner can't clean, instead of 2 !!

Unused File Extension NortonAntiVirus.MediaStatusSink HKCR\NortonAntiVirus.MediaStatusSink
Unused File Extension NortonAntiVirus.MediaStatusSink.1 HKCR\NortonAntiVirus.MediaStatusSink.1
Unused File Extension Symantec.Norton.SystemStatus HKCR\Symantec.Norton.SystemStatus
Unused File Extension Symantec.Norton.SystemStatus.1 HKCR\Symantec.Norton.SystemStatus.1

NIS 2013

XP Pro SP3

Kudos0

Re: Issues since recently updating 360

I can tell you what happened here (to a degree)

if you look in your N360 history after you tried a registry clean, you will notice an entry stating that the attempted 'clean' of the N360 registry entries by CCleaner was blocked as an Open Process Token.

Norton say its fixed in the latest patch, so that should be the end of it.

Keep posting if it continues

Kudos0

Re: Issues since recently updating 360

As cgoldman notes "I dont advise this for the inexperienced."

If you are using a registry cleaner, be sure it has a backup feature so if something goes wrong with your changes, you can restore your registry to a proper working condition.

Things happen. Export/Backup your Norton Password Manager data.
Kudos0

Re: Issues since recently updating 360

I had the original SystemStatus entries.  They were excleded from future scans.

After going to 20.2 with NIS2013 in Windows 7 HomePremium x64 Thursday night, I gained the other two entries, MediaStatusSink.

Attempts to "fix" all 4 entries normally accomplished nothing.

So, what does it mean to say the incompatibility was fixed?

Kudos0

Re: Issues since recently updating 360

Entries are still there on my patched system
Kudos0

Re: Issues since recently updating 360

All I can say based on the words of the gurus is to ignore the N360 entries that appear on CCleaner and other registry cleaners.

If you really want to clean the registry, you're probably best just using the registry cleaner in N360 to do this, -but be careful- one mistake with a registry cleaner or manually changing the registry could corrupt the system.
Kudos0

Re: Issues since recently updating 360


collie21 wrote:
All I can say based on the words of the gurus is to ignore the N360 entries that appear on CCleaner and other registry cleaners.

If you really want to clean the registry, you're probably best just using the registry cleaner in N360 to do this, -but be careful- one mistake with a registry cleaner or manually changing the registry could corrupt the system.

My comment above stands.  It is best to use a registry cleaner with a backup feature, so you can recover from a cleaning that goes bad.

Things happen. Export/Backup your Norton Password Manager data.
Kudos2 Stats

Re: Issues since recently updating 360

Since we are talking about registry cleaners (pro and con), here is a very good article by quietman7 s posted on Bleeping Computer:

http://www.bleepingcomputer.com/forums/topic378243.html/

Please check out the other links at the bottom of his post!

Kudos0

Re: Issues since recently updating 360

Regarding what peterweb said,

I think N360 automatically generates Windows Restore Points before it performs registry cleans, which could act as a form of backup, so at least you have a method of recovering from a bad registry clean - but don't rely on that alone! Back up the registry before you use registry cleaning tools, if you're not confident with this, its best to leave the registry alone

Yank: Thanks for that article, pretty interesting

Kudos0

Re: Issues since recently updating 360


collie21 wrote:

Regarding what peterweb said,

I think N360 automatically generates Windows Restore Points before it performs registry cleans, which could act as a form of backup, so at least you have a method of recovering from a bad registry clean - but don't rely on that alone! Back up the registry before you use registry cleaning tools, if you're not confident with this, its best to leave the registry alone

Yank: Thanks for that article, pretty interesting


Can someone confirm that a restore point is created? I do not use 360 so I cannot check this.

Things happen. Export/Backup your Norton Password Manager data.
Kudos0

Re: Issues since recently updating 360

Hi Peterweb,

i have attached a screenshot of CCleaner showing the N360 pre Registry Clean system restore point.

Regards,

Collie21

Kudos1 Stats

Re: Issues since recently updating 360


pd123 wrote:

Apparently CCleaner issue was meant to be fixed with new release 20.2.0.19.  BUT.....

Not in my case, I now get 4 exceptions for Norton CCleaner can't clean, instead of 2 !!

Unused File Extension NortonAntiVirus.MediaStatusSink HKCR\NortonAntiVirus.MediaStatusSink
Unused File Extension NortonAntiVirus.MediaStatusSink.1 HKCR\NortonAntiVirus.MediaStatusSink.1
Unused File Extension Symantec.Norton.SystemStatus HKCR\Symantec.Norton.SystemStatus
Unused File Extension Symantec.Norton.SystemStatus.1 HKCR\Symantec.Norton.SystemStatus.1

NIS 2013

XP Pro SP3


pd123, same issue here; but using NIS 2013 with XP Home SP3.  Since I get the same registry issues every time I run CCleaner...and since the file extensions are, after all, "unused"...I just right-click on each entry and chose "Add to exclude list."  Problem solved, no harm done.  Hope this advice is helpful.

This thread is closed from further comment. Please visit the forum to start a new thread.