PDF Security & Access Issues

How to Fix PDF File Permissions Not Inheriting from Windows Folders

Phi Hung VoPhi Hung Vo Nov 2, 2026 869 views

Question details

PDF files moved between Windows work-queue folders are retaining their original permissions instead of automatically inheriting the destination folder's permissions.

How to Fix PDF File Permissions Not Inheriting from Windows Folders
Product
PDF Files
Device & OS
Windows
Scenario
Moving PDF documents across different Windows directories within a workflow queue and expecting them to adopt the security properties of the new destination folder.
Observed behavior
The moved PDF fails to inherit the destination folder's permissions, restricting file access, even though other workflow steps function correctly.
Before you start

Ensure you are logged in with an administrator account on your Windows PC to view and modify NTFS security and folder inheritance settings.

Solution 1Recommended

Force Inheritance via Windows Advanced Security Settings

Use the Windows folder properties menu to push inheritable permissions to all files currently residing inside the destination folder.

This issue typically arises from Windows NTFS behavior rather than Adobe Acrobat or PDF properties. When moving files on the same drive volume, Windows retains the original permissions. Pushing inheritance from the parent folder corrects this for existing files.

1
Open Folder Properties

Right-click the destination Windows folder containing the PDF and select 'Properties' from the context menu.

2
Access Advanced Security

Navigate to the 'Security' tab and click the 'Advanced' button located at the bottom of the window.

3
Enable Inheritance

Check the box at the bottom that says 'Replace all child object permission entries with inheritable permission entries from this object'.

4
Apply Changes

Click 'Apply' and then 'OK'. The PDF file will now correctly inherit the folder's security permissions.

Force Inheritance via Windows Advanced Security Settings
Testing Workflows: After applying the changes, test your workflow by opening the PDF in a PDF reader to ensure proper access is fully restored.
WPS PDF Tools

Save As a New PDF with WPS Office to Reset Permissions

If Windows moving permissions continue to disrupt your workflow, you can easily use WPS Office to 'Save As' a new document directly in the destination folder. Creating a new file directly forces Windows to apply the destination folder's inherited security settings automatically.

  1. 1. Open the PDF in WPS Office: Launch WPS Office and open the PDF file that has incorrect permissions.
  2. 2. Trigger the Save As Function: Click on the 'Menu' button in the top-left corner and select 'Save As' from the dropdown list.
  3. 3. Select Destination and Save: Choose the correct work-queue folder as the destination and click 'Save'. The newly saved file will perfectly inherit the folder permissions.
Instantly bypasses Windows NTFS move-permission bugs by generating a fresh fileFully compatible with all standard PDF formats and Adobe Acrobat propertiesLightweight and highly efficient PDF viewer, editor, and annotatorSeamlessly integrates into existing document queue workflows
microsoft office alternative - wps office

Frequently Asked Questions

Why do PDF files keep their old permissions when moved in Windows?

This is standard Windows NTFS file system behavior. When you move a file to another folder on the exact same drive volume, Windows simply updates the file's directory pointer and retains its original security permissions. It does not automatically apply the new folder's permissions.

Is this an Adobe Acrobat specific bug?

No, this is related entirely to Windows folder security and NTFS permissions. It can happen to Word documents, Excel spreadsheets, and image files as well, although it is often noticed during automated PDF workflow processes.

How do I fix permission inheritance for an entire drive?

You can right-click the drive or root folder, go to Properties > Security > Advanced, ensure 'Enable Inheritance' is turned on, and check the option to replace child object permissions. Proceed with caution as this overrides any custom file securities previously set.