OK - I think we are going in circles. First do you understand why this is happening? second do you understand that it is not permanent?
It can happen in 1.77 is you do not have the main footprint database installed. So if you want to try this then in the 1.77 installation make sure ADE is not running then go to the Global folder and carefully move the file mfdb.dbs to another folder and be sure to remember where you put it
Now start ADE 1.77 and try loading a stock airport - I am sure you will find it takes a long time. If you check the Global folder you will find ADE has recreated the mfdb.dbs file but it is much smaller than the one you moved
Close and re-open ADE and load the same stock airport as before. You should find that it opens much faster. Shut ADE and put the original mfdb.dbs back overwriting the newly created one. If you want to you can open that same stock airport again and it should load faster. It happens that 1.77 has a well populated database.
Now run ADE 1.79 for v5 and load again that stock airport that took 5mins 45.53 sec to open. I am sure it will load much faster. Also I can tell you that the size of the airport you open is not relevant to this process. When you open a stock airport in 1.79 for the first time ADE is processing a whole region of airports and objects. So in fact nearby airports will also open quickly.
Perhaps this will make what is going on more acceptable. It needs a bit of time and you may get slow loads the first time you open a stock airport in a given region.