Access denied for newly created folder, unable to change permissions

1

I just created a new folder: C:\Projects\API from the Command Prompt, using mkdir API from within the projects folder, after deleting an old folder of the same name, using: RMDIR API /S.

I then attempted to access the API folder from the same Command Prompt window, which resulted in the error:

Access is denied.

I closed down the Command Prompt window and reopened as administrator. Same issue.

I then opened Windows Explorer, right-clicked on the folder and selected Project Properties, followed by Security. The linked screen appeared:

No permissions

Showing no permissions. When I click the Advanced button, I see a screen:

No permissions

When I click either the Change button, to change ownership, or the Continue button, I get a third screen, saying:

You do not have permission to view or edit this object's permission settings.

The Master Priest

Posted 2016-11-07T14:02:53.030

Reputation: 13

1Have you tried rebooting yet? Disk checks? – Ƭᴇcʜιᴇ007 – 2016-11-07T14:35:23.267

I haven't tried rebooting. I was hoping to avoid this if possible, as my computer is very slow to start and I have a lot of things I'm running at the same time. What sort of disk checks would you recommend? – The Master Priest – 2016-11-07T14:36:32.763

Answers

1

It isn't uncommon to see people encounter issues with permissions when they create a new folder hierarchy at the root of the operating system partition. Have you considered utilizing the Public profile folder hierarchy, instead?

That being said, it may be wise to delete the empty API folder and double-check the NTFS permissions on the C:\Projects folder before you attempt to recreate it.

Are you running Version 1607 (a.k.a. the Anniversary Update)? If so, you can utilize the Windows Subsystem for Linux bash shell to easily delete that folder. Once you have the bash shell enabled, navigate to the location of the folder and use the command rm -r [folder] to delete it.

Run5k

Posted 2016-11-07T14:02:53.030

Reputation: 13 092

Windows Bash starts and quits immediately after starting, which is a known issue. Still looking into the problem and may raise a further issue. Standard Microsoft workaround does nothing. – The Master Priest – 2016-11-07T20:36:44.480

That is unfortunate, and definitely an issue that I haven't encountered first-hand just yet. If necessary, you can always reboot your computer using a Linux Live distro image and delete the folder(s) without being hampered by Windows permissions. – Run5k – 2016-11-07T21:14:29.693

After a second restart trying to get Windows Bash to work, I remembered I have Git Bash on my computer. Upon navigating to the file area in Git Bash I found the folder has disappeared: it appears during the process of the second restart the system has cleared the folder away itself. I have accepted your answer as it has been helpful in solving the problem, and clued me in as to what to do next time if the same issue reoccurs. – The Master Priest – 2016-11-08T10:01:21.270

Glad to hear that everything is back to normal. – Run5k – 2016-11-08T13:31:02.657