EFB Data Provider Crash on Startup

[sully0808]

Just built a new computer and installed EFB.  It originally installed OK a couple weeks ago, but I got random crashes or I would get start errors because files were being used in by other programs?!?.  I decided to uninstall EFB and reinstall.  Now that I reinstalled, I can't even get the Data Provider to run through it's initial setup.  I keep crashing around initialization.  sometimes I get farther, but nor much.

 

I have attached my whole logfile, but most of it looks like this:

 

2017-06-03 08:09:29.670 Debug    *** Started: AivlaSoft Electronic Flight Bag 1.6.8.33244
2017-06-03 08:09:30.862 Debug    License successfully verified.
2017-06-03 08:09:30.871 Debug    check user settings
2017-06-03 08:09:30.879 Debug    User settings loaded from 'D:\My Documents\AivlaSoft\EFB\Settings\DataProvider_UserSettings.bin'
2017-06-03 08:09:30.882 Debug    Prerequisites ok, starting data provider now
2017-06-03 08:09:32.026 Debug    Initializing sequence started.

 

I have been using this program for a couple years now and love it.  Anything you could do to help me get this running again would be great!

 

Thank you,

Kevin

 

System info:

OS Name    Microsoft Windows 10 Pro
Version    10.0.15063 Build 15063
System Type    x64-based PC
Processor    Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz, 4200 Mhz, 4 Core(s), 8 Logical Processor(s)
Installed Physical Memory (RAM)    16.0 GB
 

DataProviderLogfile.txt

[aivlasoft]

Hi Kevin,

 

it seems that 'someone' has its fingers on the logfile already when the DataProvider is trying to open it. Maybe the AntiVirus software, or any other tool that is running on your computer. I don't know who else could be interested in the DataProviders logfile (other than the DataProvider itself). Maybe you can try to start the DP with administrator rights.

 

[sully0808]

I always run DP as administrator. That does not seem to make a difference. I will try to disable Microsoft Defender, but I had it on the last computer and had no issues with it. I occasionally had a bad startup or CTD but it was always start up the next time. 

 

Now I can't even get past initialize 99% of the time.