question

Elroy-1144 avatar image
0 Votes"
Elroy-1144 asked MotoX80 commented

Error launching executable: "The requested operation requires elevation"

We're running 32-bit Windows 10 build 1909 on some of our test computers. When we launch an application that was developed in-house, we see an error message, "The requested operation requires elevation".

We're logged-in with administrative context and we have tried taking ownership of our application folder & files. We still see the prompt when we double-click the shortcut or executable.

We have tried turning-off UAC, that didn't help.

If we Right-click the shortcut and click "Run as administrator" the application works properly.

The problem is that we need this application to run for standard (non-admin) users. What do we need to change to make the "elevation required" message stop?

Thanks for reading!

windows-10-generalwindows-10-security
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

cooldadtx avatar image
1 Vote"
cooldadtx answered

Couple of things that could cause this beyond what you already mentioned.

  • Does the application have a manifest file that specifies it requires elevation? If so then adjust or remove the manifest file from your project and rebuild.

  • Is it running in compatibility mode? If so then remove the compatibility settings on the exe/shortcut.

  • Is the exe/shortcut properties configured to require an administrator? If so then remove that setting from the exe/shortcut.



5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Elroy-1144 avatar image
0 Votes"
Elroy-1144 answered

Thanks for your reply! It is not running in compatibility mode, I know we checked that... I don't believe that the file/shortcut properties are configured to require an administrator, we checked properties and I don't recall seeing anything like that but I will re-check.

I will check with the developer to see whether there is a manifest file.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MotoX80 avatar image
0 Votes"
MotoX80 answered

What IDE/compiler is he using? I would expect there to be an elevation setting in the project settings.

What API calls is his code making? Is he doing something that requires admin access?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

LimitlessTechnology-2700 avatar image
0 Votes"
LimitlessTechnology-2700 answered

Hi there,

When Windows can't recognize the security identifier associated with the file ACLs (Access Control List / Permissions) it displays the SID. Normally Windows will be able to translate that SID into an account name or alias, such as 'DOMAIN\Username'. So makes sure that your exe file can fetch the required details from the Users or the app manifesto.



If the reply is helpful, please Upvote and Accept it as an answer

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Igor-3117 avatar image
0 Votes"
Igor-3117 answered MotoX80 commented

Hello, I work with Elroy-1144. Thank you everyone for your suggestions. I ended up doing what @cooldadtx suggested but in reverse. Our application did not use a manifest file. After adding this file and rebuilding this C# app using VS2019 it solved the issue. The small shield right above the .exe app that was visible on some of the racks is no longer there. This is still strange since this issue was only happening on some racks.

On 32bit machines we are still not able to see compatibility tab when right clicking on the app and going to properties. Would anyone know why this might be happening?

Thanks.

· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

On an executable it should always be there. The cases I know of when it wouldn't be:

  • Not an exe

  • Group policies have disabled compatibility mode (this is easy to see though as none of the executables would have the option)

I've also heard of people sometimes seeing this problem on really old versions of Windows 10 Home before the Windows updates were applied but I haven't seen it myself.

0 Votes 0 ·

Thank you cooldadtx. Sounds like our issue might be some sort of a glitch from when Windows 7 was upgraded to Windows 10.

0 Votes 0 ·

this issue was only happening on some racks.

Are you referring to a physical rack in a datacenter where groups of servers are mounted? What OS's are the machines in the rack running?

On 32bit machines we are still not able to see compatibility tab when right clicking on the app and going to properties.

Does the program work on those machines? If so, then you have no need to mess with any compatibility settings.








0 Votes 0 ·

We refer to them as racks because our PCs have additional equipment. You can think of them as regular PCs that are scattered across our building.

The app works now after an update. It's just odd that 32bit PCs don't have compatibility tab and 64bit PCs do have it. This tab is nice to have in case any issues come up in the future. Have it and not need it :).

Thanks.

0 Votes 0 ·

I've never had much luck using compatibility settings over the years.

0 Votes 0 ·