Could it be possible to ask to the MSFS team to:
- STOP updating on the evening when nobody is there to give support?
- STOP updating while procedures that are not tested at ALL???
This is the second big failure, are there lessons learned planned?
Lemme try and shed some light to these points 
One of the Community Managers today noted that there are multiple team members around when updates release, so there are people there watching over the forums 
Pretty much everything that is put in the final release notes has been tested in betas In the end, everything is tested by the user base!
Hope this sheds some light 
1 Like
Don’t know how I got so lucky. My update on Xbox took 15 minutes 5 minutes after it went live (but no A320neo v2). On my PC is another story. I’ll try it on another day.
MSFS update was crawling on my PC. So I check the XBOX app, needed an update. Stopped the MSFS update and closed it. Restarted MSFS and now the update only took 5 - 10 minutes.
the a320neo v2 has been temporarily removed from production due to CTDs
Yeah I read that in the release notes.