• otacon239@feddit.de
    link
    fedilink
    arrow-up
    63
    ·
    2 months ago

    Don’t forget about the hidden ProgramData directory at the root of the file system. Ableton Live likes to install there for some ungodly reason.

    • 0x4E4F@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      15
      ·
      edit-2
      2 months ago

      Always remember, C:\ProgramData is the eqivalent of /etc in Linux. If they don’t know where to put/hide shit, but needs admin priviliges to edit and users can only read, you put it in C:\ProgramData.

      • Hawke@lemmy.world
        link
        fedilink
        arrow-up
        13
        ·
        edit-2
        2 months ago

        I think programdata is closer to /usr/lib or maybe /var/lib.

        You almost never see config files in programdata.

        • 0x4E4F@sh.itjust.worksOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          2 months ago

          Config files that are meant to be used as sane defaults for new user accounts, yes. Config files that are meant to be manually edited, no.

          Besides, there are a lot of examples of configs that are saved in ProgramData, like, let’s say, registration info for proprietery programs (of course, this info needs to be shared amongst users, so your safest bet is ProgramData). Hidden by default, makes it perfect for storing everything the program is trying to hide from the user.

    • Morphit @feddit.uk
      link
      fedilink
      arrow-up
      4
      ·
      2 months ago

      Don’t forget that there’s a hidden system junction at C:\ProgramData\Application Data that points to C:\ProgramData. Because everyone loves loops in their filesystem. Of course C:\Users\All Users is also a junction to C:\ProgramData. This kills updatedb in WSL.