×
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
cyberdude
Reliable Contributor
Reliable Contributor
Message 11 of 18

Re: Total Protection not working on macOS Monterey 12.1 MacBook Pro M1X

hello @GaneshR 

could you assist perhaps ?

cyberdude
Reliable Contributor
Reliable Contributor
Message 12 of 18

Re: Total Protection not working on macOS Monterey 12.1 MacBook Pro M1X

hello @SusanMoser 

i would like to ask if you have been contqcted by a mcafee mod in the meantime ?

greetings

Catelle
Contributor
Message 13 of 18

Re: Total Protection not working on macOS Monterey 12.1 MacBook Pro M1X

Dear All, 

 

I have installed Monterey 3 days ago, I should read your posts before doing this...

Now each time I open McAfee and click on, for example Update ( but I have same problem for pretty all action), the app shuts down and I have this report ( part of the report):

Translated Report (Full Report Below)
-------------------------------------

Process: McAfee LiveSafe - Internet Security [4784]
Path: /Applications/McAfee LiveSafe - Internet Security.app/Contents/MacOS/McAfee LiveSafe - Internet Security
Identifier: com.mcafee.console
Version: 4.11.2 (4.11.2)
Code Type: X86-64 (Translated)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2022-04-29 13:50:52.0861 -0400
OS Version: macOS 12.3.1 (21E258)
Report Version: 12
Anonymous UUID: 5D7B4E04-6B9C-A146-E864-3B57D473566C


Time Awake Since Boot: 15000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.Metal.DeviceDispatch

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000076694c282078
Exception Codes: 0x0000000000000001, 0x000076694c282078
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [4784]

VM Region Info: 0x76694c282078 is not in any region. Bytes after previous region: 129713585004665 Bytes before following region: 10234081304456
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
commpage (reserved) 1000000000-7000000000 [384.0G] ---/--- SM=NUL ...(unallocated)
---> GAP OF 0x7f481af00000 BYTES
MALLOC_TINY 7fb81af00000-7fb81b000000 [ 1024K] rw-/rwx SM=PRV

