I have attached the asked for zipped scenery config file.
As I've said in my previous message, your scenery.cfg contains non-standard commands, which indicates you used an external utility to change it. Those non-standard command, as they are, wouldn't cause a problem to the migration process, because the only lines that are checked are the ones with the "Local" keyword, which will be changed from the old path to the new one, the one you installed the Addon Manager into, which by default is C:\Program Files (x86)\Addon Manager.
However, such path hasn't been updated in your scenery.cfg file but, since there's no reason why the installer didn't do it, the only possible explanation is that the external utility you are using, must have restored your scenery.cfg to a previous version, one that was current BEFORE the sceneries were migrated, causing the problem.
Of course, this should be fixed by reinstalling all the FSDT and Flightbeam sceneries, using only the current installers, which will update all paths.
Or, if you know how to do it, you might just change all the "Local" paths in the scenery.cfg, to have the full path for the scenery, which by default is C:\Program Files (x86)\Addon Manager\ so, for example, assuming you installed in the default folder, this line:
Local=FlightBeam\KSFOHD
Should be like this:
Local= C:\Program Files (x86)\Addon Manager\FlightBeam\KSFOHD
This one:
Local=fsdreamteam\CYVR
Should be like this:
Local= C:\Program Files (x86)\Addon Manager\fsdreamteam\CYVR
And so on. This is what our installer does but, as I've said, if your external utility restored a previous version, I can see why you have the problem now. In any case, I've attached a "cleaned up" version of your scenery.cfg, with a more readable structure, which should make it easier to edit.
