2

I'm in the task to make a .manifest file, so Win7 does no bother me with the UAC because it is an unsigned app. (The app is old and wont be upgraded)

I've tried several ways from looking around the web, but it is not working

<?xml version="1.0" encoding="utf-8"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel level="asInvoker" />
      </requestedPrivileges>
    </security>
  </trustInfo>
</assembly>

I've have also looked at:

  • The Application Compatibility Toolkit (as this question recommends), but it is too cumbersome and did not solve the problem.
  • This question is similar, but ends solving the problem for that specific product (Crimson Editor)

Do you know how to craft the .manifest XML file so an unsigned app runs without warning?

Community
  • 1
Eduardo Molteni
  • 1,758

2 Answers2

1

As per my knowledge, In Vista, any app which does not have a manifest will not be elevated (but will be Virtualized). But running it will not invoke the secured desktop till you do "Run as Administrator".

The manifest you gave as an example will just make sure Vista knows that your app is Vista aware. "As Invoker" means that your app does not require Administrative Privileges. But till you make it "Require Administrator", it will NOT show the UAC Prompt. (I answered for Vista since I have worked n it. I think Windows 7 would behave similarly).

Ganesh R.
  • 5,259
0

You're really asking here for a hole in UAC. Such holes are normally plugged-in by Microsoft as soon as they're discovered ...
It looks to me like a much more lasting solution to just digitally sign this old executable.
Signing can be done on any existing executable, and does not require its re-linking or re-compiling or otherwise knowing anything special about it. Application-signing certificates only cost a few hundred bucks per year.

harrymc
  • 498,455