When I read about this problem Friday morning, the very first thing I did on initial loading of MSFS was to go to the Content Manager. I did find updates for KDFW, KSWF and one landing challenge, which I installed.
I then flew for about 2 hours with no issues. I was online the entire time.
Just now, I fired up the sim and started setting up a flight on the ground at KBOS. As sometimes happens, I was disconnected from the server. A minute or so later, I was automatically reconnected, and sure enough, received the “packages out of date” message.
I doubt that the KDFW and KSWF updates have anything to do with this problem. Those might have been there for quite some time - anything in the Content Manager should be an optional update - (not mandatory) in any case. A while back I had a bunch of livery updates in there (probably for weeks) before I happened to go to the Content Manager and noticed they were available.
What I think has happened is that at least some elements of the upcoming World Update 4 have been pre-staged on the servers, which is fine - but if they are going to do that, they need to make very sure that those elements remain in an inactive “standby” mode, until the full update is ready to go, which won’t happen until Tuesday.
Or there may indeed be a beta test group that is configured to receive the full update now, but the server is mistakenly trying to push updated content to the entire MSFS user base, which is not ready for it.
Major updates are always preceded by an update of the main sim executable, downloaded from the MS Store, which has to be in place and running before any new packages can be installed.
I answered “no” to the message and shut down the sim until they fix this problem. I don’t care if I lose my logbook, but I do not want to lose all my carefully crafted and tested graphics and controller settings.