Appdata File Security

Windows has become practically overwhelmed with file security. I have little use for it and the enhanced security is messing with the toolbar that I wrote years ago.

I have a file security problem where I cannot write to a data file in Appdata.

The read-only bit does not remain cleared and is probably never cleared although Explorer says it is. The app works on version 7 of course.

August 11th, 2013 11:11am

The "Read-only" bit is inconsequential to security.  It's an arbitrary attribute bit that an application can choose to ignore (most do).

If you're having permissions problems writing a file, the pertinent info will be in the Security tab.

Windows permissions / ACLs are very reminiscent of those invented by Digital - which is what you might expect given the author of Windows NT.

UAC sees to it that your normal processes run as a non-privileged shadow of your user account, presumably to protect your system from the things you haphazardly do (I hate the assumption that I'm using my computer stupidly, as I'm sure you do).  I guess most Windows users blindly execute anything from the internet that promises them glitz and glamour.

UAC also "magically" redirects some file accesses to different places on your drive, presumably to help make older software "better behaved".

You'll need to determine the specific permissions settings for the files you're trying to write, and what their paths really are.

What well-behaved applications (that need to access things that are for whatever reason normally blocked by UAC and permissions) are expected to do is this:

1.  Run their installers at an elevated privilege level (you set a flag to let Windows know you need this).  The user will have to answer a UAC prompt during installation.

2.  Access the things the application will need and specifically open up the permissions to allow the application ongoing unfettered access.  This might involve granting the user Full Control permissions, for example.

Beyond this, if you're really just looking to operate your computer yourself, and you EXPECT to have administrative privileges 24/7, then you might want to consider killing off UAC entirely.  The only downside to doing this is that Metro/Modern toy apps won't run without it on.  To shut off UAC is exactly like it was in early Vista releases, before Microsoft added the ability to disable it (which they've removed again):  You have to change the EnableLUA value in the registry to 0.

Hope this helps.

   

Free Windows Admin Tool Kit Click here and download it now
August 11th, 2013 1:32pm

It helped a little bit. I wrote the application years ago and I do have the source.

There never was an installer. The I/O comes and goes to a SQLCE database.

Let me take care of some puppy problems and I'll be back.

Renee

August 11th, 2013 1:49pm

Over the years starting with Win 7 functionality has slightly deteriorated, for example I can not rename buttons (which is in the database). It is of note that the changes are good until thr next reboot which also points to the writing of the database. The thing is, it has been so long since I wrote it and I've had a injury to boot, following the code is challenging.

To make it multiuser the databases for each user the database are in

Free Windows Admin Tool Kit Click here and download it now
August 11th, 2013 2:05pm

Hey, here is the first item in the database. Either sfilename or sName should change thier name if the user wants. At any rate-there is no change BUT I may have rebooted. I'll have to check.

Renee

August 11th, 2013 4:26pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics