Cannot save files directly to root C:\ drive anymore

[rzn6jw]

I'm configured as Administrator and, up until a few days ago, I was able to save files directly to the root C:\ drive. I now get the error: ''The required privilege is not held by the client". I can still create/rename/delete folders on the drive, though, without that error message. This is only occurring on my C:\ drive; I can save files on all the drives OK.

I'm running Win 7 Pro 64-bit with NIS 2012.

Any ideas?

 

[logicearth]

Stop saving files to the root of the C: drive, there I said.

 

[rzn6jw]

The point is that I was able to save files and now I can't. What changed? Was it a Windows update or could it be NIS 2012? Or do I have a hidden rootkit/malware (Malwarebytes, IoBit and NIS all say I'm clean)?

I can save files directly to the root drive on my wife's Win 7 32-bit Home Premium PC also running NIS 2012, so it appears as having something to do with my admin security on the 64-bit PC.

 

[rzn6jw]

I have to run apps in 'Admin' mode to be able to save to C:\ root driv

This is in addition to my previous thread where, logged on as an Administrator and running Win 7 Pro 64-bit, suddenly I couldn't save files directly to my root C:\ drive:

If I run the program (ie, Notepad) as Administrator, I can 'Save As..' directly to the root drive. If I run the program normally, I can't.

This all started a couple of weeks ago when I downloaded the Witcher 2 from Steam and tried to run the program from the Steam library. Clicking on the run icon, nothing would happen. Searching the Steam forums, I found that other users were having the same problem and the resolution was to run Steam, the Witcher 2 launcher, and the Witcher 2 .exe all as Administrator. That worked fine.

Then, a few days later, other Steam games I had been playing OK started acting the same way, so I configured them for Admin also.

Now it seems that my logon ID, even tho I log on as Administrator, doesn't act as an Admin.

Any ideas what is going on?

 

[jav]

The reason why you cant save to root (C:\ in your case) is due to the fact that Windows 7 dosent allow non-admins to save to root...

