Update 0.2.3 unable to install
-
Just uninstall the old one via the uninstaller (apps and features) then run the new installer. That worked for me.
-
@HumongoDongo said in Update 0.2.3 unable to install:
Just uninstall the old one via the uninstaller (apps and features) then run the new installer. That worked for me.
Does not work for me
-
We are currently looking into what is causing some users to not be able to install the latest version of the 146.
As a short term solution you should be able to resolve the problem in the following way:
Ensure you have closed the Add or Remove Programs window.
Browse to "C:\Program Files (x86)\InstallShield Installation Information" (this may be a hidden folder so you may need to show it -guide )
Locate the folder {94EC32C4-50EA-4603-B9C1-E797ABE5ABC5}, and delete it.You should then be able to install the 146 Professional again.
Alternatively if you get in touch with our support team they will be able to supply you with an automated method
-
Hi all,
Our IT team is continuing to investigate these error messages when running the v0.2.3 installer and we provide an update as soon as we know more.
For those who haven’t updated yet, we would recommend uninstalling v0.2.2 via Windows’ Apps and Features before running the v0.2.3 installer. That should ensure a smooth update process.
If anyone is having difficulties installing the 146 Professional v0.2.3 update, can I kindly ask you to open a ticket with Just Flight Support via the following link and our support team will be able to assist: Just Flight - Support
Apologies for the inconvenience.
Mark - Just Flight
-
Our IT team is continuing to investigate these error messages when running the v0.2.3 installer and we will provide an update as soon as we know more.
If you haven’t updated yet, we would recommend uninstalling v0.2.2 via Windows’ Apps and Features before running the v0.2.3 installer. That should ensure a smooth update process.
If you are still having difficulties installing the 146 Professional v0.2.3 update, can I kindly ask you to open a ticket with Just Flight Support via the following link and our support team will be able to assist: https://www.justflight.com/support
Apologies for the inconvenience.
-
-
If you are still having difficulties installing the 146 Professional v0.2.3 update, can I kindly ask you to open a ticket with Just Flight Support via the following link and our support team will be able to assist: https://www.justflight.com/support
Apologies for the inconvenience.
-
@JF Staff,
The issue isn't with the v0.2.3 installer exactly. The actual issue relates to the previous update in June 2024 and it's only come to surface now. The v0.2.2 installer installed the BAe146 as v2.2
See screenshot from Installed Apps:
It is thus not possible to use the InstallerShield Wizard in the Installed Apps to uninstall the aircraft either, because that wizard thinks it is older than what is installed. It thinks what is installed is 2.02.000 when the wizard is 0.2.0.
See screenshot when running the wizard to try uninstalling:
The same issue then arises when trying to install the new v0.2.3 update because again, the 146 was last installed as v2.2 when the update wizard is trying to install v0.2.3
See screenshot when running the v0.2.3 updater wizard (note this is the v1.2.3 wizard that was just shared on Contrail as an attempt to fix the issue, but still fails):
There are two solutions that will resolve this for everyone (without requiring to manually edit/delete system files).
- The versioning gets simply bumped up for this update and all future updates. So v0.2.3 becomes v2.3.0, and then future updates are greater than this number. No matter what is chosen, it must be greater than v2.2.
- It gets written into the installer logic to have the option of forcing the install anyway, irrespective of installed version.
I've seen the advice given by @Rich for manually deleting, but I will not be doing these steps as I want to see and test that this issue is fixed properly.
Thanks,
Ashleigh -
Same issue here. Also can't uninstall 0.2.2 and the directory
{94EC32C4-50EA-4603-B9C1-E797ABE5ABC5}
doesn't exist on my system.