Product, version and build: 5.8.188
Operating system: Windows Server 2019
PowerShell version(s): 5.1
Hi,
I created a package form app that run well except for one issue. When I use alternate credentials to run my app as administrator, the UI change and use the "old" apparence. Take a look in attachments.
Any idea? Thanks.
Old UI when package is runas admintrator
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
-
- Posts: 3
- Last visit: Thu Feb 08, 2024 8:37 am
Old UI when package is runas admintrator
- Attachments
-
- NormalUI.png (17.92 KiB) Viewed 6020 times
-
- WrongUI.png (26.86 KiB) Viewed 6020 times
Re: Old UI when package is runas admintrator
Does this happen for any WinForm packaged script ran under those credentials?
What script engine are you using to package?
What script engine are you using to package?
Brittney
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
- Alexander Riedel
- Posts: 8488
- Last visit: Tue Apr 16, 2024 8:42 am
- Been upvoted: 37 times
Re: Old UI when package is runas admintrator
We are able to replicate the problem. Windows Forms seems to ignore all settings about Visual Styles when executing under a different user account. Elevation is not affected, so the problems seems to be located with using a different security context. We are investigating if there is a work around.
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.