☰
✕
Sign In

Why sign in to the Community?

  • Submit a question
  • Check your notifications
Sign in to the Community or Sign in to TurboTax and start working on your taxes
New Member
posted Jul 18, 2023 1:21:57 PM

After installing Big Sur on a Mac mini (2018 intel), then installing from the CD and doing the mandatory upgrade, the software crashes.

Process:               TurboTax 2022 [1467]
Path:                  /Applications/TurboTax 2022.app/Contents/MacOS/TurboTax 2022
Identifier:            com.intuit.turbotax.2022
Version:               2022.r39.068 (2022.r39.068)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           TurboTax 2022 [1467]
User ID:               501

Date/Time:             2023-07-18 13:00:51.610 -0700
OS Version:            macOS 11.7.8 (20G1351)
Report Version:        12
Bridge OS Version:     7.5 (20P5060)
Anonymous UUID:        4962D9B9-9814-4385-AC95-BD15E946382D

0 4 708
4 Replies
Level 15
Jul 18, 2023 1:31:43 PM

We have seen several users have this problem after updating to the latest Mac software.

Contact TurboTax support for assistance.

 

See this TurboTax support FAQ for contacting support - https://ttlc.intuit.com/turbotax-support/en-us/help-article/account-management/turbotax-phone-number/L0Od33nMQ_US_en_US?uid=lfgviwbm


Support can also be reached by messaging them on these pages https://www.facebook.com/turbotax/ and https://twitter.com/TeamTurboTax

Level 2
Jul 22, 2023 12:48:26 PM

@DoninGA You've seen it, but when are you fixing it? 

Level 15
Jul 22, 2023 12:58:32 PM

@Puddington That question has to be answered by TurboTax support.  Not by a volunteer on this forum who does Not work for Intuit/TurboTax.

Level 2
Jul 23, 2023 10:39:39 AM

Intuit knows about a major problem with their latest software and there are no messages or emails addressing it, no tweets, nothing. Call TurboTax support for them to do what exactly? I am talking about a  defective software that won't open. 

 

And to you being a volunteer, good for you! But I've seen you deflecting this problem as it being Mac OS issue, which it is certainly NOT, in a different post. That makes me question your impartiality.