Even when you just like all the rest of us haven’t found a solution, that is still very good input. Especially knowing you have the same issue also on another virgin installation.
Like you say, this very much seems to be a issue related to certain hardware and/or drivers for that hardware. Where the hard part of course is to figure out exactly which hardware and/or drivers. Since the issue can be avoided by stopping the standard Windows Audio service, it’s tempting to believe the issue one way or the other is related to audio. Still odd why not more people are seeing the same issue. I mean, there aren’t really that many brands and types of soundcards which would use the Windows Audio service.
Oh well, not much we can do at this point more than wait and hope Asobo will eventually do their job like you say.
Speaking about Asobo, have you so far received any useful info from them other than the standard ■■■■ they seem to send to anyone with an issue? Almost regardless what the issue is…to reinstall C++, language packs etc.
I’ve of course created a support ticket with them as well about this issue. And gave them loads of information already. Both describing the issue as detailed as I possibly can but also by providing them log files from dxdiag, msinfo as well as links to this thread. Telling them about the workaround stopping the Windows Audio service allows those of us having this issue to launch MSFS.
Sadly, they still haven’t even commented on this. I’m not sure if they’ve even bothered to fully read what I’ve told them up to this point. They keep giving me the same ■■■■ reinstalling VC++ etc over and over again as well as telling me they still see how I have the ucrtbase.dll error in my logs. Almost like they are suggesting as long as I have that error in my logs, they won’t be able to help me.
Now how funny is that!?
Like you would go to have your car fixed and they tell you they won’t be able to help you fix your car as long as it’s broken 