Hello, I’m on Windows 10 with the latest Dorico6 Pro. Recently, ‘File → Save’ and ‘Ctrl+S’ always open the ‘Save As’ dialog, even for projects that have already been saved. I tested with a brand new project, same result. The Hub still shows the correct file path. Diagnostic report attached. Thank you
Dorico Diagnostics.zip (1.4 MB)
Are you saving to Cloud storage, or an external drive?
No I save locally on my computer !
Hmm.. Windows 10. Unsupported well past EOL. There could be issues. No ,more security patches. Living dangerously. Yes, it’s a miserable situation, but that’s where we are.
… and you’re not having the same issue with any other app?
And you’ve rebooted?
I don’t think there have been other reports of this of the forum – so it might be a local problem with your setup, rather than a bug in Dorico itself. But I’m sure someone more knowledgeable will be along shortly.
Make sure you have permission to write to the destination folder. If you don’t, it will prompt to Save As…
ty derAbgang, I have checked the permissions. I can create a new text file in the destination subfolder and delete it without any problem, so I definitely have write permission there.
I have done some further testing. The problem occurs immediately when opening the project. The project already has an asterisk (*) in the title bar, even though I have not made any changes. If I immediately choose File > Save, without changing anything, Dorico opens the Save As dialog.
If I then select the correct subfolder and save the project to the same existing file, everything works normally afterwards: Ctrl+S saves the file without opening Save As.
I have also tested this with a brand-new project, with the same result. I have confirmed that I have write permissions for the destination folder. The Recent Projects list also shows the correct path.
This makes me think that Dorico is somehow losing the correct file path or save association when the project is opened.
Or possibly that the file is opened as read-only?
The logs report your filename as “mélodies d’été 26.dorico” — what happens if you use something that doesn’t require “special” (i.e. non-English) characters (assuming that’s what happened here)?
Oh man, how to do you expect a filename like that to even remotely work? There’s your problem. Sorry!
That’s your reader, the name is correct in Mac Terminal: mélodies d’été 26.dorico
I figured something like that; my point is that there might have been something (much like the problem with commas) that was causing the software to ‘reject’ the filename in lieu of a more ‘legal’ name. I was kind of grasping at straws to see if changing the name to something without special characters (knowing that they are not unusual in the language of origin) would make a difference. A comma in the filename or path has been known to cause problems; maybe there’s a similar incompatibility affecting this. As I said, “grasping at straws.” 
TY guys for your answers !
I tried with this file name “melodie summer 26” and a still have the same problem !
I can manage with this little discomfort and maybe a future update will fix the problem…
Thanks for checking — not sure, then (and the characters with the acute, grave, circumflex, etc., accents should be “legal” anyway)! I think someone (@benwiggy) asked if the file was opened as “Read Only”; other related things might be that the file is similarly “locked” as “Read Only” in the OS file system, or open in another app, or maybe in Dorico on another computer.
Is it just with this file, or any Dorico file? (Assuming it does not happen with other apps….)
Perhaps it is the spaces in the filename. I haven’t used Windows in a number of years but there was a time when spaces were “illegal” in file names in Windows if I recall correctly. Not a problem in macOS.
Windows has no problems with space in filenames.
Windows has allowed spaces for approximately forever, Yes, there was a time in once long ago, but that is irrelevant.
There are dozens of web pages with the allowed and disallowed characters for filesystems. Google it. There is no need for speculation.
One example:
So what sort of disk? Local, cloud based, Samba, USB stick, Dropbox (Dropbox has known issues…)?
Well, actually, allowing spaces in file names in Windows began in 1995 - only a few years before I changed to Apple products. So, in the larger scheme of things, that has not been “approximately forever” and suggesting that thought is irrelevant is just rude when one is grasping at straws to try to help. But, thank you for that nonetheless. I’m sure the favor will be returned one day. 