0

When I install my application using the setup executable (generated using NSIS) on certain computers a particular DLL does not get the ACL for the the local Users group in its security permissions. The result is that loading the DLL in question only works for administrators.

It is always the same DLL that is affected. All the other DLLs install perfectly. The DLL is properly signed.

The DACL for a DLL usually contains these entries:

  • SYSTEM
  • John Doh (john@doe.local)
  • Administrators (PC-NAME\Administrators)
  • User (PC-NAME\Users) --- this one is missing on the affected DLL

What could cause this, and how can I fix it?

Harry Johnston
  • 35,639
  • 6
  • 68
  • 158
KungPhoo
  • 516
  • 4
  • 18
  • 1
    Please provide some more information. What is so special about this DLL, where did you get it from and what is its name? Does it happen on all versions of Windows? Which directory are you installing to? – Anders Feb 25 '16 at 13:13

1 Answers1

0

I think I found it. The local user installs the program using the administrator account, but some dll is locked. After a reboot, the dll is getting overwritten, but now the rights for the local user(s) are missing!

KungPhoo
  • 516
  • 4
  • 18