I’m encountering a strange issue and hope someone can shed light on it.
I have an Inno Setup installer that creates application files in: C:\ProgramData\Company\SoftwareName. There are two executable files:
This second executable, named starter.exe, requires elevated permissions to launch.
If I:
According to Microsoft, if a manifest is present, the file should follow the manifest’s instructions rather than be evaluated based on heuristics (e.g., filename patterns like "installer," "update," "setup").
I managed to work around this by installing a Windows shim for the file using Compatibility Administrator, but I still don’t understand the underlying cause of this behavior.
Furthermore, this behavior isn’t consistent across all computers—only some. I read that the system might build an internal database to help evaluate executables for elevation.
Is there anything I can do to address this?
On Monday, October 28, 2024, 08:56:17, Wojtek wrote:
Is there anything I can do to address this?
Check the compatibility options on the executable – it looks like the "Run program as Administrator" compat option is set for that specific path.
I have an Inno Setup installer that creates application files in: C:\ProgramData\Company\SoftwareName. There are two executable files: