"Install" "setup" to Vista
-
Hi all: It seems Vista is sensitive to executable containing word like "Install", "Setup" etc, The problem I have is that I have that kind of exe called "Setup.exe" which contrary to what its name indicated is not an installation program, when it was closed the Vista prompts me "this program might not have installed correctly" later I found out that maybe Vista asks for "Uninstall" key, so I provided it with that. This method seems to work for one time, but failed to do so subsequently, but I'm not sure if it is a legitimate method.
-
Hi all: It seems Vista is sensitive to executable containing word like "Install", "Setup" etc, The problem I have is that I have that kind of exe called "Setup.exe" which contrary to what its name indicated is not an installation program, when it was closed the Vista prompts me "this program might not have installed correctly" later I found out that maybe Vista asks for "Uninstall" key, so I provided it with that. This method seems to work for one time, but failed to do so subsequently, but I'm not sure if it is a legitimate method.
Add a manifest to the EXE that tells Vista what permission level it needs. In almost all cases, you'll use
requestedExecutionLevel='asInvoker'MSDN article: clickety[^]--Mike-- Visual C++ MVP :cool: LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ Ford, what's this fish doing in my ear?
-
Add a manifest to the EXE that tells Vista what permission level it needs. In almost all cases, you'll use
requestedExecutionLevel='asInvoker'MSDN article: clickety[^]--Mike-- Visual C++ MVP :cool: LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ Ford, what's this fish doing in my ear?
Thanks, Michael! I used the following manifest configure, and compiled it into the PE using the method mentioned in the article, but problem remains. <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3"> <security> <requestedPrivileges> <requestedExecutionLevel level="="asInvoker"" uiAccess="false"/> </requestedPrivileges> </security> </trustInfo> </assembly> I was wondering if I choosed the correct method to build that manifest into the PE after I read http://www.gregcons.com/KateBlog/CommentView.aspx?guid=682d4de9-572f-4a18-b822-19069e50410f. But I did see the manifest exists in the PE.
-
Thanks, Michael! I used the following manifest configure, and compiled it into the PE using the method mentioned in the article, but problem remains. <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3"> <security> <requestedPrivileges> <requestedExecutionLevel level="="asInvoker"" uiAccess="false"/> </requestedPrivileges> </security> </trustInfo> </assembly> I was wondering if I choosed the correct method to build that manifest into the PE after I read http://www.gregcons.com/KateBlog/CommentView.aspx?guid=682d4de9-572f-4a18-b822-19069e50410f. But I did see the manifest exists in the PE.
If that is your complete menifest file, then it's incomplete, try this one.
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity version="1.0.0.0"
processorArchitecture="X86"
name="MyExe.exe"
type="win32"/>
<description>MyExe Description</description><!-- Identify the application security requirements. -->
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel
level="asInvoker"
uiAccess="false"/>
</requestedPrivileges>
</security>
</trustInfo>
</assembly>regards,
Jonathan Wilkes Darka [Xanya.net]