We are preparing to move to Windows 10, and one application, which works fine on Windows 7, does not behave correctly in a normal user session. The application is no longer supported by the vendor, so we have no escalation path for support.
We can get the application to behave correctly by using [Run as different user], and re-entering the same credentials as the current user's session. Using the RUNAS command line also works.
Neither [Run as Administrator], nor logging on as a local administrator, resolves the issue, so this doesn't seem to be a Windows permissions issue (I'm yet to be convinced this is a UAC issue).
As the app currently is called from a script, we are OK with using the command line, but don't want the user to need to re-enter their password unnecessarily.
To troubleshoot, I tried to use ProcMon, and found nothing obvious.
My questions are:
How does Windows treat [Run as different user]/RUNAS.exe differently from the current session, so we can try to emulate it?
Is there a local security item which I can do to emulate the above?
What other methods can I use to troubleshoot the exact issue?
TL:DR Damn you Windows 10, allow my app to work!