Even when you login with your admin account UAC strips down admin privileges from you.
You can change it if you want (personally don't recommend it) http://www.sevenforums.com/tutorial...-uac-change-notification-settings.html?filter

If you right click your drive and go to Security tab, you can see that Users don;t have Write privileges. (you can click EDIT/ADVANCED and change it there. Not recommended aswell )

 

[rzn6jw]

Attached is a shot of the Administrator Security and UAC control panel settings for my C:\ drive. Even though my ID as a user and as an Administrator have full control, I still cannot save to the root. Up until 2 weeks ago, I could. I'm wondering what has changed. I can save to the root if I run the program I want (ie. Notepad) as Administrator but I didn't used to have to do that. Has some Win 7 update changed the Admin access or something?

 

[Britton30]

This all started a couple of weeks ago when I downloaded the Witcher 2 from Steam and tried to run the program from the Steam library.
Then, a few days later, other Steam games I had been playing OK started acting the same way, so I configured them for Admin also.


Any ideas what is going on?

I think see a pattern here my friend. Steam is one of a large handful of sites/programs which cause problems with Windows 7. Try uninstalling it and see if the problem goes away.
Regardless if you could save files to the system root two weeks ago, it's not recommended. Steam may be the cause.

 

[Lukas123]

I'v run into the same problem, on a clean Windows 7 install. Like most installs, I setup 1 user, who is System Administrator. There's no way MS can hide behind the fact it does not like administrators to write into their own drives ! I found both C:\ and the Program Files folder to be in that case. What Logicearth says, is so wrong, he states that an administrator should have no control over its own system. Who will do that then ? Create another account because the right-system in Windows is crap ? Not writing in the root, because the right system is crap ? No.

I've disabled UAC as a function, and I'm waiting until MS makes it working, but I don't expect that ever to be in Windows 7. I'm expecting something clear and correct, like the average Unix OS.

 

[logicearth]

I'v run into the same problem, on a clean Windows 7 install. Like most installs, I setup 1 user, who is System Administrator. There's no way MS can hide behind the fact it does not like administrators to write into their own drives ! I found both C:\ and the Program Files folder to be in that case. What Logicearth says, is so wrong, he states that an administrator should have no control over its own system. Who will do that then ? Create another account because the right-system in Windows is crap ? Not writing in the root, because the right system is crap ? No.

I've disabled UAC as a function, and I'm waiting until MS makes it working, but I don't expect that ever to be in Windows 7. I'm expecting something clear and correct, like the average Unix OS.

Oh can you write in the root file system on Unix/Linux systems? No!? Listen let me explain something to you. You are not prevented from controlling your system you have full control. Microsoft is not to blame because you lack knowledge on configuring permissions, the same you would need to do on Unix/Linux. Do you think you have access to the system directories on Unix/Linux even with an Admin account? No you do not! That is were the "root" account comes into play.

 

[Lord Lucan]

Stop saving files to the root of the C: drive, there I said.

We are not tyros here; so we are not talking about saving a letter we wrote to Aunt Matilda. I like to write a short note on the root of every partition (I have about 16 of them, with various OS's on them) saying what partition it is - you know, like "SATA 3 80Gb drive, 3rd Primary". This is because Windows in particular tries to confuse us by inconsistent drive lettering depending which version I boot.

Do you think you have access to the system directories on Unix/Linux even with an Admin account? No you do not! That is were the "root" account comes into play.

I am not convinced you know what you are talking about. You can always name an account in Linux as "Admin" but there will be nothing special about it. The Linux equivalent of the Windows "Administrator" is "root". If you log in to the Linux "root" account you can write, delete and edit whatever you want, including writing to the root directory (equivalent to the Windows C:\) which in my case is in its own partition. Perhaps you have only experienced a dumbed-down version of Linux, like Zorin or Ubuntu? I just tried it, successfully, in Debian, as you sounded so convincing.

In fact one solution to the problem of writing to the Windows C:\ would be to boot Linux (maybe from a live disk) and do it from there.

 

[ron7000]

attached are 2 pics of my security settings, in win7 64-bit professional on home computer, having all windows updates accept for the win10 ones to avoid.
I have my UAC set to the lowest - never notify.
And my Administrator account is enabled.
My ron account is in Administrators group.
I also have steam installed, last week downloaded fallout new vegas, anyone who likes that needs their head examined. got rid of it and now doing modern warfare 2.
I can create new folder and text file on C:\ with no problem.

I see this kind of problem often on work computers where security folks hack gpedit and the registry.
Have seen things such as an administrator account not able edit a file like C:\windows\system32\drivers\etc\hosts in place. Have to copy that file out to the desktop, edit and save on the desktop, then copy modified file back to location and say overwrite. This is so the system is more secure. If yours is doing it you should be happy :haha:


you can try removing all folder/files under C:\Windows\System32\GroupPolicy\
or move the contents out of that location so it's empty,
then reboot, that will clear any group policy settings that may be causing your problem.
Copy back those files/folders under the GroupPolicy folder then reboot to restore what you may have had.

 

[ron7000]

these updates i have not done:
the 2 optional are KB3118401 and KB3121255.
would not surprise me if win7 updates make win7 worse to encourage people to migrate to win10.

 

[UsernameIssues]

Stop saving files to the root of the C: drive, there I said.

We are not tyros here; so we are not talking about saving a letter we wrote to Aunt Matilda. I like to write a short note on the root of every partition (I have about 16 of them, with various OS's on them) saying what partition it is - you know, like "SATA 3 80Gb drive, 3rd Primary". This is because Windows in particular tries to confuse us by inconsistent drive lettering depending which version I boot.

There are a few ways to make this task easier. You can create a shortcut to notepad (or your favorite editor). Modify that shortcut to run as admin. When you want to add/edit files in the root (or other protected areas), open the editor with that shortcut.

I keep several text files in the root of lots of computers. Things like batch files that set static IPs to the computer or restart the computer or disconnect an RDP session while leaving the remote computer unlocked. I have to edit those from time to time. It is easy to edit them from a different computer that is connected via the admin share. That way, my text editor (or script) does not have to run as admin on my local computer.

Do you think you have access to the system directories on Unix/Linux even with an Admin account? No you do not! That is were the "root" account comes into play.

I am not convinced you know what you are talking about. You can always name an account in Linux as "Admin" but there will be nothing special about it. The Linux equivalent of the Windows "Administrator" is "root". If you log in to the Linux "root" account you can write, delete and edit whatever you want, including writing to the root directory (equivalent to the Windows C:\) which in my case is in its own partition. Perhaps you have only experienced a dumbed-down version of Linux, like Zorin or Ubuntu? I just tried it, successfully, in Debian, as you sounded so convincing.

In fact one solution to the problem of writing to the Windows C:\ would be to boot Linux (maybe from a live disk) and do it from there.

In Windows 7, by default, members* of the group named Administrators normally start apps as if they are not an administrator [e.g. the apps are not using an admin security token]. A user logged on with an account* that is in the group named Administrators will still need to tell the operating system to start an app with admin rights.

*except the built in user account named Administrator.


By default, the built in user account named Administrator is disabled. If you enable and log on to that account**, then most apps that you start (and most infections) can write to protected file areas like the root, program files, windows and other folders without taking the extra step to elevate the editor to the admin level.

You can rename the built in user account named Administrator to any name that you wish. If you rename it before using it, then the user profile folder name will agree with the new name.


**I would not recommend enabling and using that account. You are better off learning why things work the way that they do and leaving the various Windows security models in place.

 

[Daniapp]

How to fix Cannot save files to drive C in Windows 7

maybe you can see in my article how to fix Can not save files to drive C in Windows 7
https://goo.gl/NzSR1c