What you’re seeing
- Folders on workstations still carry their old permissions after the policy was linked and refreshed.
- Permissions corrected by hand keep reverting to a previous state.
- Application event log errors mention security policy processing or file system settings.
- Startup takes noticeably longer on PCs that do receive the policy.
Common causes
Every environment is different, but these are the causes our engineers find most often:
- File system permissions in Group Policy are applied with security settings, which only reapply at startup or on a periodic security refresh.
- Another policy, script or application also sets permissions on the same folder, and they keep overwriting each other.
- The folder path in the policy uses a drive letter or variable that resolves to a different location on the target PCs.
- Security filtering or organizational unit placement keeps the policy from reaching the computer accounts.
- The policy replaces permissions on all subfolders and files, which takes a long time on large folders and can fail partway through.
- The ACL references local groups or accounts that don't exist on the target machines.
Why it matters
These policies usually exist for a reason: to let an application write to a protected folder, or to lock down data that only certain staff should see. When they don't apply, either the app fails for standard users and generates support calls, or sensitive folders stay more open than intended. Permissions that flip back and forth are especially costly, because each fix seems to work until the next refresh, wasting time and undermining confidence in your configuration.
How AskTechGurus fixes it
Skip the trial and error. A certified engineer works on your actual system, finds the root cause, and fixes it properly.
Tell us what’s happening
Submit a ticket in about two minutes. Paste the error, describe what changed, and pick your tier. No charge to submit.
A certified engineer diagnoses it
A vetted, US-based systems engineer claims your ticket, usually within minutes during business hours, and investigates over a secure remote session you can watch and end at any time.
Fixed and verified with you
The engineer resolves the root cause and confirms with you that it’s working. You don’t just get a workaround, and you get a plain-English summary of what was wrong.
Pay only when it’s resolved
Fixed price from $99, invoiced only after you approve the fix. If it isn’t resolved, you don’t pay.
Frequently asked questions
Could users currently have more access than they should?
Yes, if the old permissions were broader than the new ones. Until the policy applies correctly, the previous access stays in place.
Why do our manual corrections keep getting undone?
Something else is set to manage the same folder, often another policy or a script. Until the competing source is found, each one overwrites the other.