Windows 10: An app with <requestedExecutionLevel level="asInvoker" uiAccess="true"/> in manifest fails...

I have a custom app with <requestedExecutionLevel level="asInvoker" uiAccess="true"/> in its manifest. It is signed with a self-issued certificate and installed in Program Files. It works without problems in 23H2, but raises "A referral was returned from the server" in 24H2 under the same conditions. I've tried everything possible, including group policies and disabling UAC, nothing helps to mitigate this error. Windows is unusable for me without this app. Is it a bug? Is it possible to escalate? I've heard about enhanced admin protection in 24H2, is this error somehow connected to this

:)

 

Visual Studio 2010 Installer Project

I resolved the issue. The program always needs to be run as administrator.

Visual Studio 2010 ( and probably Visual Studio 2008 ):Under the Application tab of the project properties, you have to click "Application Settings" to access the App.Manifest file. Pretty close to the top you find this:

Changing that last line to <requestedExecutionLevel level="requireAdministrator" uiAccess="false" /> solved my problem and created a new one.

NOW it threw the error:

Disabling Click Once security under the security tab of the projects properties took care of this. Now there is a prompt for elevation when the program starts. If there is a way around this anyone knows of besides disabling UAC all together, I'd love to know.

Thanks for all your help guys.

 

0xc0000142 error when launching epic games launcher

I mean, undo the steps you followed in the tutorial you were referring to.

//After following a tutorial linked in the forum, I would get the 0xc0000124//

EpicGamesLauncher.exe has the following inbuilt manifest. It already runs as "asInvoker".

<ms_asmv2:trustInfo xmlns:ms_asmv2="urn:schemas-microsoft-com:asm.v2">

<ms_asmv2:security>

<ms_asmv2:requestedPrivileges>

<ms_asmv2:requestedExecutionLevel level="asInvoker" uiAccess="false" />

</ms_asmv2:requestedPrivileges>

</ms_asmv2:security>

</ms_asmv2:trustInfo>

Once done, run the Farbar Scanner and share the logs here.

• Download Farbar Recovery Scan Tool (FRST64.exe) [See also: Collect Farbar Recovery Scan Tool logs.]
  
• Rename FRST64.exe to EnglishFRST64.exe.
  
• Run the program. Don't check or uncheck any options. Click "Scan".
  
• Upload the two logs, FRST.txt and Addition.txt, to your OneDrive and share the link here.
  

 

Date format change in 1703 update?

There is a twist break without you being the programmer.

You can create a file "ApplicationName.exe.manifest" containing the data that I will pass below.

<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">

<assemblyIdentity

type="win32"

name="CodeGear RAD Studio"

version="12.0.3420.21218"

processorArchitecture="*"/>

<dependency>

<dependentAssembly>

<assemblyIdentity

type="win32"

name="Microsoft.Windows.Common-Controls"

version="6.0.0.0"

publicKeyToken="6595b64144ccf1df"

language="*"

processorArchitecture="*"/>

</dependentAssembly>

</dependency>

<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">

<security>

<requestedPrivileges>

<requestedExecutionLevel

level="asInvoker"

uiAccess="false"/>

</requestedPrivileges>

</security>

</trustInfo>

</assembly>

If it does not work try renaming the name of your application and the name of the manifest, for example.

ApplicationNameTeste1.exe The manifest has to be ApplicationNameTeste1.exe.manifest