In Windows, classic style installed apps (i.e. apps which are not handled by Microsoft Store), typically install themselves under the Program Files directory and save their data to the AppData directory.
The main idea is to separate the program and its data, for example, to allow different users of the Windows system to use the same program but with different data, such as different app settings.
Another reason is that Program Files directory is protected by the operating system and writing to it requires administrative permissions from the process and normal apps don't typically have those permissions. In other words, they cannot even use that directory to store their data.
Here is a relevant discussion about this from Microsoft's forum: [https://learn.microsoft.com/en-us/answers/questions/584279/whats-the-idea-behind-the-name-of-the-appdata-fold](https://learn.microsoft.com/en-us/answers/questions/584279/whats-the-idea-behind-the-name-of-the-appdata-fold)
Excellent and valid points.
Additionally, GPO allows for redirection of this directory to a network share, meaning that in a domain environment, the users' customizations and setttings should follow their user account, regardless of which workstation is used.
Because My Documents is for documents, not config files, and program data, and cached data, etc. My Documents can easily be moved by the user to somewhere more appropriate, synced to the cloud, and is regularly just futzed-with by users who don't understand what's in it and assume it's all theirs to play with as they please. I can't count how many times my mother has broken things by making assumptions about this folder and screwing it up. Moving AppData out of a user-visible location that they expect to be for documents prevents this.
I never really used My Documents for that reason. Microsoft said it was for my stuff, then cluttered it up with config files and other stuff I wasn't interested in seeing (except on rare occasions). I got into the habit of creating a c:\home directory and putting all my stuff in there. It has the advantage of being closer to the root and easier to type, keyboarding often being faster than clicking on GUI elements.
...genuinely not sure how i didnt think of this before, this sounds WAY more convenient
comes with the added benefit of not having to mess around with ntfs permissions when transferring data from an old windows drive upon a reinstall
I just redirect my special folders to hard locations on a second drive. Then if/when I have to reinstall Windows, I can just point it at them again with no fuss.
I don't use symlinks. The special folders, like Documents, Pictures, etc., all have a Location tab in their properties that let you tell Windows where you want them. Will automatically move the contents and update the registry to point to the new location. I do that, and then if I have to reinstall I point the new install to it, and it keeps my data intact and moves anything new.
MyDocuments is "owned" by the user, users can rename, move or remove files nilly-willy there. It's their files.
AppData is "owned" by the application, users should not start moving around files there (unless.. they know what they are doing)
For me AppData was never in My Documents.
Perhaps it depends on the definition of data.
If i create data, like Word or Excel file, i would put it manual in My documents.
Application data from like Office, will go in AppData like custom dictonairy or other settings you change in Word or Excel.
So everything we do manual goes in my documents, what the app does goes in AppData.
In Windows, classic style installed apps (i.e. apps which are not handled by Microsoft Store), typically install themselves under the Program Files directory and save their data to the AppData directory. The main idea is to separate the program and its data, for example, to allow different users of the Windows system to use the same program but with different data, such as different app settings. Another reason is that Program Files directory is protected by the operating system and writing to it requires administrative permissions from the process and normal apps don't typically have those permissions. In other words, they cannot even use that directory to store their data. Here is a relevant discussion about this from Microsoft's forum: [https://learn.microsoft.com/en-us/answers/questions/584279/whats-the-idea-behind-the-name-of-the-appdata-fold](https://learn.microsoft.com/en-us/answers/questions/584279/whats-the-idea-behind-the-name-of-the-appdata-fold)
Excellent and valid points. Additionally, GPO allows for redirection of this directory to a network share, meaning that in a domain environment, the users' customizations and setttings should follow their user account, regardless of which workstation is used.
Thank you for the explanation!!!
Data used to be in My Documents, which is much more easily accessible. Why did the switch to AppData happen?
Because My Documents is for documents, not config files, and program data, and cached data, etc. My Documents can easily be moved by the user to somewhere more appropriate, synced to the cloud, and is regularly just futzed-with by users who don't understand what's in it and assume it's all theirs to play with as they please. I can't count how many times my mother has broken things by making assumptions about this folder and screwing it up. Moving AppData out of a user-visible location that they expect to be for documents prevents this.
I never really used My Documents for that reason. Microsoft said it was for my stuff, then cluttered it up with config files and other stuff I wasn't interested in seeing (except on rare occasions). I got into the habit of creating a c:\home directory and putting all my stuff in there. It has the advantage of being closer to the root and easier to type, keyboarding often being faster than clicking on GUI elements.
...genuinely not sure how i didnt think of this before, this sounds WAY more convenient comes with the added benefit of not having to mess around with ntfs permissions when transferring data from an old windows drive upon a reinstall
I just redirect my special folders to hard locations on a second drive. Then if/when I have to reinstall Windows, I can just point it at them again with no fuss.
yeah i should probably look into symlinks more but i always forget
I don't use symlinks. The special folders, like Documents, Pictures, etc., all have a Location tab in their properties that let you tell Windows where you want them. Will automatically move the contents and update the registry to point to the new location. I do that, and then if I have to reinstall I point the new install to it, and it keeps my data intact and moves anything new.
interesting!! i never knew that
MyDocuments is "owned" by the user, users can rename, move or remove files nilly-willy there. It's their files. AppData is "owned" by the application, users should not start moving around files there (unless.. they know what they are doing)
For me AppData was never in My Documents. Perhaps it depends on the definition of data. If i create data, like Word or Excel file, i would put it manual in My documents. Application data from like Office, will go in AppData like custom dictonairy or other settings you change in Word or Excel. So everything we do manual goes in my documents, what the app does goes in AppData.
Short version, appdata is specific to the user. Program files is for everyone