How to Fix Acrobat Shared Review Selected Folder Is Invalid Error
Question details
The user is attempting to set up a shared review or shared commenting folder in Acrobat but receives an error stating that the selected location is not a valid folder.

- Product
- Adobe Acrobat
- Device & OS
- not provided
- Scenario
- Setting up a shared folder for collaborative PDF commenting or initiating a shared review over a network.
- Observed behavior
- Acrobat displays a persistent error message stating 'the selected location is not a valid folder' and prevents the shared review configuration from proceeding.
Ensure you have the necessary administrative read and write permissions for the network or local drive you are trying to use. Verify that your network connection is stable before attempting to troubleshoot the folder path.
Verify Folder Permissions and Network Path Accuracy
The most common cause of this error is insufficient folder permissions or an incorrectly mapped network path.
Acrobat requires explicit read/write access to host the review files. If the path is mapped incorrectly or restricted, it will default to an invalid folder error.
Navigate to the intended shared folder in your file explorer, right-click it, and select 'Properties'. Under the 'Security' tab, ensure your active user profile is granted both Read and Write permissions.
When entering the folder location in the Acrobat setup wizard, use the full UNC network path (e.g., \\ServerName\SharedFolder) instead of a mapped drive letter (like Z:\), which Acrobat may fail to recognize.
Try creating a temporary folder on your local desktop. Proceed to set up the Acrobat shared review using this local folder to confirm whether the issue is isolated to network or firewall restrictions.

Check WebDAV or SharePoint Configurations
If you are using a web server or SharePoint for the shared review, an incorrect URL format or authentication issue will trigger the invalid folder error.
Collaborate on PDFs Seamlessly with WPS Office
Avoid complex network folder configurations, WebDAV setups, and permission errors. WPS Office provides built-in, easy-to-use PDF collaboration, commenting, and sharing features directly within its modern PDF editor.
- 1. Open your PDF in WPS Office: Launch WPS Office on your device, click on the 'PDF' tab, and open the document you wish to share for review.
- 2. Add your comments and annotations: Navigate to the 'Comment' tab on the top ribbon. Here you can highlight text, insert sticky notes, underline content, or draw shapes to annotate the document.
- 3. Share the document via link: Click the 'Share' button in the top right corner. You can instantly generate a shareable link to collaborate with colleagues without needing to troubleshoot complex network shared folders.

Frequently Asked Questions
Why doesn't Acrobat support my OneDrive folder for Shared Review?
Adobe Acrobat's traditional Shared Review feature relies on network drives, WebDAV, or SharePoint to host the review file XML structure. Standard cloud-syncing services like OneDrive or Dropbox local folders lack the server-level response mechanisms Acrobat requires, causing it to read the location as an invalid folder.
Can a firewall cause the invalid folder error in Acrobat?
Yes. If your computer's firewall or network security policies block Adobe Acrobat from pinging the network directory or WebDAV server, it will assume the folder does not exist or is invalid. Ensure Acrobat is whitelisted in your firewall settings.
Is Adobe Shared Review still the best way to collaborate on PDFs?
Adobe has been transitioning users to cloud-based 'Send for Review' features via Adobe Document Cloud. Using standard shared network folders is considered a legacy feature, which is why it often encounters SMB protocol or permission issues on newer operating systems.
How do I clear cached server locations in Adobe Acrobat?
Open Acrobat, navigate to 'Edit' > 'Preferences', and select the 'Tracker' category from the left pane. From there, you can manage or clear cached server profiles that might be retaining outdated network credentials or corrupted paths.




