Bug Bounty: 150 $ for solution PDFCreator on Windows Vista
Submitted by philip on Wed, 2007-09-12 14:16.
Hello,
as you all know, PDFCreator currently does not work properly under Windows Vista. The upcoming Version 0.9.5 will have basic Vista support, but the main problem has not been solved.
The problem is, that Vista has a strict security system, that does not allow the way PDFSpooler.exe tries to start PDFCreator under the context of a user.
Is there someone who has already done this under windows Vista?
We have the possibility to do this in C (not C# oder C++) oder in Visual Basic 6.
Any help, hints oder experience is appreciated here, as we have spent several days on this issue without a result.
We are offering a bounty of 150$ for the first one who can solve this.
regards,
Philip
Hello,
(I have Microsoft Windows Vista Ultimate x64.)
It seems that the problem is the User Account Control restricting access. This program needs to run with administrator rights.
To do things with admin rights, many programs require elevation. You need to tell Vista to elevate each EXE file that needs administrator rights.
For each EXE file (only if they need it), create a file named the same as the EXE + ".manifest", e.g: "PDFSpooler.exe.manifest".
In the manifest file, copy the following:
______________________________________________________
<?xml version="1.0" encoding="utf-8"?>
<asmv1:assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1" xmlns:asmv1="urn:schemas-microsoft-com:asm.v1" xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<assemblyIdentity version="1.0.0.0" name="MyApplication.app"/>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
<security>
<requestedPrivileges xmlns="urn:schemas-microsoft-com:asm.v3">
<!-- UAC Manifest Options
If you want to change the Windows User Account Control level replace the
requestedExecutionLevel node with one of the following.
Limited User:<requestedExecutionLevel level="asInvoker" uiAccess="false" />
Administrator:<requestedExecutionLevel level="requireAdministrator" uiAccess="false" />
Highest possible:<requestedExecutionLevel level="highestAvailable" uiAccess="false" />
If you want to utilize File and Registry Virtualization for backward compatibility then delete the requestedExecutionLevel node just below:-->
<!-- Change this --><requestedExecutionLevel level="requireAdministrator" uiAccess="false" />
<!-- ^ Change this ^ -->
</requestedPrivileges></security>
</trustInfo>
</asmv1:assembly>
______________________________________________________
Then, after you pick from the options I listed in the text above and delete the commands, embed the manifest file(s) into the corresponding EXE(s) when you compile it/them.
You might just choose what I put in for default:
______________________________________________________
<?xml version="1.0" encoding="utf-8"?>
<asmv1:assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1" xmlns:asmv1="urn:schemas-microsoft-com:asm.v1" xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<assemblyIdentity version="1.0.0.0" name="MyApplication.app"/>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
<security>
<requestedPrivileges xmlns="urn:schemas-microsoft-com:asm.v3">
<requestedExecutionLevel level="requireAdministrator" uiAccess="false" />
</requestedPrivileges>
</security>
</trustInfo>
</asmv1:assembly>
______________________________________________________
I hope this helps! (And I also hope that I get the $150!)