I read in this forum that "today" has an update been releaes. So, I run the updater, Atfer the first run, it still tellls me that I have to update, After thge 10th or so runnuing the updater, it tells me that I am up to date.
It seems you are expecting the updater to tell you something about your update status, which is not what it does.
The Updater won't tell you you are outdated, and won't tell you are up to date.
The updater will just try to update *everything* ( assuming with "updater" you started it from the FSDT Updater icon ), and will show the progress about which files are being updated, if required, and will quit automatically at the end when all installed products are checked.
To know if you are updated, you just notice if it's not downloading anything other than the 3 kind of files that are always supposed to be downloaded (because we found is way faster, do to the way these files compress), which are the Airport Services, the Jetway replacement files and the custom GSX profiles for the FSDT airports.
- If you see it's downloading files OTHER than these, it means you were in need of an update.
- If you see it's downloading files OTHER than these the next time you start it, it means Cloudflare cache might still haven't got that version of the file.
The way Cloudflare caching works, is that files are not refreshed on individual nodes unless somebody connected to that node requests them.
If you are the first one requesting the new files, Cloudflare will download the files you requested from our server so you, and everybody after you, will download them from that local Cloudflare node. This might take a bit of time, depending how many files have been updated, that's why it took "10 tries" to get the latest files, you only had to wait for the time for your local Cloudflare node to download the files your requested from our server, to be then served to you.
If we didn't use Cloudflare caching, nobody would be able to download anything, good or bad or outdated, because there's no way our server could keep up with such kind of traffic.
And of course, BECAUSE the way the updater works, trying to download again something that is not what is supposed to be, you KNOW the files you downloaded are not updated (because it's downloading over and over files that are not supposed to be always redownloaded), so you KNOW you might need to use the OFFLINE installer instead.
That's only in case you don't want to wait for your local Cloudflare node to be updated. Something that always happen, as confirmed by your own report that "it worked at the 10th try": it was just a matter of waiting but, again, you don't *have* to wait: if you are in that situation, it's precisely why we also have an Offline installer.