InDesign 2023 makes a read only file

[Christina228449123bw0]

I have just updated to the 2023 InDesign, and now suddently my documents are read-only and I cannot save the file, but have to make a save as version and give the document a new name everytime I have to save my work.

Do you know why this is happening? And how to avoid this?

[leo.r]

I'm running InDesign 19.0.1, on Mac OS Monterey (12.6), at home and not on any network. 

By mhvz2019

For starters, try to update to the latest InDesign 19.4 and macOS 12.7 (the latest Monterey if you have to stay there).

To complicate the situation, you problem sounds like a known bug in InDesign 19.4 (although I'm not sure it's exactly the same one). So if you're still experiencing this issue in 19.4, then try to revert to 19.3 (you can do so from Creative Cloud app).

[mhvz2019]

I've just now tried it on my work computer (Monterey is my home one) running Mac OS Big Sur 11.7.3 and InDesign 19.4 and it's working absolutely fine. As you mentioned my issue on my home computer is a know issue in 19.4, it must be OS specific as there are no problems on my work version.

[HARSHIKA_VERMA]

Hi @mhvz2019 & @HeiniB,

Sorry for the delay in responding. It looks like you're experiencing the read-only issue on your Mac machine. The fix that went in for 18.4 was for Windows only.

However, for the Mac machines, we suggest you try disabling the Mac preview for InDesign files to see if that is indeed the cause of this issue. We will share the information with the team so they can investigate in the right direction.

Please share your Adobe ID, phone number, location, and the best time to contact you so we can contact you directly for a debug session on your machine.

We will try our best to help you.

Thanks,

Harshika

[HeiniB]

Unfortunately, it seems that it is pointless to post your problems here, as Adobe is obviously not interested in users' problems.
They are only interested in our money...
As you can see above, the last (petty) response from Adobe was almost a year ago.

[pifath67]

Update to 19.5.
It has become even worse...
Almost EVERY file (newly created or existing) is now write-protected.
it is almost impossible to work reasonably efficiently.
Thanks for nothing, Adobe!

[pifath67]

We haven't heard anything about “read-only” for a long time.
Apparently the users have come to terms with the problem and Adobe no longer needs to work on it.
As long as they get their money for the subscription and everyone keeps quiet, all is well with the world...

[Abhishek Rao]

Hello everyone, 

I understand how frustrating this read-only issue can be, especially when it disrupts your workflow. We're committed to addressing your concerns and improving your experience with InDesign. 

If you haven't already, please try disabling the Mac preview for InDesign files, as it might be contributing to this problem. We recommend keeping your software updated to the latest versions, as they often include important fixes.

For those still facing this issue, your feedback is invaluable. Please share any details you can, such as your operating system version and any specific circumstances under which the problem occurs. This information will help us investigate further and find a resolution.

Thank you for your patience, and we're here to assist you!

Best,

Abhishek Rao

[MJMarek]

Just FYI: I have this issue accessing a PC via VPN (WIN 11); however, I have found that opening the INDD file directly from file manager is a viable workaround. If I open directly from InDesign, all files open as read only. 

[karend23069192]

I'm on a mac and before I open larger files I switch from column view to list view and then double click the file to open and it opens as it should. If I open it in column view I get a read-only file.

[Abhishek Rao]

Hi MJMarek and karend23069192,

Thank you for sharing your experiences and workarounds! It’s great to hear that you’ve found solutions that help you manage the read-only file issue. Switching views or directly accessing files through the file manager seems to be effective for some users.

For others still encountering this problem, your insights are invaluable. If anyone else has similar experiences or additional workarounds, please feel free to share them. We're continuously gathering feedback to address these issues and improve InDesign’s performance.

Thank you all for your patience, and we’re here to help!

Best,
Abhishek Rao

[pifath67]

I think most of us work with an absolutely standard environment. I, for example, work with MacOS Ventura and a file server with Windows Server 2019.
It shouldn't be rocket science for developers to find a bug like this.
For us, on the other hand, who pay a lot of money for functioning software that we have to work with on a daily basis, this error means a lot of lost time, risk of errors and frustration.
So please do something about it!
By the way: the “workarounds” mentioned in this thread have all been tried and have not helped.

Translated with DeepL.com (free version)

[Abhishek Rao]

Hi pifath67,

Thank you for your feedback, and I understand your frustration with the read-only issue. We’re actively working to resolve this, and your input is invaluable.

Could you please share a screen recording demonstrating the problem? This will help our team troubleshoot more effectively. In the meantime, ensure you're using the latest version of InDesign.

Thank you for your patience!

Best,  
Abhishek Rao

[pifath67]

Here are the screen videos of various scenarios:
1. file is immediately opened read-only.
2. file is not write-protected until after the 4th opening.
3. an already write-protected file is saved to another location and is then write-protected again.
4. a file that is not write-protected is write-protected after saving.
I hope this helps.