Thread 0 Crashed:: Dispatch queue: com.Metal.DeviceDispatch
0 libobjc.A.dylib 0x7ff800894593 objc_retain + 35
1 Foundation 0x7ff8017f84e9 -[NSBundle infoDictionary] + 39
2 Foundation 0x7ff8017fcf16 -[NSBundle bundleIdentifier] + 22
3 AGXMetal13_3 0x7ffa1b3c2df9 0x7ffa1b049000 + 3644921
4 libdispatch.dylib 0x7ff80084a317 _dispatch_client_callout + 8
5 libdispatch.dylib 0x7ff80084b4fa _dispatch_once_callout + 20
6 AGXMetal13_3 0x7ffa1b3be1ad 0x7ffa1b049000 + 3625389
7 AGXMetal13_3 0x7ffa1b3d4aea 0x7ffa1b049000 + 3717866
8 Metal 0x7ff8097efb08 -[MTLIOAccelService initWithAcceleratorPort:] + 382
9 Metal 0x7ff8097ef964 +[MTLIOAccelService registerService:] + 143
10 libdispatch.dylib 0x7ff80084a317 _dispatch_client_callout + 8
11 libdispatch.dylib 0x7ff8008577ee _dispatch_lane_barrier_sync_invoke_and_complete + 60
12 Metal 0x7ff8098b85bd MTLIOAccelServiceRegisterService + 71
13 Metal 0x7ff8097ef7cf +[MTLIOAccelDevice registerDevices] + 146
14 Metal 0x7ff80981a115 invocation function for block in MTLDeviceArrayInitialize() + 1195
15 libdispatch.dylib 0x7ff80084a317 _dispatch_client_callout + 8
16 libdispatch.dylib 0x7ff80084b4fa _dispatch_once_callout + 20
17 Metal 0x7ff8097ef63f MTLCopyAllDevices + 189
18 CoreUI 0x7ff80835e704 ___CUIShouldUseMetalShaders_block_invoke + 11
19 libdispatch.dylib 0x7ff80084a317 _dispatch_client_callout + 8
20 libdispatch.dylib 0x7ff80084b4fa _dispatch_once_callout + 20
21 CoreUI 0x7ff80835e6f3 __38-[CUIHueSaturationFilterLocal _kernel]_block_invoke + 288
22 libdispatch.dylib 0x7ff80084a317 _dispatch_client_callout + 8
23 libdispatch.dylib 0x7ff80084b4fa _dispatch_once_callout + 20
24 CoreUI 0x7ff80835e5d1 -[CUIHueSaturationFilterLocal _kernel] + 42
25 CoreUI 0x7ff80835e29e -[CUIHueSaturationFilterLocal outputImage] + 451
26 Foundation 0x7ff8018220e0 -[NSObject(NSKeyValueCoding) valueForKey:] + 307
27 CoreUI 0x7ff80833f3f5 -[CUIShapeEffectStack standardEffectCompositeWithShapeImage:blendOntoImage:] + 443
28 CoreUI 0x7ff80835cb6c -[CUIShapeEffectStack newFlattenedImageFromShapeCGImage:withScale:cache:] + 148
29 CoreUI 0x7ff808347e86 -[CUIThemeFacet updateLayer:effects:] + 691
30 CoreUI 0x7ff8083626d9 CUICoreThemeRenderer::MakeOrUpdateProgressBarLayer(CUIDescriptor const*, CALayer**) + 2369
31 CoreUI 0x7ff808345885 CUICoreThemeRenderer::CreateOrUpdateLayer(CUIDescriptor const*, CALayer**) + 843
32 CoreUI 0x7ff8083454b6 CUIRenderer::CreateOrUpdateLayer(__CFDictionary const*, CALayer**) + 184
33 AppKit 0x7ff80342d822 -[NSCompositeAppearance _callCoreUIWithBlock:options:requireBezelTintColor:] + 386
34 AppKit 0x7ff803447c95 -[NSAppearance _createOrUpdateLayer:options:] + 79
35 AppKit 0x7ff80358623b -[NSProgressIndicator updateLayer] + 529
36 AppKit 0x7ff8034f3ec9 _NSViewUpdateLayer + 98
37 AppKit 0x7ff8034105eb +[NSAppearance _performWithCurrentAppearance:usingBlock:] + 66
38 AppKit 0x7ff80364fb82 __30-[_NSViewBackingLayer display]_block_invoke + 113
39 AppKit 0x7ff80344c885 -[NSFocusStack performWithFocusView:inWindow:usingBlock:] + 92
40 AppKit 0x7ff8034f3892 -[_NSViewBackingLayer display] + 383
41 QuartzCore 0x7ff807fe3951 CA::Layer::display_if_needed(CA::Transaction*) + 873
42 QuartzCore 0x7ff80813a336 CA::Context::commit_transaction(CA::Transaction*, double, double*) + 640
43 QuartzCore 0x7ff807fc5231 CA::Transaction::commit() + 777
44 AppKit 0x7ff80358f761 __62+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayLink]_block_invoke + 285
45 AppKit 0x7ff803cd6668 ___NSRunLoopObserverCreateWithHandler_block_invoke + 41
46 CoreFoundation 0x7ff800ac6f75 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
47 CoreFoundation 0x7ff800ac6e0a __CFRunLoopDoObservers + 543
48 CoreFoundation 0x7ff800ac628c __CFRunLoopRun + 840
49 CoreFoundation 0x7ff800ac5884 CFRunLoopRunSpecific + 562
50 HIToolbox 0x7ff809bbbce6 RunCurrentEventLoopInMode + 292
51 HIToolbox 0x7ff809bbb913 ReceiveNextEventCommon + 283
52 HIToolbox 0x7ff809bbb7e5 _BlockUntilNextEventMatchingListInModeWithFilter + 70
53 AppKit 0x7ff80342353d _DPSNextEvent + 927
54 AppKit 0x7ff803421bfa -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1394
55 AppKit 0x7ff8034142a9 -[NSApplication run] + 586
56 AppKit 0x7ff8033e8227 NSApplicationMain + 817
57 dyld 0x204e4251e start + 462

Thread 1:: com.apple.rosetta.exceptionserver
0 runtime 0x7ff7ffebd9a4 0x7ff7ffeb9000 + 18852
1 runtime 0x7ff7ffecb738 0x7ff7ffeb9000 + 75576
2 runtime 0x7ff7ffecced0 0x7ff7ffeb9000 + 81616

Thread 2:
0 ??? 0x7ff890fd6940 ???
1 libsystem_kernel.dylib 0x7ff8009ccd5a __select + 10
2 libfmphelpers.dylib 0x10d361aa9 FMP::FMPCommBroker::run(void*) + 457
3 libsystem_pthread.dylib 0x7ff800a014e1 _pthread_start + 125
4 libsystem_pthread.dylib 0x7ff8009fcf6b thread_start + 15

Thread 3:: com.apple.NSEventThread
0 ??? 0x7ff890fd6940 ???
1 libsystem_kernel.dylib 0x7ff8009c497a mach_msg_trap + 10
2 libsystem_kernel.dylib 0x7ff8009c4ce8 mach_msg + 56
3 CoreFoundation 0x7ff800ac7db0 __CFRunLoopServiceMachPort + 319
4 CoreFoundation 0x7ff800ac6440 __CFRunLoopRun + 1276
5 CoreFoundation 0x7ff800ac5884 CFRunLoopRunSpecific + 562
6 AppKit 0x7ff803590f5e _NSEventThread + 132
7 libsystem_pthread.dylib 0x7ff800a014e1 _pthread_start + 125
8 libsystem_pthread.dylib 0x7ff8009fcf6b thread_start + 15

 

 

 

