# Sorry you must provide a path in C:\\Users

**URL:** <https://community.localwp.com/t/sorry-you-must-provide-a-path-in-c-users/25000>\
**Category:** Feature requests\
**Created:** [March 28, 2021, 2:34am UTC](https://community.localwp.com/t/sorry-you-must-provide-a-path-in-c-users/25000 "2021-03-28T02:34:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rastographics](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/rastographics/32/11302_2.png) [@rastographics](https://community.localwp.com/u/rastographics)\
**Post date:** [March 28, 2021, 2:34am UTC](https://community.localwp.com/t/sorry-you-must-provide-a-path-in-c-users/25000/1 "2021-03-28T02:34:46Z")

</div>

Is there a valid reason why this is a thing? (forcing user to only use C:\Users)

![2021-03-27 21_27_17-Window](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/2X/7/775827c8e8a538a054ab60865f8944d3c0c882bd.png)

All of my repos are setup already in another subfolder on my C drive. Why does local force us into Users folder?  
If this reason is still not valid, could the restriction be removed? thanks!

---

<div class="post-metadata">

**Author:** ![rastographics](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/rastographics/32/11302_2.png) [@rastographics](https://community.localwp.com/u/rastographics)\
**Post date:** [October 19, 2021, 3:14pm UTC](https://community.localwp.com/t/sorry-you-must-provide-a-path-in-c-users/25000/4 "2021-10-19T15:14:56Z")

</div>

Hi! This seems like a bug with not allowing the user to choose where to store the site files. Is there some more information I could provide that would help with providing a fix for this?

---

<div class="post-metadata">

**Author:** ![ben.turner](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/ben.turner/32/5366_2.png) [@ben.turner](https://community.localwp.com/u/ben.turner)\
**Post date:** [November 17, 2021, 8:22pm UTC](https://community.localwp.com/t/sorry-you-must-provide-a-path-in-c-users/25000/5 "2021-11-17T20:22:30Z")

</div>

I think that this would 100% be a bug if Local indicated that you could create a folder somewhere outside of `C:\Users` but then failed to do so.

My thinking of putting it in the Feature Request category was that Local is clearly telling you that you can’t have the files in a place outside the `C:\Users` folder or on another drive, so the app is working as intended. Changing this behavior isn’t really fixing a bug, it involves reworking how Local works in order to do something new.

I’m not 100% sure of the reason for that requirement, but if I were to guess, it’s likely a limitation of Windows permissions and the way that Electron (the framework that Local is built on) works. I’ve created a ticket for one of the Local engineers to take a closer look, but I don’t really have an ETA for when it will be worked on since there aren’t any votes on this and it doesn’t seem to be a high priority for the community.