Solved Can't save file to C:\ despite changing ownership & access

So sick of the patronisation of recent Windows releases. I am currently on 8.1.

I can't figure out what else I have to do, to save a config file to the root of C. It's an old application, and that's where the config needs to go.

I am worried that the medicine is worse than the illness in this problem - all the messing around with ownership might have damaged my windows installation.

Who needs to be the owner of what, on C: for me to simply save a file there?

My user is already the owner, and it's an admin user. I propagated across C: and then added System and Trusted installer with Full admin access.

Yet i STILL cannot write to C: Getting message: Error 0x80070522: A required privilege is not held by the client.
:w00t:

What more do I have to do, to write to my own c: drive on my own computer.....

Hope somebody can help!

No help from Microsoft's article, but answer found in comments on a video on youtube...

[h=3]João Vitor Ferreira[/h]9 months ago

For me the problem was that the Admin Approval Mode was Enabled.
To change that do the following: 1. Run->secpol.msc 2. Local Policies->Security Options. 3. Set "User Account Control: Run all administrators in Admin Approval Mode" to Disable. 4. Restart the P

That's disabling UAC which is the way I always run. I did it this way:

Change the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System

Key: EnableLUA

Value data: 0

Note: This prevents Metro/Modern apps or Store from working.

Click to expand...

secpol.msc seems easier though.

Ztruker said:

That's disabling UAC which is the way I always run. I did it this way:

Change the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System

Key: EnableLUA

Value data: 0

Note: This prevents Metro/Modern apps or Store from working.

Click to expand...

secpol.msc seems easier though.

Click to expand...

No actually - I had already disabled UAC. This disables something additional. Google to learn more.

martienne said:

Ztruker said:

That's disabling UAC which is the way I always run. I did it this way:

Change the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System

Key: EnableLUA

Value data: 0

Note: This prevents Metro/Modern apps or Store from working.

Click to expand...

secpol.msc seems easier though.

Click to expand...

No actually - I had already disabled UAC. This disables something additional. Google to learn more.

Click to expand...

Yes, you're correct. I was the one that first published that finding. It works well for things like not needing to specify an elevated command prompt, because it always is, if set. Things like that.

This was complete news to me. I had never even come across the Local Security manager before.
Seems to be a relatively undocumented feature.
For each version of Windows they are making it harder to be an educated user, and easier to be a muppet who can hardly turn off his computer all the time, but needs a user interface that look like a playboard for a toddler.

I did not use secpol.msc, I used the methods I described and the

"User Account Control: Run all administrators in Admin Approval Mode"


is disabled, so how can it be any different?