I have a workstation running Windows Server 2008 that's logged into an AD domain, and I have a dual boot with Ubuntu Linux. When running Linux, I'd like to be able to use the same Thunderbird profile I use under Windows, so I pointed Thunderbird to use a profile I found under:

\Users\(myname)\AppData\Local\Thunderbird\Profiles

It turns out it was not the correct profile -- it had the right configuration, but the Inbox was an old version. I eventually found out the correct path was:

\Users\(myname)\AppData\Roaming\Thunderbird\Profiles

What's the rationale behind those different places to store application data?

up vote 160 down vote accepted

Roaming is the folder that would be synchronized with a server if you logged into a domain with a roaming profile (enabling you to log into any computer in a domain and access your favorites, documents, etc. Firefox stores its information here, so you could even have the same bookmarks between computers with a roaming profile.

Local is the folder that is specific to that computer - any information here would not be synchronized with a server. This folder is equivalent in Windows XP to C:\Documents and Settings\User\Local Settings\Application Data.

LocalLow is the same folder as local, but it has a lower integrity level. For example, Internet Explorer 8 can only write to the LocalLow folder (when protected mode is on).

This document from Microsoft ("Managing Roaming User Data Deployment Guide") has a long explanation for what these three folder areas are and how they are used, as well as the changes implemented between Windows XP and Vista (Windows 7 retains the Vista structure).

  • 2
    As for Thunderbird, the TB profile should actually live in Roaming but the cache of downloaded mails, at least for IMAP accounts definitely should be elsewhere. If I were in a domain here, there'd be a lot of copying going on on each logon/-off with 1+ GiB of mails. – Joey Aug 11 '09 at 21:56
  • 1
    I guess the choice of Local* bs Roaming is the app developer's choice? – Howiecamp Dec 28 '09 at 0:08
  • 4
    This link from Microsoft (same as above, but not a doc) has a good explanation of folders, what is used where, and relationship to folders in XP. – mindless.panda Aug 24 '11 at 14:33
  • 1
    @Howiecamp, yes, this link details the SpecialFolders enumeration for .NET 4.0. Developers choose which folder to save data to, in this case either ApplicationData or LocalApplicationData. – mindless.panda Aug 24 '11 at 14:35
  • 6
    What is lower integrity level w.r.t any application or internet explorer for that matter? – RBT Feb 23 '17 at 1:50

Roaming: This folder (%appdata%) contains data that can move with your user profile from PC to PC—like when you’re on a domain—because this data can be synced with a server. For example, if you sign in to a different PC on a domain, your web browser favorites or bookmarks will be available.

Local: This folder (%localappdata%) contains data that can't move with your user profile. This data is typically specific to a PC or too large to sync with a server. For example, web browsers usually store their temporary files here.

LocalLow: This folder (%appdata%/../LocalLow) contains data that can't move, but also has a lower level of access. For example, if you're running a web browser in a protected or safe mode, the app will only be able access data from the LocalLow folder.

The apps themselves choose whether to save to the Local, LocalLow, or Roaming folders. Most desktop apps use the Roaming folder by default, while most Windows Store apps use the Local folder by default.

  • This is a very underrated answer. – Hashim Oct 29 at 23:45

As explained in this blog post, The LocalLow folder (and several other Low folders) are created as an extra level of security for programs that are frequently under attack because they are exposed to the web. Internet Explorer and Adobe Acrobat are two prime examples on my system.

Essentially, a program that knows it is vulnerable can start itself in in "low" access mode so that it can only write into those folders and not infect the rest of the hard drive.

  • 1
    Could you please explain what is wrong with this answer? – Josiah Yoder Jul 18 at 14:38

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.