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
Returning Member
posted Feb 8, 2021 1:11:23 AM

Can you fix error code 102348 problem

error code 102348 when trying  to save or print

0 9 1911
9 Replies
Level 15
Feb 8, 2021 1:45:32 AM
Level 1
Feb 18, 2021 2:56:04 PM

I've encountered this issue too, and none of the suggestions in the link seem to be the solution.  Load, edit, save all work fine from a different location.  I'm wondering if it's an issue with a long file location/name.  I've run into that occasionally in the past with other apps.

Intuit Alumni
Feb 18, 2021 3:53:27 PM

If you are having issues and need assistance, please contact customer support. Please see the Customer Support phone number hereIf you would like to reach out through our website, please see the TurboTax FAQ below for contact information: https://support.turbotax.intuit.com/contact/

Level 1
Feb 27, 2021 12:27:22 PM

Thanks Katrina - I found the solution in another thread.  It was the Windows 10 Ransomware protection - just needed to enter TTax as an exception.

New Member
Mar 16, 2021 7:53:51 PM

I can not save my work on Turbotax

Intuit Alumni
Mar 17, 2021 9:51:47 AM

@Mercury64Comet Are you getting the error message 102348 when trying to save your information? If so, the following help article can offer some assistance on how to resolve this issue:  Error 102348: Cannot save tax file or File not found

 

If you are not experiencing this particular error but are still having difficulty saving your information, please describe exactly what's happening when you try to save.

New Member
Apr 2, 2021 1:54:10 PM

Mine was also because of Windows 10 ransomware protection

Level 1
May 14, 2021 5:33:04 AM

saving it to a location with a short path worked for me. thanks. (dealing with TT actually takes me longer than doing my taxes)

New Member
Mar 25, 2022 8:03:16 AM

Thanks for the Windows Ransomware reply.  That was the problem which is now fixed!!!