Chat support available. Click the chat icon on the bottom right corner to start chatting with us right away!

Support mSecure

Msecure crashing on macOS 11.7.10 (20G1427)


can you send an update? its been a few weeks now.

It crashes at startup.



Process: mSecure [30276]

Path: /Applications/

Identifier: com.mseven.msecuremac

Version: 6.1.5 (999)

App Item ID: 1157750250

App External ID: 861573689

Code Type: ARM-64 (Native)

Parent Process: ??? [1]

Responsible: mSecure [30276]

User ID: 501

Date/Time: 2023-12-17 10:10:47.757 +0100

OS Version: macOS 11.7.10 (20G1427)

Report Version: 12

Anonymous UUID: 9D916621-8575-AABB-0351-A98BEE745CB2

Sleep/Wake UUID: 57A33DDD-5F47-474D-B50E-765704C2290F

Time Awake Since Boot: 520000 seconds

Time Since Wake: 3700 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue:


Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000


Termination Signal: Segmentation fault: 11

Termination Reason: Namespace SIGNAL, Code 0xb

Terminating Process: exc handler [30276]

VM Regions Near 0:


    __TEXT 100b1c000-100dd8000 [ 2800K] r-x/r-x SM=COW /Applications/

Thread 0 Crashed:: Dispatch queue:

0 ??? 000000000000000000 0 + 0

1 com.mseven.msecuremac 0x0000000100cfbffc 0x100b1c000 + 1966076

2 com.mseven.msecuremac 0x0000000100cf5704 0x100b1c000 + 1939204

3 com.mseven.msecuremac 0x0000000100cf60e8 0x100b1c000 + 1941736

4 libdispatch.dylib 0x000000019d2afec0 _dispatch_client_callout + 20

5 libdispatch.dylib 0x000000019d2b1758 _dispatch_once_callout + 32

6 com.mseven.msecuremac 0x0000000100cf60ac 0x100b1c000 + 1941676

Hi Simon,

Thank you for following up on this issue. Unfortunately, our developer has not been able to figure out what's causing this issue. The strangest thing about is not everyone running Big Sur is experiencing the issue. He's still looking into the problem, so I hope we'll have a new update published to the store soon. In the meantime, we do have a legacy build of the 6.1.4 version that does solve the problem.

If you're interested in getting access to that legacy build, please email us at to let us know. After you send the email, let me know here in this thread, and I'll get back to you as soon as I see your email.

Connexion ou Inscription pour poster un commentaire