I have build an installer for my application with the QtIFW2.0.1 on Windows. As we offer the installer for download, I have signed the installer executable with a valid certificate. So our verified name shows up while the installation process ask for the needed access rights.
Nevertheless there is an unpleasant messagebox if the user uninstalls, updates or changes our application via the maintenancetool.exe.
How is it possible to extract the maintenancetool.exe, sign it and put it back in the installer executable?
Maintenancetool signing in Windows (QTIFW-667) is possible since Qt Installer Framework version 3.1.0 which was released April 11th 2019.
Related
I am trying to write a C++ program to check if an app is downloaded from Microsoft Store or not. This app can be natively installed using setup.exe file, which I can detect by reading the registry path that it initializes to.
Unfortunately when it is installed from App Store the registry path is different.
Can someone suggest me any Winn32 api for this to check if an app is installed from MS Store or reliable work arounds?
Recently I have been experimenting with Firebreath and developed a plugin in order to showcase my c++ projects on my portfolio website. I would like to make it easy for users to look at the projects without downloading files if they are new on my website.
The only issue I have at this point is that when users visit my page, they will receive a message indicating the plugin is missing. I would like to have an option for the users to automatically install my plugin without having to manually download and run it.
The plugin is mainly targetted at Windows users, since the applications are as well. I intend to support Google Chrome, Firefox, Internet Explorer. Currently I am using a MSI installer to install the plugin.
I have found a question similar to this, but I still needed to save the MSI installer and run it.
My question is: What would be the best way to implement this?
There isn't any way to "automatically" do what you want to do. The closest that I have heard of would be to use a java applet that would download and install the plugin for them. This can be pretty reliable on Mac but far less reliable on windows (for a number of reasons, among which the fact that many windows users don't have java installed and that Chrome blocks java applets by default without intervention by the user).
Other options include:
Creating a CAB file installer (only works on IE)
Creating a XPI firefox extension that packages the plugin (requires restarting the browser, only works on firefox)
Creating a CRX chrome extension that packages the plugin (only works on Chrome)
Microsoft ClickOnce used to work pretty well for one click installs of MSI files from a web page, but recently I think it doesn't work on many (if any) browsers; haven't seen it used in awhile, anyway.
There is no "automatic" way to install plugins; that would be considered a severe security issue. This is probably the #1 reason that plugins are as uncommon as they are.
do what adobe does,
create a tiny activeX application downloader, sign the activeX from with cheap SSL
when a user, enters your site, he will automatically be downloading this tiny ActiveX, after installation complete, inside the tiny ActiveX, have some type of batch script to download the EXE from remote server and silently install it.
adobe does this, on every reboot in boot.ini or startups
very easy
I followed the instructions given in this link http://support.microsoft.com/kb/167158 for packing my ActiveX control. It works fine in my development machine. When it is accessed in some other machine it gives the following error "Windows Has blocked this software because it cant verify the publisher". I have used a test certificate to sign my control and the testing machine is Windows 7 with IE 9.
Problem Fixed:
I have to sign my .ocx file other than my cab file and build the control with MFC dlls statically linked. That helped me to fix the issue.
You have some options:
Sign the CAB
Add your site to trusted site or change your browser settings
Here some links about signing the CAB:
http://msdn.microsoft.com/en-us/library/ms537364(v=vs.85).aspx - Signing and Checking Code with Authenticode
http://www.top20toolbar.com/misc/codesigncert.htm - Article about how to sign ActiveX for free
you can also try to install the activeX with non-admin rights (Only for vista and Windows 7) http://msdn.microsoft.com/en-us/library/windows/desktop/aa369519(v=vs.85).aspx - Installing a Package with Elevated Privileges for a Non-Admin
What about Download unsigned ActiveX set to Enable:
if this is working then you need to check your sign and see it's ok,
I want to create an installer for windows service built in C++. I have followed this article to create the Service.
I have 3 win32 console application in my solution. one for installation , one for uninstallation and one that does the actual work.
I must humbly recommend WiX (Windows Installer XML Toolset) for all your installer needs.
I have an Access 2003 application that communicates with a Webservice to get articles from a central database. It runs fine in a full Access install but when I make runtime install with Package Wizard included in Access 2003 developer extensions, it fails with the error message "429 cannot create an object in the active-x component"
The DLL used for the webservice communication is mssoap30.dll. That dll doesn´t ship with the runtime install and when I try to manually add it to runtime install it is there but when I try to register the DLL it fails with the message:"The register failed reason failed to initiate a DLL" Same result when I put the DLL in the applications folder or in Microsoft shared/Office11. Is there anyone who has made an Access runtime application with web service communication?
If mssoap30.dll is failing to register, that probably means mssoap30.dll itself has dependencies that are missing.
You can download the SOAP Toolkit Installer here:
http://www.microsoft.com/downloads/details.aspx?FamilyID=ba611554-5943-444c-b53c-c0a450b7013c&DisplayLang=en
It's only 1.4 MB, and it should fix the problem. Depending upon what you're using to build your installer, you should be able to embed the SOAP installer and run it during installation (or else just give both files to your users and tell them to install both - that never killed anybody).