[Abhishek Rao]

Hi @pifath67,

Thank you for sharing the screen recordings; they are greatly appreciated. We recognize how frustrating this issue can be, and we’re actively looking into it.

Please make sure you’re on the latest version of InDesign, as it includes important updates. Update to the latest version and let us know if that resolves the issue. If you encounter any other specific patterns or problems, don’t hesitate to share.

Thank you for your patience!

Best,  
Abhishek Rao

[Abhishek Rao]

Hello @pifath6,

Could you please let me know if the file is being saved locally or on a remote file server? If it's on a remote server, try saving it locally to your macOS and check if the issue persists.

Looking forward to your update.

Thanks,
Abhishek Rao

[pifath67]

Hello,

first, i use Indesign 2025, latest Update.

And the issue only appears with files on our file server. Locally the problem doesn't appear.

[Abhishek Rao]

Hi @pifath67,

Thank you for the update!

Since the issue is only occurring with files saved on your file server, could you please provide the details of the SMB version being used on the file server? InDesign's performance can sometimes be affected by the SMB protocol version, so it's important to ensure compatibility.

Please consider these guidelines:

• If you’re using SMB 1, it is recommended to upgrade to a newer version like SMB 2 or SMB 3, as these are more reliable and secure.
• Ensure that both your macOS and the file server support the same version of SMB to minimize any file-handling issues.
• If possible, you can try switching to a newer version temporarily to check if it impacts the behavior.

Moreover, I recommend reaching out to your IT admin regarding this, especially since the issue does not persist when saving files locally. They may be able to assist with adjusting the SMB settings or addressing any server-related concerns.

Please let me know if changing the SMB version helps resolve the issue or if you need any assistance in making the changes.

Looking forward to your response!

Best,
Abhishek Rao

[pifath67]

We use Windows Server 2019 with SMB2 on our servers and the MACs also support this.
According to our IT department, a test change to SMB3 is not possible without problems, as these are virtualized servers and the change would then also affect other areas of the company, whose production could then possibly be disrupted.

[pifath67]

It is almost impossible to work with this software in a halfway efficient way and without frustration.
You constantly have to save files under new names or somewhere else and overwrite the previous one to avoid getting confused with multiple versions of the same file.
The problem that you cannot overwrite existing PDF files when exporting because they are supposedly open still exists too.
When will something finally be done about these errors other than just writing pointless posts in the forum to annoy us users?
This problem has been known for over two years now and NOTHING has been done about it.
Customers who pay a lot are being ripped off here!

[Abhishek Rao]

Hey pifath67,

I totally get your frustration – constantly saving files with new names is a huge pain. From what you've shared, it seems the issue might be related to the network setup. While  InDesign is tested across multiple network configurations, not all setups are tested. Different network configurations, software, and hardware can sometimes cause these annoying glitches. As the issue is not seen when files are saved locally, it might be the configuration of permission on the File server which again needs to be looked upon by your IT team. 

The only workaround I’d suggest, for now, would be to save the files locally and avoid saving them directly to the server. I know that's not ideal, but it could help prevent the read-only issue.

Appreciate your patience, and I’m here if you need anything else!

Best,  
Abhishek

[pifath67]

Unfortunately, it is not possible to grant more than full disk access and administrator rights. And the Mac clients have these on the file server.
In addition, the error first occurred after an InDesign update without anything being changed in the user configuration on the network.
InDesign is also the only program with which we have problems with write protection.
All of this suggests to me that the problem is more likely to be with Indesign.
And don't forget, we are not the only ones who have the problem...

[Abhishek Rao]

Hello @pifath67,

Thank you for your patience. I discussed this with the product team, and they have informed me that a bug has been logged for this issue. The team is currently investigating it, and I will keep you updated with any progress or if further information is needed.

^
Abhishek

[pifath67]

Just did an InDesign update.
Surprise: Nothing has changed regarding the write protection problem or the problem of not being able to overwrite PDF files.
I think the "team" should stop collecting information and start solving the problem.
I have the feeling that no one at Adobe is interested in a solution. It's just a lot of work...
This really can't be called customer service - it's more of a rip-off. You get an inferior product for a lot of money.

[pifath67]

Addendum: It is NOT possible to overwrite an existing PDF even if ALL folder windows have been closed, Acrobat has been closed, and the file hasn't been opened previously. Message: File is already open. Haha...
Possible workaround: Shut down the computer before saving 😉
When will these serious bugs finally be fixed, Adobe?

[pifath67]

It's nearly impossible to work sensibly and efficiently because almost EVERY file is opened as read-only.
Why do WE always have to use workarounds to compensate for the shortcomings of the software we pay a lot of money for?
After all, WE are the customers, for whom a minimum level of service could be provided.
But large companies apparently don't care about customers once they've paid for the product...
It's sad...