you are viewing a single comment's thread
view the rest of the comments
[–] 85 points 2 months ago* (last edited 2 months ago) (12 children)

Y'all joke, but when that 'task' is run through process monitor, we see it's trying to overwrite a DLL in system32, create a directory at root of %systemdrive% or cache some data in the Program Files application itself, instead of utilizing ProgramData or Appdata properly.

When applications fail these simple practices and demand local admin, they shouldn't touch your network.

<3

  • source
  • hideshow 12 child comments
  • [–] 17 points 2 months ago (4 children)

    LUA Buglight is also good for documenting why a program needs admin when it shouldn't.

    After that, you just write an admin shim with the app compatibility toolkit and just add write perms to the necessary folders.
    ...Unless it's system32. Then your software request can die in a fire, and I'm forwarding the info to your boss (and mine) before you can complain to them.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 2 months ago (3 children)

    Can you please explain to the laity what the problem with System32 is? So we know why to avoid it

  • source
  • parent
  • hideshow 3 child comments
  • [–] 4 points 2 months ago (2 children)

    It is the beating heart of Windows itself, the nuclear reactor at the heart of the facility. And much like with a nuclear reactor, you don't screw around in the core unless you have a damn good reason.
    Doing so at random is a good way to make both go kaboom.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 24 points 2 months ago (5 children)

    As an insane person who moved all my folders to the D drive, it’s absurd how many big companies hard code C:\Users\you\AppData\Roaming

  • source
  • parent
  • hideshow 5 child comments
  • [–] 3 points 2 months ago

    The hardcoded AppData path is the main reason I had to spring for a larger system drive a few years ago despite not installing any programs to it. Gradle/NuGet/every other package manager were the main culprits, with Microsoft themselves coming second. Every few months I'd clear out their caches and "temporary" file folders and it'd free up tens of gigabytes.

    I'd mess around with symbolic links to move it to another drive if I didn't half-expect Windows to break them at some point.

  • source
  • parent