cannot write to c drive on windows 7 pro

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

No user should be able to write to the root of C:\ or to any other system reserved directories. He should normally only be able to write into directories within his profile or the public folder, both within the \Users\ Folder. So what you are seeing is absolutely normal. If he was previously able to write directly into C:\ something was wrong then, or he was using an account with admin rights. No user should use a PC as Admin, the admin account should only be used for very special reasons, and if possible via UAC, and not logged on directly as it.

I can make a folder in root of c: (say C:\General Storage) and write to it without special permissions. You may not agree with my approach, but so long as the folder is not in Windows or Program Files, you should be able to write to it.

in this case, it was the change that makes me think something has gone wrong.

I can also create a directory, but I can't write any files directly into C:\. Not with a standard user account.

ASKER

This user was an admin and had been writing to the C: drive for years. We are thinking he did a Windows Update this week, and now those permissions are gone. All of our other Admin users have been writing to C: for years and none of us have run into this problem before. All of the reports in our software package write the PDF report to the C: and then the user can choose to print it, email it, or save it to another directory. This is the first time any user has reported a problem.

Recent updates have had no impact on permissions on a machine that is working properly. As noted, check for viruses and root kit viruses.

ASKER

John, we ran the TDS Killer and it came up clean. When we try to run SFC, it gives us the message "Must be an administrator running a console session to use the SFC utility." I have someone trying to figure out how to get around that setback now.

On this machine, log out, and log in as an administrator - either local admin or server admin. Then run SFC again. It should run, and if not, something has compromised the machine.

It is still wrong for anyone to be allowed to write into the root of C:\, and allow users to logon as an Admin as a standard course of action. You can give him the password to an Admin account if necessary, but that must only be used when absolutely necessary. Even I who am the Admin and only user of my PC's login as a standard user. I also don't see any reason why a file has to be saved into the root of C:\. You can save it elsewhere, and also print it from there. If your software saves it to C:\ then it isn't setup properly or working as it should. But of course that is my point of view my point of view (and that of normal admins).

You don't need to logon as an admin to run sfc /scannow, just open a CMD prompt with admin privileges (right click on cmd.exe and select "Run as Administrator").

ASKER

rindi, If I was running a traditional network, I couldn't agree with you more. Our sales force are "independent" contractors that are required to purchase their own computers and in many cases work out of their homes. (So most are configured as Admin) The legacy software we use writes to the C: and then the user is free to move the PDF reports on their machine. In 17 years, this is the first time we have had a machine stop letting us write to the C:. I don't want to argue the merits of how we do it, but I am just supposed to fix it. I am sure you understand.

ASKER

Ok, we ran the sfc as administrator, and now it states:
Windows Resource Protection found corrupt files but was unable to fix some of them. Details included in CBS.log

We can see the log file, but we can't open it or copy due to "invalid privileges" since we are "not" an administrator. Thanks for all of your help on a busy Friday for a guy who can't seem to help himself.

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Also, try running Windows Repair Install as suggested earlier. Support thread back there as well.

ASKER

THANK YOU THANK YOU

Even though we could not read the CBS.log file, the user rebooted his computer. When his computer came back up, he can now write to the C: again. (whether that is right or wrong).

Thank you John and rindi for sticking with me today.

ASKER

I am really new to this stuff but John Hurst and rindi were awesome!!