Protected mode won't let us extract pages or save files to a network drive.

Question

I understand that Adobe is not in favor of working on file servers, but not everyone is working in a cloud-based workflow. We are running Acrobat Pro 2026 and macOS Tahoe. Since upgrading we can no longer save Acrobat files to our server and extract pages won’t work either. We have one computer running the same versions of Acrobat and the OS where protected mode is turned off and it works fine. Our other computers have protected mode on and we are unable to turn it off. We can select to turn it off and quit Acrobat, but when we restart Acrobat it comes up with a message that Acrobat quit unexpectedly  and protected mode is turned back on. While we can save the files to the desktop and copy them to the server, this is an inefficient way for our team to work. Any thoughts on how to get Acrobat out of protected mode? Thanks!

Beth23082061er6k · Answer

So we have been in the middle of updating our entire department and it’s taken me a while to get back to looking into this further. So here are answers to your questions and what we have discovered since my initial post. I can totally understanding Acrobat preventing us from opening files that it believes to be suspect. But we are saving files that we have created internally to our local server and this shouldn’t be a problem and hasn’t been until this recent upgrade to macOS Tahoe and Acrobat 2026. I can’t believe we are the only business that still uses local servers. The process of having to save everything to our local machines and then copy to the server is not efficient and needs to be addressed by Adobe.

What's the exact Acrobat Pro build on the affected machines (Acrobat > About Acrobat Pro)? Is it the same build as the one working computer, or did the working one just not get the same update? Acrobat Pro versions were all the same, we were running v2026.001.21529. We did notice later that 2 of our computers were running slightly different versions of the MacOS, but this ultimately doesn’t make any difference. Also, we wouldn’t say that one computer was “working”, it was just that we could turn Protected Mode off on one and not the other. My understanding is that won’t be an option moving forward anyway as Adobe is requiring Protected Mode? In that case we just need to be able to save when in Protected Mode which is not currently the case.
Have you run Help > Check for Updates on the affected machines yet, in case there's a newer build than what's installed? We updated to Acrobat Pro v2026.001.21771 on 2 of the computers to test and it appears that we can now turn Protected Mode on and off again in the new version on both. We also updated to the latest version of MacOS on those 2 computers but still can’t save if Protected Mode is on.
Is the crash-on-relaunch happening only when you try to disable Protected Mode, or at other times too? The crash was occurring when we tried to disable Protected Mode, but that seems to have resolved and we can now disable Protected Mode. However, with Protected Mode on we cannot save to the server or extract files to the server. With it off we can save and extract. We also use the Pitstop plug-in and have updated it to the latest version compatible with Protected Mode as well. With Protected Mode off we ran into some glitches with Pitstop that require a restart of Acrobat to get it working again. These didn’t occur with Protected Mode on.

In the meantime, a couple of things worth trying:

Make sure all affected machines are fully updated, Help > Check for Updates, then restart. This is the single most common fix for Protected Mode regressions after an OS or app update. Everything (Acrobat, MacOS and Pitstop) was update to date as of last week.
Rather than turning Protected Mode off entirely, you can add your server path as a trusted location instead, which is meant for exactly this kind of workflow: Specify privileged locations in Acrobat (on Mac: Acrobat > Preferences > Security (Enhanced) > Privileged Locations > Add Folder Path). Note this affects Protected View more directly than Protected Mode itself, so it may help with opening/trusting files from the share even if it doesn't fully resolve the save/extract-pages restriction. We don’t have a problem opening files from the server, we have a problem saving files to the server and this didn’t help.
For general background on what Protected Mode restricts and known conflicts, Adobe's official troubleshooting page is here: Protected Mode troubleshooting. Not sure if this is applicable? I could see Protected Mode preventing us from opening files, but not from saving them?
You may also go through the correct answer marked in a similar discussion here When the sandbox (Protected Mode Disabled) preference is enabled... Grant Access alert on Mac. and see if that helps. We don’t receive the Grant Access dialog box in either mode, we simply receive a message, “The file may be read-only, or another user may have it open. Please save the document with a different name or in a different folder.” when Protected Mode is active. I used the Diagnostics tool and here is the Log ID 84e0b642-5bac-4ac1-97bf-0752fff1fb11.
Additionally, please check the steps shared in the help page https://helpx.adobe.com/acrobat/kb/error-acrobat-pro-dc-quit-unexpectedly-when-trying-to-open-acrobat-on-mac.html I didn’t do this as Acrobat is no longer crashing when switching modes.

Not sure what to do at this point. FYI Protected Mode exhibits the same behavior on an older Mac running MacOS Sequoia, so not an OS issue.

Thanks!

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.