From time to time, when launching the installation of our software package (in silent-mode) on Windows 8.1, the following message box pops up at the end of the installation: “Error: could not generate uninstaller”. Nevertheless, the Uninst.exe and Uninst.log files have been created and do not look corrupted.
We are currently using PB 3.1 (we cannot test it with 3.2 because of another pending issue).
Do you know where this error comes from? This issue is quite blocking since the automatic installation on our system is hung by the popup.
Actually, on our automatic test systems, we do not have any antivirus program running, even Windows Defender is completely disabled for tests performances reasons (antivirus and anti-spyware). The only active protection is Windows Firewall, I don’t know if this one can interfere. Do you know precisely at which phase of installation this error is issued? Perhaps it would then be possible to do some workaround in the custom actions.
We didn’t see any additional error code (besides the “-1” which is general, I guess) and there is no log from previous install since we always start from a clean situation. Here is the test sequence:
The computer boots and starts Windows 8.1
The task scheduler launches our Paquet Builder installer from the command-line at log on (we use automatic log on). Note that our installer is launched from the local account’s Temp folder, I don’t know if this might be a problem or not.
The error sometimes occurs here and blocks the process.
Some tests are executed.
Our Paquet Builder installer is launched from the command-line to uninstall the package, + some cleanup.
We suspect that some tasks from Automatic Maintenance might access file and or folders among which our Paquet Builder installer files. We haven’t seen the problem after one week, but it is infrequent, so we’ll check further during a couple of weeks to be sure it no longer occurs.
Did you have any feedback of other Paquet Builder issues due to Automatic Maintenance under Windows 8.1?
If all files are in the “Temp” folder, maybe Automatic Maintenance tries to analyze them to determine whether they are real temp files or something else in order to delete them?
No feedback nor other error report regarding this though.