Hauer 31 Posted January 13, 2021 Share Posted January 13, 2021 Dear Aerosoft Team, As I was experiencing a sudden annoying lack of beacon / strobe lights with my entire Airbus series, I decided to delete all 3 products from my PC in order to re-install them. I was able to re-install both the A318/19 & A320/21 products and update them to the latest version via the Aerosoft Updater. However, when having re-installed the A333 and wanting to update, I ran into the following issue (made 2 attempts, both with the same result). See attached. Note that I had opted not to install the "locked" version of RAAS (FS2Crew) as I own the professional RAAS 64-bit product. During the update process, a screen appears asking me again if I want to install the RAAS (FS2Crew) product. I opted not to via the exit button. For you info, everything was installed as "Administrator" and my Microsoft Defender AV had been deactivated during the whole proces. Please advise. Thank you / danke. Regards, Herman Please login to display this image. Please login to display this image. Please login to display this image. Link to comment Share on other sites More sharing options...
miquelpp 27 Posted January 13, 2021 Share Posted January 13, 2021 Hi , this happened to me with a clean installation. In my case I had to install the "oficial update" first and then the experimental. Problem solved. Maybe can help. Best. Miquel. Link to comment Share on other sites More sharing options...
MajorTom 9 Posted January 14, 2021 Share Posted January 14, 2021 Hi, I've reported this some time ago in the 'updater' section, also an easy fix to 'resolve' this : https://forum.aerosoft.com/index.php?/topic/157464-updater-a330-problem/ And yes, it only happens when you do a clean install from nothing to the latest experimental, then the RAAS installer is called twice... Maybe it will be fixed with the next release ? best regards, Tom Link to comment Share on other sites More sharing options...
Hauer 31 Posted January 14, 2021 Author Share Posted January 14, 2021 Thanks guys! Followed Miquel's procedure and all went well. First updated to v1.0.3.1 and afterwards ticked the experimental option and now have v1.0.3.2 Agree with Tom that possibly Aerosoft can look into this... Am somewhat surprised this had not been picked up prior to releasing the experimental update for a "clean" install. No doubt, others will encounter similar... Cheers - Herman Link to comment Share on other sites More sharing options...
Deputy Sheriffs Secondator 643 Posted January 15, 2021 Deputy Sheriffs Share Posted January 15, 2021 Hello Herman, Thanks for bringing this to our attention. We'll have a look into it and hopefully next update will go smoothly. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.