We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

shetty_rohan
Posts: 363
Joined: Fri Dec 07, 2012 5:28 am
Location: Bangalore, India
Contact: Website

Launch signed exe with working directory

Hi,

I have an aip file in which I do the following
1) I have a file(PalService.exe) which we gets copied to appdata folder
2) I have also "enabled signing" for this file
3) I also launch this file using the "Custom Action"->"Launch exe with Working directory"(e.g. File Path : [#PalService.exe])

When the setup launches this custom action, operating system pops up a message saying "PALservice.exe is not signed"
But, when I check the file in the installed folder, it shows that this file is signed.

Any idea, how to fix this??

Regards,
Rohan
Attachments
setup-windows-386.aip
aip file
(405.38 KiB) Downloaded 654 times
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: Launch signed exe with working directory

Hello,

I'm not sure why you have encountered this behaviour.

Can you please tell us a more detailed scenario, like what kind of certificate are you using for signing your executable? It is a vendor certification or you've created your own certificate and have used it to sign your executable. In order to test your scenario, if the certificate is created by you, can you please send it to us so we can investigate this?

Can you also please send us a screenshot with error?

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
shetty_rohan
Posts: 363
Joined: Fri Dec 07, 2012 5:28 am
Location: Bangalore, India
Contact: Website

Re: Launch signed exe with working directory

cert.jpg
cert.jpg (162.05 KiB) Viewed 11463 times
Hi Dan,

I have attached the screenshot.
- I use COMODO(Proper commercial certificate from http://www.comodo.com/) certificate, which is working fine(e.g. Setup.exe shows that it is certified).
- The setup launches the PalService.exe(which is signed).
- In Windows Vista, when the Setup launches the PALService, Vista shows the Security alert(because we open a socket). In this message we get "Publisher : Unknown"

Do let me know if you have any more questions

Regards,
Rohan
shetty_rohan
Posts: 363
Joined: Fri Dec 07, 2012 5:28 am
Location: Bangalore, India
Contact: Website

Re: Launch signed exe with working directory

Do let me know if you need any help in reproducing this problem.

Steps to reproduce
1) Write a very simple program which listens on some socket
2) Use advancedInstaller to copy this to a folder(also make sure that AdvancedInstaller signs this file)
3) Launch this program using the custom action
4) Run this setup on a windows Vista machine
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Launch signed exe with working directory

Hello Rohan,

Can you please add a description and a description URL in "Description" and "Description URL" fields from "Digital Signature" page and see if the behavior still persist? If so, can you please try to manually sign (using SignTool.exe) the related "PalService.exe" file using your COMODO certificate and, then manually run the "PalService.exe" and see if the behavior it is the same?

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
shetty_rohan
Posts: 363
Joined: Fri Dec 07, 2012 5:28 am
Location: Bangalore, India
Contact: Website

Re: Launch signed exe with working directory

Thanks Daniel. I will try these next week and get back to you.
shetty_rohan
Posts: 363
Joined: Fri Dec 07, 2012 5:28 am
Location: Bangalore, India
Contact: Website

Re: Launch signed exe with working directory

Hi Daniel,

Following are my findings
1) I have tried with "Description" and "Description URL". I get the same problem.
2) I tried with "signing the exe" separately, I get the same problem.
3) Instead of "Launching the program through Setup", I tried to open(i.e manually by clicking on the executable). In this case also I get the same problem.

So , it seems like a NOT a bug in AdvancedInstaller. Seems like a Microsoft problem

Regards,
Rohan

Return to “Building Installers”