Database Search

match allmatch any Look in all areasLook in current areas Check all datesPrevious dayPrevious 3 daysPrevious weekPrevious fortnightPrevious monthPrevious 2 monthsPrevious 3 monthsPrevious half-yearPrevious year

TechHome

• DirMake Error 1029 on Windows Server 2008 R2
• External Manifest with WinBatch
• Manifest Check
• Manifest Faqs
• UAC Manifest Setting Triggers 1129 Error

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

Manifest FAQs

 Keywords:  UI Access UIAccess TRUE FALSE @TRUE @FALSE Manifest Notes FAQ FAQs Code Signing Certificate MakeCert

---

Manifest Notes:

• Applications running at normal privilege levels are NOT allowed to communicate with (i.e. send messages to) applications running at higher privilege levels (e.g. the SendMessage API reports success but your message never reaches the target application running at a higher privilege).

• If your application needs to send messages to all applications, regardless of their privilege level:
  1. The uiAccess flag MUST be set to TRUE in your application's manifest.
  2. Your code MUST be digitally signed.
  3. Your application MUST reside in a trusted location (e.g. Windows, Program Files), otherwise the uiAccess flag is ignored. It will still run if they are not in one of these locations, but they will not receive the privilege. You can disable this security feature through the local security policy mmc snap-in.
• Regardless of the state of the uiAccess flag, your application will always be able to send messages/drive input to windows of applications running at privilege levels equal to or less than your own privilege level.

• The size of your manifest must be an exact multiple of 4 (i.e. if it is 253 bytes/characters, then you must pad the end of the manifest text with three spaces).

---

Code Signing Notes:

Can't afford to pay for a Code Signing Certificate? You can use makecert to create your own certificate and then add the cert to your trusted certificate store to run the code on your own machine. Reference: If your application does not have a digital signature and has uiAccess=true in its manifest, it will fail with "A referral was returned from the server."

NOTE: These instructions assume you have visual studio installed and are using a command prompt that has all the environment variables set to find SDK utilities such as makecert and signtool. If not, you will need to find these tools on your hard drive before running them.

1. Open an elevated command prompt
   • Click start
   • Find Cmd Shell or command prompt
   • Right-click, click Run As Administrator
2. Create a trusted root certificate
   • Browse to the folder that you wish to contain a copy of the certificate
   • In the command shell, execute the following commands:

          makecert -r -pe -n "CN=Test Certificate - For Internal Use Only" -ss PrivateCertStore testcert.cer
          
          certmgr.exe -add testcert.cer -s -r localMachine root
          

3. Sign your file
   • In the command shell, browse to the location of your exe
   • In the command shell, type:

     SignTool sign /v /s PrivateCertStore /n "Test Certificate - For Internal Use Only" /t http://timestamp.verisign.com/scripts/timestamp.dll APP.exe

     Where APP.exe is your application.

---

Article ID:   W17969

Filename:   Manifest Faqs.txt

File Created: 2013:01:14:13:09:52

Last Updated: 2013:01:14:13:09:52