Parallels crashes upon startup on macOS Sequoia 15 beta

Discussion in 'Installation and Configuration of Parallels Desktop' started by MauricioC7, Sep 6, 2024.

  1. MauricioC7

    MauricioC7 Bit poster

    Messages:
    4
    I have the Standard permanent license for version 18. After updating my two devices, a Mac Mini and a MacBook Pro, both with M2 chips, I was able to install and run Parallels on the Mac Mini without any issues. However, on the MacBook Pro, I couldn't. As soon as Parallels is installed and I try to run it, the error below occurs. I've already tried troubleshooting steps from other forums, such as attempting to install via terminal and deactivating the license, but the same error persists. Has anyone experienced a similar situation and managed to resolve the issue?

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

    Process: prl_client_app [35604]
    Path: /Applications/Parallels Desktop.app/Contents/MacOS/prl_client_app
    Identifier: com.parallels.desktop.console
    Version: 18.3.2 (53621)
    Build Info: Parallels-53621.0~18.3.53621.0
    Code Type: ARM-64 (Native)
    Parent Process: launchd [1]
    User ID: 501

    Date/Time: 2024-09-06 13:39:42.0356 +0200
    OS Version: macOS 15.0 (24A5331b)
    Report Version: 12

    Time Awake Since Boot: 210000 seconds
    Time Since Wake: 13264 seconds

    System Integrity Protection: enabled

    Crashed Thread: 0 Dispatch queue: com.apple.main-thread

    Exception Type: EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000

    Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
    Terminating Process: prl_client_app [35604]

    Application Specific Information:
    abort() called

    Kernel Triage:
    VM - (arg = 0x0) Fault was interrupted
    VM - (arg = 0x0) Fault was interrupted
     
  2. O_B

    O_B Bit poster

    Messages:
    6
    Yep.
    After the latest update to Sequoia:

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

    Process: prl_client_app [2314]
    Path: /Applications/Parallels Desktop.app/Contents/MacOS/prl_client_app
    Identifier: com.parallels.desktop.console
    Version: 19.4.1 (54985)
    Build Info: Parallels-54985.0~19.4.54985.0
    Code Type: ARM-64 (Native)
    Parent Process: launchd [1]
    User ID: 501

    Date/Time: 2024-09-08 21:41:15.7648 -0500
    OS Version: macOS 15.0 (24A5331b)
    Report Version: 12
    Anonymous UUID: 06EFE60B-56B6-677D-AAF6-45B798BD4857


    Time Awake Since Boot: 430 seconds

    System Integrity Protection: enabled

    Crashed Thread: 0 Dispatch queue: com.apple.main-thread

    Exception Type: EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000

    Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
    Terminating Process: prl_client_app [2314]

    Application Specific Information:
    abort() called
     
  3. Adeboye Adeotan

    Adeboye Adeotan Staff Member

    Messages:
    443
    Hello O_B,

    Please be informed that this issue has been fixed in our latest release of Parallels Desktop, version 20.

    Provided you have a subscription, you may install Parallels Desktop using the following link:

    https://link.parallels.com/link/66dfeea0xN44
     
  4. MauricioC7

    MauricioC7 Bit poster

    Messages:
    4

    Hello Adeboye,
    But won't this fix be applied in version 18? Will those who acquired a perpetual licence for this version now be left with this unresolved issue?
     
  5. O_B

    O_B Bit poster

    Messages:
    6
    Uninstall/reboot/reinstall resolved the issue.

    My Windows VM did not boot cleanly after the fresh installation, but Parallels did load.
     
  6. Adeboye Adeotan

    Adeboye Adeotan Staff Member

    Messages:
    443
    Hello O_B,

    Are you still experiencing this issue with your Windows virtual machine?

    If so, please collect a technical report at the moment of issue reproduction (Help > Send technical data > check "Attach screenshots..." > press Send Report) and send the report's 9-digit ID as a reply to this post.
     
  7. MauricioC7

    MauricioC7 Bit poster

    Messages:
    4
    Hi O_B,
    Thanks, it worked for me too.
     

Share This Page