UAC - Showing fake Shield icon on the Exe
-
Hello , Even though my application does not have the manifest file,Vista shows shield icon over my exe. Initially I thought it was because of the Installer detection Techniques, such as: 1) Analyzing the Exe name, the OS identifies the required level of Execution. 2) Analyzing the binary content of the application, where the OS identifies the required level of execution. I copied the Exe to the desktop, but it did not put the shield icon over my exe. So I came to a conclusion that the above two scenarios are not the reason for this failure. Environment: Installed OS - Vista Business. Account - Administrator with UAC turned on. The Exe was displayed under Program Files directory. To run the application Admin Rights is not required. Is there a different scenario that we need to try inorder to remove the shield icon which is displayed over the exe file Note: Previously My application had manifest file, but now we have changed the Exe inorder to make it run in the standard user privilege. (Therefore we removed the manifest file) The funniest part was, even though it displays the shield icon, UAC prompt did not pop up, when i am trying to launch the Exe and therefore the Application launched without any problem. Is this a Vista bug? what can i do remove this shield icon. Would really appreciate your help. Thanks, WindowsPistha.
-
Hello , Even though my application does not have the manifest file,Vista shows shield icon over my exe. Initially I thought it was because of the Installer detection Techniques, such as: 1) Analyzing the Exe name, the OS identifies the required level of Execution. 2) Analyzing the binary content of the application, where the OS identifies the required level of execution. I copied the Exe to the desktop, but it did not put the shield icon over my exe. So I came to a conclusion that the above two scenarios are not the reason for this failure. Environment: Installed OS - Vista Business. Account - Administrator with UAC turned on. The Exe was displayed under Program Files directory. To run the application Admin Rights is not required. Is there a different scenario that we need to try inorder to remove the shield icon which is displayed over the exe file Note: Previously My application had manifest file, but now we have changed the Exe inorder to make it run in the standard user privilege. (Therefore we removed the manifest file) The funniest part was, even though it displays the shield icon, UAC prompt did not pop up, when i am trying to launch the Exe and therefore the Application launched without any problem. Is this a Vista bug? what can i do remove this shield icon. Would really appreciate your help. Thanks, WindowsPistha.
WindowsPistha wrote:
I copied the Exe to the desktop, but it did not put the shield icon over my exe
Do you have a standalone manifest file for it in the directory where it exists when it displays the shield? Even if the manifest does not exist in the executable as a resource, it should still look for one in the directory of the executable and use it if it fits. I've noticed those standalone manifests suffer from caching when you try to delete or remove one, the effect can linger even though the manifest no longer exists there. Various techniques to shake it loose like rebooting ultimately prevail but not after some cursing and head scratching. Anyway, just an idea.
-
WindowsPistha wrote:
I copied the Exe to the desktop, but it did not put the shield icon over my exe
Do you have a standalone manifest file for it in the directory where it exists when it displays the shield? Even if the manifest does not exist in the executable as a resource, it should still look for one in the directory of the executable and use it if it fits. I've noticed those standalone manifests suffer from caching when you try to delete or remove one, the effect can linger even though the manifest no longer exists there. Various techniques to shake it loose like rebooting ultimately prevail but not after some cursing and head scratching. Anyway, just an idea.
Thanks Bob ! rebooting also did not help :(