Chigley

Jaap, have you turned off your Anti-Virus and Firewall before trying to upgrade? See my last post on https://forum.aivlasoft.com/topic/7069-tried-to-update-to-latest-version-now-efb-will-not-start/ I was getting similar error messages to those you have posted.

Sussed it! 😀😀😀 Taking a couple of days away and thinking about when programs don't work when normally they do usually means that it's a user problem. I was thinking about what wasn't happening during the install and the fact that it appeared to be only a few users with problems, it dawned on me it smelt of anti-virus rejection. Tonight I uninstalled and deleted everything, rebooted and turned all my anti-virus and firewall protection off then downloaded the apps afresh. With the Apps set up as antivirus exceptions and allowed through the firewalls I installed the server but didn't run it, then installed the client. Updated Navigraph FMS data manager to AIRAC 2211 I then ran the server and built a fresh database. Running the client worked, so all is good. It may be prudent in the future to add a note to further upgrade announcements that anti-virus and firewalls must be turned off as well as running the installations "as an administrator" before attempting to upgrade. It's a rookie mistake but one that is easily overlooked in the absence of a warning note. Thank you for your patience in helping to work the issue out.

I'm away for a couple of days so I'll retry at the weekend. It does sound the same as what I've done previously. Apart from the Registry, Documents folders are there any hidden files that remain after a Win/settings/Apps/uninstall, I'll also delete the build 135 downloads I have. Ian C

That is exactly what I have done already. I uninstalled both Apps via Windows /Settings/Installed Apps then restart the PC. Both build 135 apps were new downloads from your website. Please clarify "Run both installers, one after the other" Do you mean to complete the server installation by running the database builder or quit the server installation before building the database? Then installing the client. I always, without fail, run everything connected with flight simulation with administrator rights. Ian C

I have just tried everything again as fresh build 135 downloads and installs on a single machine and the server "appears" to be alright so I tried installing the client following everything as default. Everything goes OK until the same error message occurs as in my post above, however checking file explorer there is no \client folder and therefore no \client\globe folder and also there cannot be a \shic file to be opened for writing. Details as above.

I have the same problem. Initially I couldn't get either the server or client to update to build 135. Eventually I updated the server but didn't see a splash screen telling me to delete old databases. As I was guided, I created a new database and also updated to Navigraph AIRAC2211. The server started OK and last night the client (on a networked PC) started without any problem. As I had been running the server as 135 but the client as 134 (I hadn't had a splash screen advising of an update being available) I tried to update the client to 135 tonight but the client wouldn't open; it froze at 0% progress when trying to open the airport database. At this point I decided to delete the current database and create a new one which went OK, no problem. The client still wouldn't open freezing at 0% progress opening the airport database. I deleted the client app and attempted to reinstall it, the installation failed, see screenshot . Everything I tried failed so I uninstalled the client and server, on my SImulator PC and deleted the Aivlasoft folder in Documents. I did the same for the networked client on my secondary PC. On both PC's I did a file explorer search for any AivlaSoft files and deleted everything found. I also deleted the AivlaSoft folder in the RegEdit. I restarted both PC's and downloaded Build 135 from your website and attempted to reinstall the client. The installation failed with the same error as shown below, attempting to inore the erroneous file only creates another error message for the subsequent file. For a fresh install to fail is something lingering in the background? Ian C P3DV5 EFB V2 134 and 135 Tried Networked and single PC Default path Licensed As above