Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.
One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.
Windows 7 C: drive permissions - file copy problem
So with Windows 7, it appears that even a local administrator user account can't copy data to the root of the C: drive...without giving explicit "run" rights as an administrator (when I try to copy something to the root C: I get a window that says "denied" and that I need to provide administrator permissions to copy this file). However, I have a few mapped network drives from our file server, and if I try to copy a word document (for example) to my root C: from a mapped network drive, I gives me the following error:
Location is not available
P:\ refers to a location that is unavailable. It could be on a hard drive on this computer, or on a network. Check to make sure that the disk is properly inserted, or that you are connected to the Internet or your network, and then try again...
But, I am connected properly...and the network drive is still there. I can copy files from the network drive to my desktop (for example) without any problem. Why is this happening and how do I "fix" it?
Location is not available
P:\ refers to a location that is unavailable. It could be on a hard drive on this computer, or on a network. Check to make sure that the disk is properly inserted, or that you are connected to the Internet or your network, and then try again...
But, I am connected properly...and the network drive is still there. I can copy files from the network drive to my desktop (for example) without any problem. Why is this happening and how do I "fix" it?
Asked:
-
2
2 Solutions
LVL 1
UPDATE: so instead of trying to copy a file from the mapped drive letter in windows explorer, I instead opened a window to the same location on the file server, but used a UNC path (\\servername\sharename). When I copied the file this way, it worked?! What is the difference here???
It might be User Access Control (UAC) issue
Put below code in batch file and run on your machine with elevated command prompt
then reboot your computer and check.The code will disable all UAC on your computer.
reg add HKLM\SOFTWARE\Microsoft\Wi
reg add HKLM\SOFTWARE\Microsoft\Wi
reg add HKLM\SOFTWARE\Microsoft\Wi
reg add HKLM\SOFTWARE\Microsoft\Wi
reg add HKLM\SOFTWARE\Microsoft\Wi
reg add HKLM\SOFTWARE\Microsoft\Wi
reg add HKLM\SOFTWARE\Microsoft\Wi
reg add HKLM\SOFTWARE\Microsoft\Wi
Alternatively, you can disable UAC through control panel \ user accounts \ user account settings
But batch file worked than control panel method for me most of the time.
Thanks
Put below code in batch file and run on your machine with elevated command prompt
then reboot your computer and check.The code will disable all UAC on your computer.
reg add HKLM\SOFTWARE\Microsoft\Wi
reg add HKLM\SOFTWARE\Microsoft\Wi
reg add HKLM\SOFTWARE\Microsoft\Wi
reg add HKLM\SOFTWARE\Microsoft\Wi
reg add HKLM\SOFTWARE\Microsoft\Wi
reg add HKLM\SOFTWARE\Microsoft\Wi
reg add HKLM\SOFTWARE\Microsoft\Wi
reg add HKLM\SOFTWARE\Microsoft\Wi
Alternatively, you can disable UAC through control panel \ user accounts \ user account settings
But batch file worked than control panel method for me most of the time.
Thanks
I don't necessarily want to disable UAC, and additionally, there could be some policies being pushed down from the domain server about this. I am just trying to figure out why this behavior happens. I can always copy the file to my desktop, then from my desktop, copy it to the root C: drive, or as my update mentioned, I can just use the UNC method. It just doesn't make sense.
i totally understand the issue...all about UAC and access tokens
when you are elevated, the drive mappings don't exist so that's why it give that error
if you run a command prompt and do net use you will see the drive mappings
if you run elevated command prompt and to net use you don't see the drive mappings
this explains it a bit more
Programs may be unable to access some network locations after you turn on User Account Control in Windows Vista or newer operating systems
http://support.microsoft.com/kb/937624
when you are elevated, the drive mappings don't exist so that's why it give that error
if you run a command prompt and do net use you will see the drive mappings
if you run elevated command prompt and to net use you don't see the drive mappings
this explains it a bit more
Programs may be unable to access some network locations after you turn on User Account Control in Windows Vista or newer operating systems
http://support.microsoft.com/kb/937624
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Tackle projects and never again get stuck behind a technical roadblock.
Join Now