coryb
Posts: 1
Joined: Sun Aug 20, 2017 8:41 am

Installer error after restart

We ran into some trouble with our installer where after a restart occurs after installing the "Visual C++ 2013 Redistributable (x86)", the installer would automatically run upon logging in and pop up an error "Invalid Command Line". Our version of Advanced Installer was out of date and our maintenance period expired, so we renewed our license. With the latest version of Advanced Installer, our built installer no longer has this problem, but now it has a new problem. Now after reboot, during the install, it shows an error "Source file not found: C:\...\Atlasware_Setup_2.2.11.01.cab. Verify that the file exists and that you can access it." I did look and the file does not exist. These are the steps to reproduce:

1. Build an installer that includes the prerequisite "Visual C++ Redistributable for Visual Studio 2013 Update 5 x86".
2. Rename the built installer file (I think this is a key step; if the installer name doesn't change, the install succeeds).
3. Find a machine that has an older version of the Visual C++ 2013 Redistibutable and has an active application that is using it.
4. Run the installer on this machine. It will attempt to install the new 2013 redistributable and then say it must restart to complete the installation.
5. Click Restart and wait for the reboot. Log back in to get back to the desktop.
6. Our main installer is automatically started. (This was the point where "Invalid Command Line" dialog was shown with the installer built from the older Advanced Installer)
7. Navigate through the installer until it begins the install process. This is when the "Source file not found..." error is shown.

This is a screenshot of the error:
Source_File_Not_Found_Error.png
Source_File_Not_Found_Error.png (55.33 KiB) Viewed 1396 times
So even though this error can be prevented by not renaming the installer, this is not an adequate solution because 1) we cannot control the filename they use when they save the installer file and 2) we actually provide a version of our installer called "Atlasware_Latest.exe" which is always the latest version of our installer; it does not contain the version number like it does when it is output from building in Advanced Installer.

Is there any solution to this problem aside from not renaming the installer?
Sorin
Posts: 663
Joined: Mon May 08, 2017 1:03 pm

Re: Installer error after restart

Hello and welcome to our forum,

Please note that during an installation, after the restart, it is possible that the original msi and resources to be needed. Can you please try to enable "Single EXE setup (resources inside)" from "Builds" page and "Do not delete extracted MSI and CAB files" from the same page, under "Bootstrapper Options" section. This option prevents Windows Installer to delete MSI and CAB files to be deleted from the extract location above. If your users no longer have your EXE, this will allow your package to be repaired or modified (e.g. from the Control Panel) if required by the user or by a patch.

Please let us know if this was helpful for you.

Best regards,
Sorin
Sorin Stefan - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”