Access rights on Win7 AllUsers Application Data folder

Question

0.00/5 (No votes)

See more:

My Windows desktop app shares settings between Windows users, so I keep a settings file under AllUsers Application Data (wherever that might end up). All works fine on WinXP but on Vista/7 I find that only Windows Administrators can change files this area. I don't yet provide a manifest so each user thinks he can change settings but virtualization ensures that each user actually has his OWN settings file. This breaks the idea of Common (allUsers) AppData.

I could always run my app at Elevated access - BAD idea! for many reasons.

I can set the ACL on my AppData folder at installation time - ok until someone cleans up or loses my folder when subtle bugs happen.

I'm tempted to put the settings back into my Program Files installation folder and set the file's ACL there - would this work? Could I set up a user-writable folder within my installation folder?

Where is my shared application data expected to live?

Posted 28-Jan-10 1:45am

myGuid

Updated 29-Jan-10 0:18am

Tony Richards

v3

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Tony Richards · Answer 1 · 2010-01-29T00:17:00

I wouldn't suggest playing with ACL at installation time: if you app is installed in a business environment, for example, the changes may fail.

Be careful about putting things in your installation folder as well. If your program ends up in Program Files, you could end up with the same problem.

What are you using to make the program? If you're using the .Net Framework, you could try using the built in Settings features which can have Application scope settings as well as User ones.