Please Sign In with Norton Account to Ask a Question or comment in the Community
Posted: 17-Feb-2020 | 5:32AM · 126 Replies · Permalink
Running Norton 360 version 8.5.4 under OSX High Sierra (10.13.6) and I get about 2-3 kernel panics a day at the moment. It happens randomly sometimes even if the computer is just sitting there with no apps open. Uninstalling Norton 360 fixes the problem so it must be related to it somehow.
Anybody able to shed any light? I can probably supply crash logs if required.
Brian
Posted: 17-Feb-2020 | 7:33PM · Permalink
Good luck with it !
I have been complaining about that since December last year and NO ONE from Norton has addressed the issue.
Worse, when my emails were attacked recently and made unusable, Norton denied all responsibility, claiming the problem existed with or without Norton installed - totally irrelevant!
There just isn't enough hours in the day to keep this software running on Mac - should never have been released to market.
I was told 'an expert' would call me back to resolve - got a call 10 days later asking if they could close the case!!
This is the only time in more than twenty years that I have had a software issue on Mac and I am proceeding to cancel the subscription. NORTON was a respected name in the industry. Not any longer.
Buyer beware!
Posted: 18-Feb-2020 | 10:21AM · Permalink
I am hurt by the same problem. I was running Norton Security version 8.3 under OSX High Sierra (10.13.6). There was no kernel panic problem at that time. I upgraded Norton Security to Norton 360 in February 2020. Immediately after that, the kernel panic problem occurs at least once every day. The common feature of all kernel panics is only "a freed zone element has been modified in zone kalloc.128". However, the generated memory address, the generated time, and the generated process are all different and have no commonality. Isn't this problem a serious incident? Because the only workaround you can currently select is Norton 360 Uninstall. Please respond immediately.
Posted: 20-Feb-2020 | 6:54AM · Permalink
So today I contacted Norton online support and a very nice chap was informed of my problem and asked to remote access my machine. So via Team Viewer he dived in, checked to see if the product was up to date, turned on the Norton Secure VPN (despite the fact that I'm in a home office behind a hardware Firewall so no real need) and said 'all is OK with Norton, no problems, should be fine' and then finished. I asked if surely he would like to view the OSX crash logs etc but he wasn't interested (probably had no clue on what they are). I said I was not happy that he had actually done anything but he just signed off.
So basically he did nothing as far as I can see.
Just waiting for the next kernel panic and then I will be escalating this as far as I can go.
Posted: 24-Feb-2020 | 3:05PM · Permalink
Exactly the complete LACK of support I received from Norton - all they are trained to do is check latest updates and deny any responsibility. I suffered crashes on a daily basis.
I NOW HAVE THE FIX FOR THIS PROBLEM:
Cancel your subscription and remove all Norton software - my Mac and iPhone have been crash free for weeks now and I don't have to waste hours and hours!
Posted: 27-Feb-2020 | 11:49AM · Permalink
I used RemoveSymantecMacFiles to remove the Norton360 environment to reinstall Norton360. However, after reinstallation, Norton360 ran for 12 hours and finished in the kernel panic!
In addition, I compared this kernel panic with the past. There is no commonality between the aborted memory address and process. Common is "a freed zone element has been modified in zone kalloc.128".
Fix is important, but I want to find the anomaly first. Is there a way to incorporate the probe?
Posted: 27-Feb-2020 | 6:34PM · Edited: 27-Feb-2020 | 6:35PM · Permalink
I too suffer from this issue (2014 MacBook Pro running Mojave 10.14.6).
I upgraded to Norton 360 at Christmas (renewal time) and after about 2-weeks started to get Kernel Panic's after a few hours of use. Mac would restart and be good again for a while .. then the same thing - again and again and again .....
I searched for a solution with no luck and saw this forum ... so I am basically giving up on Norton and will shop around for other AV vendors in future (it doesn't' pay to be loyal anymore).
I did fix this issue - by de-installing/cleaning and removing EVERYTHING that had anything to do with Notion/Symantec etc and installed Avast free for the time being to see if the Kernel Panic's stop .... and yes - they HAVE stopped since removing Norton.
Seems this issue is MacOS related (I can see threads concerning Catalina) and the issue I have is on Mojave...
I don't expect the issue to be fixed anytime soon ... and I won't be hanging around to see it either.
Good bye Norton (after 7-years)
Posted: 28-Feb-2020 | 7:14AM · Permalink
https://www.cnet.com/news/tutorial-avoiding-and-eliminating-kernel-panics/
I read "Third-party software" on this site. And I decided to try a passive workaround. (because this workaround abandons 90% of the value of Norton 360.)
The workaround should DISABLE "Automatic Scans settings". (SEE! I abandoned 90%!!!)
After doing that, my mac has been running for 18 hours without spitting kernel panic.
Posted: 09-Mar-2020 | 10:34AM · Permalink
The previous method returned a kernel panic on the second day of testing...
SMUG! I DISABLE "Automatic Scans". However, macOS and / or N360 somehow ignore that setting!
I bet. If a bug wants "Automatic Scans", I'll make it happen. However, kext folders were excluded from scanning. (I guessed that kext memory space was corrupted from many kernel panic logs.)
Four days have passed with the new settings. The kernel panic is sleeping right now.
Posted: 31-Mar-2020 | 7:02PM · Edited: 31-Mar-2020 | 7:03PM · Permalink
I've been having this same problem for awhile. I was on Sierra up until a few weeks ago. I thought maybe that was the reason, because it was so old. I upgraded to Mojave, and I think the problem got worse. It now crashes every time the iMac goes to sleep. I just tried the @Romanesque solution, so we'll see how it goes. I really hope this goes away - it's such a time waster.
Posted: 31-Mar-2020 | 8:24PM · Permalink
Norton really needs to fix several issues that are plaguing the Mac version of Norton. I know several Norton customers who are looking to leave Norton because of issues with Norton for Mac.
Sudden Reboots
Several of my friends started experiencing sudden, random restarts. This issue appeared for them after Norton 8.4 was released. I am having the same exact issues.
I contacted Apple's software development team for an analysis. Not an Apple Store Genius but the actual software development team in Cupertino. Here is their response:
"Based on our analysis of your logs it appears that the Symantec kext is causing kernel memory corruption."
Conclusion? Norton has an issue with their Kext extension. It has not only been depreciated but it is apparently causing memory corruption in the kernel. This is why it is URGENT for Norton to fix this issue.
Other issues troubling Norton for Mac
Norton blocks Disk Utility from erasing disks. It will allow disks to be erased and reformatted in ExFat or Fat.
Norton will not allow disks to be erased and reformatted in APFS or MacOS extended.
https://pbs.twimg.com/media/EUaNhonU4AAAJC8?format=jpg&name=medium
Posted: 01-Apr-2020 | 4:56AM · Permalink
I have given up with this software and uninstalled it. Guess what - not a single Kernel panic since doing it.
I have moved my business to an alternative system which seem to work fine.
I tried on several occasions to get somebody at Symantec to respond to the issue but heard nothing.
If this is the level of support that users get then I say good riddance. It was woeful and shows that either they are aware of the issue but don't have a fix/want to admit to it or they have no desire to engage with their client base.
Either way - bye bye Norton
Posted: 03-Apr-2020 | 7:23AM · Permalink
Norton really needs to fix several issues that are plaguing the Mac version of Norton. I know several Norton customers who are looking to leave Norton because of issues with Norton for Mac.
Sudden Reboots
Several of my friends started experiencing sudden, random restarts. This issue appeared for them after Norton 8.4 was released. I am having the same exact issues.
I contacted Apple's software development team for an analysis. Not an Apple Store Genius but the actual software development team in Cupertino. Here is their response:
"Based on our analysis of your logs it appears that the Symantec kext is causing kernel memory corruption."
Conclusion? Norton has an issue with their Kext extension. It has not only been depreciated but it is apparently causing memory corruption in the kernel. This is why it is URGENT for Norton to fix this issue.
Other issues troubling Norton for Mac
Norton blocks Disk Utility from erasing disks. It will allow disks to be erased and reformatted in ExFat or Fat.
Norton will not allow disks to be erased and reformatted in APFS or MacOS extended.
Slow to Load
My iMac boots up in approximately 20 seconds. Norton adds over a minute before I can use the internet. The browser will just sit there and bounce while it waits for Norton to load. (This behavior seems to be unique to Norton in comparison to the competition.)
Please don't take this feedback as complaints. I have been a Norton subscriber for over 25 years. I like Norton and I want Norton to succeed by producing the very best product. That is why I am asking for improvements.
Thank you
Posted: 05-Apr-2020 | 5:38PM · Permalink
****UPDATE****
The @Romanesque solution I tried seems to be working. I made the changes about 6 days ago, and I haven't had any problem since. ::keeping fingers crossed::
Posted: 06-Apr-2020 | 12:56PM · Permalink
Hi,
I hope you are all safe and doing well.
Are any of you still seeing the kernel panic issues with the latest update - Norton Security for Mac 8.5.5 is now available!? Thanks.
-Gayathri
Posted: 06-Apr-2020 | 1:46PM · Permalink
Recently 8.5.5 has been released. I updated and verified from 8.5.4. Unfortunately, it did not include the gospel to the frequent kernel panic.
Expect next release.
Posted: 06-Apr-2020 | 1:57PM · Edited: 06-Apr-2020 | 1:57PM · Permalink
Hi, @cluelessgent.
Thanks for verifying the solution.
Posted: 07-Apr-2020 | 12:51AM · Edited: 07-Apr-2020 | 12:52AM · Permalink
Great...
So Symantec realise there is a problem and ‘fix’ it as part of the new version... maybe...
However the fact remains that I received no help or response to my issue beyond the initial attempt to look at my machine remotely by an inept and inexperienced support staff member.
Well, I’ve moved the machine on to a different product now with no issues so I will not be installing the update and risking going back to an unstable machine.
Sorry Symantec but your total lack of customer support has let you down, BADLY, and lost you a customer, never to return.
Posted: 07-Apr-2020 | 4:41AM · Permalink
Installed Mac 8.5.5 and it has been running for 24 hours. So far, so good. No kernel panics, no runaway processes, no sudden reboots. Although, the kernel task is using >1GB of memory. Etrecheck sees no issues. Keeping my fingers crossed.
Posted: 07-Apr-2020 | 7:17AM · Edited: 07-Apr-2020 | 7:18AM · Permalink
I'm on Norton 360 8.5.5 and my computer still crash with the same kernel panic than before...
«a freed zone element has been modified in zone kalloc.128»... Some other thread says it's directly related with Norton 360...
Macbook pro mid 2015, Mojave 10.14.6
Posted: 07-Apr-2020 | 7:22AM · Permalink
How do you remove «Kext Folders» from scanning like the solution says???
I've tried to do it but I don't know how...
Let me know if you have a chance... This is driving me crazy!!!
Posted: 07-Apr-2020 | 9:53AM · Permalink
Hi, @catl.
Please refer to the following URL (from Norton Support) for Automatic Scans method. https://support.norton.com/sp/en/us/home/current/solutions/v56157581
Add the following two types to "Don't scan these folders".
/System/Library/Extensions
/Library/Extensions
Posted: 08-Apr-2020 | 8:34AM · Edited: 08-Apr-2020 | 8:35AM · Permalink
Update. Installed Norton 8.5.5 for MAC 48 hours ago. No kernel panics yet. However, this morning I had a runaway process with the Norton SysDaemon using 352% of CPU according to Activity Monitor. The top of the MAC was hot enough to burn my hand after touching it for two seconds. I used force quit to stop Norton, this simultaneously forced the SysDaemon to quit. Then Norton relaunched itself and the SysDaemon. SysDaemon is now running at about 1% of CPU. Not sure how long this might last. This SysDaemon issue was previously occurring when I was also getting the kernel panics and reboots. So, as of now, I have little confidence in 8.5.5.
Posted: 08-Apr-2020 | 10:33AM · Permalink
Hi. @BA701
This is my OLD story.
I used Norton 7.x.x and the Norton's task periodically occupied 140% of the CPU for a long time (due to a 2-core CPU).
The cause was Norton's Error Management. Therefore, I turned off Error Management. This was my decision to balance CPU usage / error reporting to Norton.
The settings are now 8.x.x and I continue.
If you want to turn off error management, see the following URL: https://support.norton.com/sp/en/us/home/current/solutions/v89785784
Posted: 09-Apr-2020 | 6:44AM · Permalink
Just to signal that I run Norton 8.5.5 and I've had 4 crashes (about the same number I've had in the whole lifetime of my MacBook Pro 2014) between Tue and Wed. None as of today, and as I write this I've just applied the potential workaround of excluding the Extensions folder from the Automatic scan. Will evaluate the results.
Posted: 09-Apr-2020 | 7:02AM · Permalink
So I've tried @Romanesque solutions and it's not working for me... I've done the add to the «don't scan» option, I've turned off the error management...
Now, I'm trying to work without any scan at all... Will see...
I keep getting the same kernel Panic...
sfree on invalid allocation at 0xffffff8069f07430"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/Sandbox_executables/Sandbox-851.270.1/src/kext/smalloc.c:248
or
panic(cpu 2 caller 0xffffff8004394a08): "a freed zone element has been modified in zone kalloc.128: expected 0xdeadbeefdeadbeef but found 0xffffff802a549d50, bits changed 0x2152416ff4f923bf, at offset 88 of 128 in element 0xffffff80249c5580, cookies 0x3f0011037af47a90 0x53521f69d9192e3"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.61.1/osfmk/kern/zalloc.c:1229
Posted: 09-Apr-2020 | 9:15AM · Permalink
Hi, @catl.
As far as I can see the disclosed kernel panic log, it is very similar to mine.
Maybe the difference in macOS version is preventing the problem from being avoided. (My macOS is High Sierra 10.13.6.)
Sorry. I can't verify the version of macOS I don't have.
Posted: 10-Apr-2020 | 1:23PM · Permalink
Update. I have been running Norton 8.5.5 since Monday, Apr 6. Finally had the much anticipated kernel panic and sudden restart today (See Below). Just before crashing I again noticed the MAC getting really hot and again found the SymDaemon runaway process at 182% of CPU. I also had Error Reporting disabled; it didnt't help. So whatever Norton added in 8.5.5 didn't help.
Anyone know how to use Norton 360 just for VPN while killing the rest of the "features"?
Type:Kernel Panic
Details: panic(cpu 2 caller 0xffffff800eadff82): "c_decompress_page: c_segno 1276671 >= c_segments_available 6656, slot_ptr(0xffffff8049acf950), slot_data(29d37b00)"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4570.71.69/osfmk/vm/vm_compressor.c:3543
Date: 2020-04-10 15:05:37
3rd party extensions:
com.symantec.SymXIPS
com.symantec.internetSecurity.kext
com.symantec.ips.kext
com.symantec.nfm.kext
Posted: 12-Apr-2020 | 6:26PM · Permalink
Update. I have now had another kernel panic and sudden restart since reinstalling 8.5.5 after my last crash on April 10. Upon re-install I also disabled error reporting and excluded /System/Library/Extensions from Automatic Scans. This did not help. Further, since reinstall SymDaemon again eventually ran out of control dominating the CPU ~200% causing the machine to get extremely hot. Aside from these 'issues', Norton otherwise seems to be a good product. But, these issues make it unusable. Worse, Norton support experts have no idea what to do about it. Norton should probably quit marketing their MAC version until its fixed because its most likely screwing all of those MAC users who haven't yet figured out why their machine is crashing. I think I might rather have a virus than to struggle with Norton problems. Back to free Avast. Maybe someone (or Norton) will post a solution some day and I can try again.
Posted: 13-Apr-2020 | 10:43AM · Permalink
I have the same issue with two Mac computers.
Posted: 13-Apr-2020 | 10:48AM · Permalink
Hi! Thanks.
I updated to the latest version. However, I got the Kernel Panic message and my machine rebooted.
I hope your Technical Team can get a solution soon.
Posted: 13-Apr-2020 | 10:53AM · Permalink
Hi..
One of my Mac has similar symptoms (Mac Pro), it is usually running too hot and the CPU has high utilization. Also, it reboot with the following panic : ... /xnu/xnu-6153.81.5/osfmk/kern/zalloc.c:1229
Regards!
Posted: 13-Apr-2020 | 11:15AM · Permalink
No change with Norton Security 8.5.5
Sudden Reboots
Several of my friends started experiencing sudden, random restarts. This issue appeared for them after Norton 8.4 was released. I am having the same exact issues.
I contacted Apple's software development team for an analysis. Not an Apple Store Genius but the actual software development team in Cupertino. Here is their response:
"Based on our analysis of your logs it appears that the Symantec kext is causing kernel memory corruption."
Conclusion? Norton has an issue with their Kext extension. It has not only been depreciated but it is apparently causing memory corruption in the kernel. This is why it is URGENT for Norton to fix this issue.
Norton while you fixing the kext issue how about fixing these issues too:
Norton for Mac incessantly pops up requests for protocols that should be automatically allowed on the Mac.
- avconferenced (is the daemon that handles all webcam requests on macOS)
- CommCenter (service handling network connectivity on the iPhone, iPad and iPod touch.)
- rapportd (daemon that enables phone call handoff & other communication features between Apple devices.)
- sharingd (daemon that enables AirDrop, Handoff, Instant Hotspot, Shared Computers, and Remote Disc in the Finder.
Unfortunately Norton ignores your settings to allow these protocols. Please fix! Mac users starting reporting this in May 2019.
https://pbs.twimg.com/media/EVFftb2UcAMqGC3?format=jpg&name=medium
https://pbs.twimg.com/media/EVK1zEBUEAAmGok?format=jpg&name=medium
Norton pops up weekly asking me to enable Firefox and Safari add ons. Friends who use Norton are really ticked about this.
- Norton Home Page
- Norton Safe Search
- Norton Password Manager
- Norton Safeweb
I am only interested in Norton SafeWeb. Allow users to pick specific add-ons and not be pestered with the rest.
Other issues troubling Norton for Mac
Norton blocks Disk Utility from erasing disks. It will allow disks to be erased and reformatted in ExFat or Fat.
Norton will not allow disks to be erased and reformatted in APFS or MacOS extended.
Slow to Load
My iMac boots up in approximately 20 seconds. Norton adds over a minute before I can use the internet. The browser will just sit there and bounce while it waits for Norton to load. (This behavior seems to be unique to Norton in comparison to the competition.)
Please don't take this feedback as complaints. I have been a Norton subscriber for over 25 years. I like Norton and I want Norton to succeed by producing the very best product. That is why I am asking for improvements.
Thank you
Posted: 14-Apr-2020 | 12:44AM · Permalink
Hi Gayathri. I have Norton Security for Mac 8.5.5 and I am experiencing 1 kernel panic attack every day. Looks like this update hasn't solved the problem.
Looking forward to a solution. I've used Symantec for a very long time and am a big fan so I'm hoping Symantec won't compel me to switch to an alternate product.
Thanks
Posted: 14-Apr-2020 | 12:48AM · Permalink
The workaround didn't work for me neither. Suffering between 1 and 2 kernel panics every single day. As I work with virtual machines as well who get suddenly stopped posing a potential threat to their integrity, I'm seriously pondering to give up with Norton.
Posted: 14-Apr-2020 | 7:01AM · Permalink
I had a very simple question when I saw info.plist of kext of Norton 360 for mac.
"Is it possible for macOS to run a module built in a higher OS without problems in a lower OS?" (At least some Japanese office computers cannot do that.)
There are 4 folders for kext of Norton 360 for mac (8.5.5). If this is further divided into groups with BuildMachineOSBuild in info.plist, there will be two groups.
- GROUP: 18G84 (macOS 10.14.x)
= com.symantec.nfm.kext (9.0.1)
= com.symantec.internetSecurity.kext (9.0.3)
- GROUP: 15D21 (macOS 10.11.x)
= com.symantec.ips.kext (9.0.2)
= com.symantec.SymXIPS (9.0.1)
If macOS supports both lower compatible and upper compatible, these groupings have no meaning.
However, if macOS supports only one of the compatibility, Norton 360 for mac is meaningless in macOS 10.13.x.
My thoughts that are derived from here:
Norton 360 for mac may be released without operation verification.
Can the development team theoretically eliminate my idea?
Posted: 15-Apr-2020 | 5:47AM · Permalink
Hi,
Would those of you who are still seeing this issue be able to send us logs? I can send you a private message with the steps. Thanks.
-Gayathri
Posted: 15-Apr-2020 | 6:20AM · Permalink
Log?
Is it a panic report from a kernel panic or is it a zip that you manually launch and harvest from Norton 360 help?
Posted: 15-Apr-2020 | 12:53PM · Permalink
Hi Gayathri;
If you want a zip it may not be accurate.
Because zip (Symantecinfo.txt) can collect the record of Symantec crash, but it does not contain the record of kernel crash that we are concerned about.
The point of this problem is that the kernel is ascended by Norton 360, not the crash of Norton 360.
Therefore, I think that zip alone is insufficient information.
Given these, I would like to know the log collection procedure you request.
Thank you.
Posted: 15-Apr-2020 | 2:08PM · Permalink
**Supplement**
As a fact that is difficult for users to notice, there is a fact that Norton 360 / 8.5.5 itself is crashing. (A single crash also happened in 8.5.4).
Fortunately, this is the information included in the zip.
The reason why it does not surface is that macOS does not appeal the fact that Norton ascended. The user needs to actively observe the Symantec log folder.
Posted: 16-Apr-2020 | 6:29PM · Permalink
Oh, by the way,
it just Norton 360.app crashed. Fortunately(?), it's not a kernel panic.
As a precaution, I checked the plist of "norton 360.app".
UNBELIEVABLE!!!
That is, "norton 360.app" showed macOS 10.14 (or higher) as the build environment, similar to kext.
ALL SEE!
Norton 360 for mac (8.5.x) builds on macOS 10.14 (or higher), but it was released as a product without testing with all versions of macOS promised to users.
Isn't this the new Coronavirus of a certain country?
Can the Norton Support Team destroy my over-imagination?
Posted: 17-Apr-2020 | 10:58AM · Permalink
Hi, Gayathri_R;
Thank you for publishing the log collection procedure.
And by chance. Eight hours ago, my macOS was shutdown and reboot with kernel panic. At that time, I was collecting the zip file using the same procedure that you published in the message.
I upload two files, a zip file and a kernel panic report (Kernel_2020-04-17-191423_MacBook-Pro.panic_.zip).
My thoughts with the kernel panic report attached;
Because I want you not to loop in the next labyrinth.
-There is no evidence of kernel panic in SymantecInfo.txt (37. CrashReporter and other Symantec logs).
-The evidence is Norton 360.app crash.
-The user provided a log that cannot be used for the survey.
However, I suspect that the root causes of the kernel panic and the norton 360.app crash are the same. The root cause is that the kernel panic trigger kext and norton 360.app are both modules built with a version higher than my macOS. (The reason why the mac cooling fan suddenly goes to high speed for a long time, or the CPU continues to be under heavy load).
If the root cause is my opinion, the answer is simple.
Pattern A; Rebuild on each macOS version guaranteed by Norton 360 for mac.
Pattern B; Rebuild with macOS version which is the range of compatibility guarantee of macOS.
As I imagine, please check the log and solve the problem as soon as possible.
Thank you
Posted: 18-Apr-2020 | 1:36PM · Permalink
Thank you for the logs, @Romanesque. Much appreciated.
Posted: 18-Apr-2020 | 4:55PM · Permalink
Gayathri
I reinstalled Norton 360 just yesterday, April 17; it took only 26 hours for the SymDaemon problem to manifest (395.2% of CPU) then another 4 hours for the kernel panic and sudden restart. Logs attached.
Posted: 19-Apr-2020 | 4:25PM · Permalink
TLDR: frustrated complaining.
This is getting more and more ridiculous and frustrating.
Several Kernel Panics a day (and way too much unsaved stuff disappearing almost every time). Even windows vista on a crappy cheap pc was more stable than what my Macbook is with Norton 360.
I still need to stick with Mojave 10.14.6 for awhile, but surely the macOS I am using should not be the problem?
I am sooo regretting of buying the Norton 360. I thought that would be an easy option for good stabile security on my and my familys computers. Now I am stuck with 1429 days remaining of Norton 360 Platinum and randomly kernel panicking laptops, just great.
(log attached)
Posted: 20-Apr-2020 | 6:32AM · Permalink
I've been following this thread for a couple weeks and it appears there is still no solution.
I have a iMac that reboots almost nightly and always references the Symantec kexts in the panic logs. At this point to prevent other damage from occuring, I'm left with no choice but to remove the product.
It could be reinstalled at a later day if a solution is posted here.
If a Symantec engineer wants my logs please contact me directly.
Posted: 20-Apr-2020 | 10:58AM · Permalink
At the moment, my Mac's with Norton are the most crash prone computers that I have had since Windows 3.0 or my Commodore Amiga with workbench 1.1.
Norton really needs to step up to the plate and hit a home run here.
Right now it appears that Norton just slopped the Mac version together with limited or no product testing. (I might be wrong about this, however, it is getting harder and harder to suppress this suspicion.)
Let us look at the problems with Norton for the Mac
- Sudden reboots (Kernel Crashes)
- Incessant pop up requests for protocols that should be automatically allowed on the Mac. For example:
- avconferenced (is the daemon that handles all webcam requests on macOS)
- CommCenter (service handling network connectivity on the iPhone, iPad and iPod touch.)
- rapportd (daemon that enables phone call handoff & other communication features between Apple devices.)
- sharingd (daemon that enables AirDrop, Handoff, Instant Hotspot, Shared Computers, and Remote Disc in the Finder.
Norton blocks Disk Utility from erasing disks. It will allow disks to be erased and reformatted in ExFat or Fat.
Norton will not allow disks to be erased and reformatted in APFS or MacOS extended.
Finally,
Norton pops up weekly asking me to enable Firefox and Safari add ons. Come on Norton, enough is enough. Let me stop these pop ups.
This thread is closed from further comment. Please visit the forum to start a new thread.