Document could not be saved file does not exist

I am seeing the same BUG (Apple, this can't be desired behavior). I have read, write, execute permissions on the subfolder. Current (inefficient) workaround:

1. Save to Documents
2. Move to...

   Select subfolder.

Shoot! This is exactly the same problem I'm having. I created a new text file, jotted down some text and tried to save it... and I got this error.

How is it possible that I can't save a new file? I get an error saying the file doesn't exist. No kidding! It's a new file I'm saving for the first time!

...?

What gives?

SOLUTION:

This is not a new issue, and yes it ***** that Mac will just simply post the answer here as its extremely easy.

The problem when you get that "The document Untitled could not be saved as "-----" . The file doesn't exist" message is actually nothing more than a Pathway problem. The pathway Text Edit wants to use has been corrupted and TextEdit has no idea where to turn.

Odds are VERY likely that if you look at the "start" folder of the path from which you are trying to save (and from which you probably save regularly), it is NOT the Top-Level Hard Drive Folder, but some folder inside the hard drive, possibly nested several layers in.

To Fix This:

1) Create any New TextEdit document, and click Save.

2) When the Save Dialogue box pops up, navigate BACKWARDS to the absolute Top Level Folder of your Mac (probably called something like "Macintosh HD" or the like - we are talking the level ABOVE your User name / account).

3) Click on that Top Level, and then navigate from there down through your User account to the actual folder where you would like to save your document. It does not matter how deep your desired folder is located as long as you Start from the absolute Top Level of your entire system.

4) Click Save. It should save Just Fine. 🙂

What you basically just did was tell your Mac which way to turn - the "directions" the Mac was using got corrupted and the TextEdit save process got lost in the woods. Doing the steps above sets the save process back on the correct path.

I have happily only ever had this problem twice, and this solved the issue 100% both times.

Here is what helped me:

option 1: Saving the file BEFORE entering any text. In this case the file is saved as it is supposed to be.

option 2: Instead of using the "save..." command in the menu bar AFTER having entered text I click on the title at the very top in the TextEdit window. Subsequently I can choose a file name and a destination. After doing this the file is saved. The given destination seems to be faulty - like already said before - but I think this method is a faster way of "repairing" it. You don't have to go all the way backwards to the top folder.

Apple doesn’t routinely monitor the discussions. These are mostly user to user discussions.

Send Apple feedback. They won't answer, but at least will know there is a problem. If enough people send feedback, it may get the problem solved sooner.

Feedback

I have exactly the same problem with an application called "RoadTripPlanner". I can save files to the default location, which is "Documents". If I try to save the file to another directory using "Save as" then I receive an error message saying "the file does not exist". The work around is to save the file to the default location, then manually move it the the respective directory, continue to work from there.

Based on the above mentioned cases we have to assume that this is not a bug in the application but in the OS (I'm using Yosemite 10.10.1 on a MacBook Pro Retina). It seems that quite randomly applications are affected by this problem.

I'd appreciate if the Apple engineers could look into this issue.

Hi Shamovala, this is a great answer! Thanks a lot.

Just out of curiosity, how did you figure out that the root of the problem was because the pathway was corrupted? I got 0 feedback from mac programs

Ever since I bought a mac in May it had been a mixed feeling of disappointment and appreciation. Mac sadly had too many little problems with very basic functionalities, such as losing the wifi connection and forcing me to delete wifi account and reset, and more often than not I don't get enough feedbacks from the program to be able to understand the problem better.

Apple, you need to get the very basic functionalities working without the users having to find a work around for you! I hate to think that I bought a mac machine that is now going into decline just because Steve is not here any more

But unfortunately it doesn't fix or solve anything...it's only a bandage solution so you can save the text until it happens again, and again, and again.

I use TextEdit to keep a running todo list for stuff I need to do at work. Stuff regularly gets added, erased, and changed, and I don't know how many times a month I can't save because I do multiple saves a day. (And before you suggest I use another program, I'm happiest using a text edit program rather than a format TODO list or Word.)

For me the FASTEST solution has been to do a CMD-A, CMD-C, CMD-Q, restart the software which opens the same file again, CMD-A, CMD-V, CMD-S...and that seems to work for a few weeks where I'll need to repeat the process.

As far as I remember after having saved the first time (save as...) the problem never occurred again. The path to the file was not corrupted - at least so it seems. I will check on this. For me clicking the title solved the problem.

Sorry for hearing you still have problems.

You can use your Apple ID to register with this site and go the Apple BugReporter. Supposedly you will get an answer if you submit feedback.

Feedback via Apple Developer

OK. If I save my file to the desktop, it saves. But if I save it to the folder I've created for text files, I get the "File Doesn't Exist" error.

Having the same problem. Any solution, Apple?

Have had this issue with Word and with TextEdit. Just started happening a week ago. Makes no sense.

Same problem here.

Seems like iWork thinks that a lot of my maps are write protected... maybe thats one of the issues... cant remove that protection though, so I dont know what happens