It’s clearly not related to someone’s computer, internet or whatever you blame. It’s on Microsobo side.
No workaround described here will fix it because it’s not on our side. Devs will take three to four months ‘investigating’ - i.e. doing nothing - just to find out what everybody here is telling them for weeks.
This is still happening to me, despite doing the recommended date/time sync.
Still the same symptoms - stuck on “Check for Updates” screen with the computer downloading something at full speed. When I exit the sim, downloading stops immediately.
Luckily for me, a restart usually cures it, and the sim normally runs ok, so it is still an irritant rather than a game-stopper. Unfortunately it is one of many irritants I have to learn to live with - for example Asobo have made it clear they are not going to fix the “Missing Ready To Fly” bug in VR (87 votes) which also requires a restart. I really can’t look forward to FS2024 knowing these bugs are most likely unresolved, with more probably being added.
I think “checking for updates” can often be a red herring leading us in the wrong direction.
If you are still really stuck with it then go to your “packages” folder - “official” - “onestore” and delete ALL the folders with the most recent date (this will often be todays date, but not always).
Sim should start in most cases without having to do a full reinstall.
The suggested solution at the top worked for me, though the quickest way for me on my W10 is to
Right-click the time and date display on your toolbar
Click Adjust Date and Time from the top of the menu
Click Sync Now button
mine hadn’t been sync’d for a couple of days.
I suspect the actual bug is in the MSFS code checking for updates - a variance of a few seconds between the server and your PC being enough to put it into a hard loop continually retrieving the same file date and time info.
My guess is that’s the root cause. File timestamp comparison down to the second instead of allowing at least a 1 hour delta. Poor coding, if true, and could be easily remedied.
I started it this morning just fine, after cloding it and coming back to it later on got stuck in checking for updates no matter what i did, time is synced and my connection is good, even flushed dns and nothing.
As I said, in my case it is a irritant, not occuring every time but needing a restart when it does occur. Seeing the unfortunate results many others have had after trying to “fix” such problems, I for one am certainly not going to risk deleting folders. Half a loaf is better than none.
Stuck in the update screen happens to me too regularly the last week (approx 1 of 5 starts). I made a new MSFS installation before SU15 to Start as clean as possible. I have a full backup of a just finished Su15 installation and I clean my scenery cache regular, when swapping large sceneries or mods, and exclude my community folder.
In short, I know how to maintain my System and how to analyze problems and solve them.
This is 100% on the developer side. This never happened in this rate before SU15. When I’m patient, I give the update screen about 2 min to give me some feedback, well I’m not so Patient any more like I used to be when starting MSFS.
What I do when MSFS is stuck:I switch to Task manager and kill the MSFS process. I’m every time anxious that it screws things up, as I’m also monitoring how much traffic is involved. Well up to now, after around 20 times doing this, MSFS start after it regular. Fingers crossed.
No program or game, that I have used before, behaves so unpredictable(I have stopped reporting and counting how many times UI elements are missing and prevent me to start a flight…).
Ladies and gentlemen (drumroll):
(Tush!)
Welcome to AI cloud gaming!
I’ve noticed lately I’ve had to go into the xbox app and use the support/repair tool multiple times to get it going. As soon as I see that hang on updates for more than 10 seconds I go back out and run it again.
Sounds like something is messing with the files that shouldn’t, corrupting them in the process. Antivirus program? Windows security settings? Faulty Ram? Faulty hard drive?