Windows 10: Forcing a program to run with standard privileges?

I have a program that has the elevated shield on its icon but when I run it, I get a window that says

Setup should not initially be run elevated. Run setup with standard privileges; it will elevate if needed.

I'm logged in as a user with Administrator rights. That's not going to change. Ho do I force this program to NOT launch elevated?

:)

 

Running Programs for a standard user

Hello

You mentioned checking the the box 'Run as Administrator'

This is the opposite of what I require ,I wanted to avoid running programs as admin . By unchecking 'Run As Administrator' I am still getting an admin credential verification prompt

Any further suggestions ?

 

Running Programs for a standard user

Hi,

Thank you for posting your query in Microsoft Community.

I understand your concern and will assist you to resolve this issue.

I suggest you to follow the steps below and check if it helps.

• 
  Right Click on the FL studio application shortcut.
  
• 
  Select properties.
  
• 
  Under shortcuts select advanced.
  
• 
  Check the box Run as administrator and check if it helps.
  

Hope this helps. If the issue remains unresolved, please get back to us and we would be happy to help.

 

Scheduled tasks run with elevated privileges can't access stored Windows credentials

It seems that after Creators update scheduled tasks run with elevated privileges ('run with highest privileges' option) can't access stored Windows credentials. Is that a bug or an intentional change and is there a recommended workaround?

Here's one way to reproduce the behaviour:

• Start Credential Manger and add some Windows share credentials.
• In a console window type 'cmdkey /list', which should list the added credentials
• Create a task in a task manager:
  • Trigger: on user logon
  • Action: run cmd.exe
  • Tick the 'run with highest privileges' option
• Reboot the machine and log in
• In the console window (let's call it 'console 1') opened from the scheduled task type 'cmdkey /list'. This most likely won't display the credentials added in step 1 and properly listed in step 2. ->
  This looks like a bug
• Now, without closing 'console 1' open another console window as an administrator (let's call it 'console 2') and type 'cmdkey /list'. This will properly list credentials added in step 1.
• Switch to 'console 1' and type 'cmdkey /list' again. This time the credentials are listed properly, unlike in step 5. It looks like an access to Windows credentials was somehow 'unlocked' by step 6.