Model: MacBookPro17,1, BootROM 7459.101.3, proc 8:4:4 processors, 16 GB, SMC
Graphics: Apple M1, Apple M1, Built-In
Display: SE2717H/HX, 1600 x 900, Main, MirrorOn, Online
Display: Color LCD, 2560 x 1600 Retina, MirrorOn, Online
Memory Module: LPDDR4
AirPort: Wi-Fi, wl0: Feb 8 2022 01:44:45 version 18.60.21.0.7.8.126 FWID 01-1cdae627
Bluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
USB Device: USB31Bus
USB Device: USB3.0 Hub
USB Device: STORE N GO
USB Device: USB 10/100/1000 LAN
USB Device: USB2.0 Hub
USB Device: USB Billboard Device
USB Device: USB31Bus
Thunderbolt Bus: MacBook Pro, Apple Inc.
Thunderbolt Bus: MacBook Pro, Apple Inc.

 

I have already turn on manually the firewall, this works now, but I can't do update, I can't delete item in quarantine, etc...

 

 

do you have same issue? any solution?

 

many thanks 

 

best regards

cyberdude
Reliable Contributor
Reliable Contributor
Message 14 of 18

Re: Total Protection not working on macOS Monterey 12.1 MacBook Pro M1X

@Catelle 

recent i have seen posting in different section about problems with Mac Os Monterey.

if i check your posting i notice that your computer has Apple M1 chip ?

if so, there are currently some problems using Mcafee with this chip model.

person that had also problems contacted live support and was told that they are aware of the issue and working for fix.

however, no timeframe could be given.

what i understand is that using mcafee it is advised to install rosetta2 on your mac.

if this is not on your system currently you could read about his from following service doc;

McAfee KB - McAfee LiveSafe crashes or quits unexpectedly on M1 Apple silicon devices (TS103282)

hope this helps

Catelle
Contributor
Message 15 of 18

Re: Total Protection not working on macOS Monterey 12.1 MacBook Pro M1X

Hi @cyberdude

 

Since Big sure, apparently Rosetta 2 is included directly with the IOS, when I installed McAfee, it never asked me to load Rosetta. And with Bigsure, I didn't have any problem with McAfee, it is since I have changed the IOS for Monterey. 

 

many thanks!

Nielss
Contributor
Message 16 of 18

Re: Total Protection not working on macOS Monterey 12.1 MacBook Pro M1X

I am another person who tried to run Total Protection on my Macbook Pro M1 Pro/Monterey 12.3. (It won't surprise anyone reading these messages that it crashed every time I tried to do something with it.) For the last hour, I've been on the phone with McAfee support (good on them for even having phone support, I must say) and I think I might have successfully gotten a refund. This involved:

1. I call tech support: Long conversation follows. He has no idea what and M1 Pro chipset is (OK, that's pretty geeky), and he keeps asking "what application" I'm running that is crashing McAfee. Twice, he puts in a call to his tech support (interesting--I never knew that tech support has tech support, but it makes sense). After walking me through a download a remote support app, there is a brief silence. Then, he tells me "Oh---I see, this is a known issue. Here's a case number for your refund."

2. I get transferred to billing. After waiting on hold, I talk to someone who is supposed to arrange my refund. However, he refuses, and tells me this issue has been FIXED. So, he shoots me back to tech support, but not before eating up another 10-15 minutes with questions that suggest he's now completely aware that Windows 11 doesn't run on Macbook Pros (well, unless--never mind). 

3. Tech Support redux: After much time on hold, and a repeat of the previous script with the tech support guy, he finally advises me that "It's a known issue." He suggests I wait until some indefinite date in the future when it gets fixed.  I said "No thank you," and suggested I get my refund (it's a 60-day guarantee, and I bought the app yesterday).  He wants to know if I'm sure--after all, I get five devices with my license, and it might work on another device. I told him that was a fair point, but it isn't why I bought it and remind him that McAfee advertises a 60-day MONEY-BACK guarantee.. He says "OK," and sends me back to the billing team (where I was before).

4. Another wait ensues. After spending the obligatory 10 minutes on hold, a rep asks for my case number. I give her the number, and since I know what's coming, I fend off the script in which they convince me not to cancel my subscription but install Total Protection on another device instead. Eventually, the billing rep takes pity on me and processes a cancellation of my subscription and a refund.

Bottom line: if it's worth an hour of your time for a $39.99 refund (teaser price for the first year), you CAN actually get McAfee to honor their guarantee. Would I do it again? Probably not--that's an hour I'll never get back. But still, I think this story speaks well of McAfee, and when I come back to this forum and read that y'all are successfully running Total Protection, I will probably even buy it again.

Canesguy
Contributor II
Message 17 of 18

Re: Total Protection not working on macOS Monterey 12.1 MacBook Pro M1X

Too bad I was too late to get a refund on my McAfee subscription.  Needless to say I not be renewing in December..

matthewb
Contributor II
Message 18 of 18

Re: Total Protection not working on macOS Monterey 12.1 MacBook Pro M1X

I too will not be renewing my subscription. This is the second time in a couple of years that this has happened. I like McAfee’s product, but they can’t seem to get ahead of the curve when it comes to Apple products. I’m not sure that would be my business model, but to each their own...

@mcafee You are going to lose a lot of market share if you can’t keep your product working on Apple products. 

How Many Badges Can You Collect?
Ready for a little competition? Members like you are earning badges and unlocking perks for their helpful answers. Are you? Click here to find out.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community