Based on the fact how many titles apparently are affected, that in a way must be a good thing. Since that means chances are higher we’ll see the issue addressed sooner rather than later.
What I still find odd is why this only affects some people. It would be very beneficial if we could find out what those of us having this problem have in common when it comes to hardware and software.
It’s tempting to think it’s related to the sound card used or its drivers. However, this doesn’t seem to be the culprit. Because as previously mentioned, I’ve tried changing my default audio device to a completely different one and I still have the same problem.
I also recently found a new driver version for my built-in Realtek audio card on my MSI Z390 MEG ACE motherboard and had my hopes up this would have fixed the problem. Sorry to say, the problem is still there with the new version.
I was kind of hoping it was a onboard realtek issue that a new soundcard would solve but if you have had the same problem with another audio device that doesnt give much hope of that.
here is what I am running
Not sure what good it will do to post our specs in here but maybe it can give a clue what those of us having this issue have in common when it comes to our hardware.
Here’s my full specs:
Case: Corsair Obsidian 500D RGB SE
Board: MSI MEG Z390 ACE - Bios: 1.A0
PSU: Corsair HX1000i
CPU: Intel Core i7-8086K
GPU: MSI GeForce RTX 3090 SUPRIM X
MEM: Corsair Vengeance RGB 3200MHz CL16 4x8 GB
HDD: 1 x Samsung 970 Evo Plus 2 TB, 1 x Samsung 970 Evo Plus 1 TB, 1 x Samsung 950 Pro 500 GB, 1 x Western Digital Red 4 TB, 1 x Seagate IronWolf 10 TB
CPU Cooler: Corsair Hydro H115i Platinum
HMD: HP Reverb G2
OC CPU: 5 GHz (HT disabled) - vCore 1.3V
OC GPU: Factory overclocked 1860 MHz
OS: Microsoft Windows 10 Pro
Anyone in here heard anything new from somewhere about this issue or even managed to fix the issue somehow?
Or is everyone getting used to always disable the Windows Audio service before launching MSFS?
I’ve sent two reminders now to Asobo Support asking them for a status update on my open support ticket where I sent them some config and log files they were asking for.
I guess you still haven’t found out what is actually causing this issue where having the Windows Audio service running while launching MSFS will make it CTD?
Just tried to reinstall visual c++ libraries one more time to no avail.
As far as I can see the issue may be related to specific hardware configuration.
I don’t know if somebody tried to do fresh win10 installation but in my case I have virgin installation in one of my drives which I use for testing. There the same problem existed .
Honestly I left Asobo to do their job since I have reported the issue.
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
Ok, I have a good news and the solution at least on my end.
I went ahead and installed Win 10 21H1 pre-release through the windows insider program.
It has been released a couple of days ago and I can confirm that the problem is solved.
Just make sure you de install the simulator first and than go and update to Win 10 21H1.
Cheers,
Thank you Bekotino! I have tried almost everything to fix the issue (FS2020 not starting) and this did lead me to correct solution. What I have tried without success (or some of them, can’t remember everything..):
Change the language settings to eng US
Uninstall Win updates
Update the drivers
Reinstall all the C-runtime libraries
Fix the registers
Join to the Windows Insiders and update ftom Win10 20H2 to 21H1
etc.
Disabling Windows audio from services did help, FS was starting but obviously without sounds. Then I started to remember that Asus Armoury Crate did install “Two-way AI noise Cancellation” software couple of days ago. I did open the Windows sound setting from speaker icon and noticed that there was “blank space”.
This mystery device did belong to the “Two-way AI noise Cancellation” software (Asus Utility in Windows Device Manager) and after uninstalling it, FS2020 starts again!
I’m glad I could help you finding solution in your case.
Did you tried to reinstall Two-way AI noise Cancellation and see what is happening ?
I believe your motherboard audio contain this feature.
In my case I have tested all versions of Win 10 21H1 and all of them worked.
I hope the final release version will be fine too.
After having more CTDs than flying for a long time and having tried every single suggestion in here and elsewhere to no avail except for a clean reinstall of Windows I took the plunge and what do you know…I can now launch MSFS without stopping the audio service and I also got rid of some other CTDs I’ve seen. I’m still on 20H2.
So, clearly there was something in my previous installation causing these issues but guess I’ll never know exactly what. Still find it strange since I’m very careful keeping my system as clean as possible from anything I don’t need.
I’ve had one single CTD after the reinstall and it was caused by perception.dll if I recall the name correctly and happened when switching from VR to 2D. I had lots of these before the reinstall. So I hope this was a one time thing.
Hi everyone. I’m new to MSFS, and I’ve had days of frustration with the ucrtbase.dll issue (amongst others). I’ve now followed the method involving the audio supplied by Bekotino, and lo…the thing worked !
I really don’t understand why this should be, but anyway I got software that works now.
I suppose the logical question next is - has anyone found, or been supplied with a permanent solution to this isue, as I don’t really want to be disablind audio every time I want to launch the game.
Many thanks for any replies
yes… since two years we know that lots of these ASUS sound tools ( which features nobody realy need ) cause issues, thus remove all that ASUS sound tools and check whether your sound-drivers are realy up2date.
You can of course also simple try do disable these Noice Canceling stuff, if these was the only one culprit in your case. So far I know is this also per default at Off and must manualy enabled..
( armor crate )
Been a software developer for over 40 years. Never seen such a poor attempt at a product.
Windows 11 and an AMD 3950X and NVidia 3060TI. I get this error every time.
Tried installing it on an old Intel 3770K with an old video card. Loads and works after a couple of tries. Pretty slow on that platform.
Tried installing it on a brand new Lenovo Yoga 7i, 11th Gen with Intel Arc graphics. The play button blinks and it does nothing. No errors, nothing in the event viewer.
This biggest disappointment is the lack of effective error messages in a log file someplace.
That’s just stupid.
I’m 68 and don’t have enough time left on this planet for this.
In cas windows audio service on/off will help, the answer is given in some existing topic. You need to check your sound-drivers /tools. In special check for running nahimic services, or installed sound tools ( in special asus or msi )
