I am so glad I am not alone as I have been searching far and wide and looking into this issue. I have the exact same error with the peculiar faulting module
190_E658703.dll
I will let you know if I find anything but for now I am gonna have to use 2024 until I can find something for 2020. Please let me know if you find something as well and hopefully someone from the community or support team can assist us.
I spent the night trying to figure out what this 190_E658703.dll is and what’s going on. It started at 03:00 UTC today (01/30/2025). I was flying normally, arrived at my destination, and needed to change aircraft. As usual, I restarted the simulator when switching to a more complex aircraft. So far, so good. I ended the flight and closed the simulator without any issues.
When I opened it again, it asked me if I wanted to enter safe mode. I thought: “What do you mean? Everything was fine.” So, I clicked to enter normal mode, and then the issue of closing in the middle of loading started. I looked for information here on the forum, and no one had specifically reported this 190_E658703 “unloader” dll error.
I removed all my addons from the community folder, reinstalled drivers, uninstalled the simulator, installed it again, cleared cloud data, and it keeps crashing. I’m at a dead end now. It’s frustrating. There’s no way this is Windows 11. I have no interest in going back to 10.
Hi the same issue, CTD in the middle of the loading. This happened just after I installed an update just 20min ago, maybe related to todays Nvidia new driver and DLSS4??, dont know, but now I can not start the game, CTD before it even finish to start.
The last time I started it was around 1 month and it worked fine, in Windows 11, so I think this should not be the issue. In my case just happened today when I started it again, asked me to install an update, and after installed it just CTD
Hi @papolo2001 , this problem happened to me before this update for DLSS 4 arrived. It may have been a coincidence. I even updated my Nvidia driver to this version that supports DLSS 4 but it didn’t solve it anyway.
I’m also having the same issue. It was working perfectly fine yesterday. I haven’t downloaded the current drivers either. I’ve attempted to start it up in both normal mode and safe mode, but there’s no change. I’ve also removed everything from my community folder, but the issue persists.
A friend of mine who is on Windows 11, the Sim is working normally but he told me that his OS build is Windows 11 22H2 26100.2894. Mine is Windows 11 22H2 26100.3037. How is yours…
Have the exact same issues as well and I’m on 24H2 26100.2894. Already had some issues yesterday with the error message showing “Your graphics device has encountered an issue” and “DXGI unkown”. I reinstalled today and as I go past the installation screen, my sim goes as well. Also have the new version of the NVIDIA app as well as the new drivers.
It’s frustrating. I didn’t change anything either. I reset and cleaned my entire simulator thinking it was something I did and it didn’t solve the problem.
I also encountered the same with 24. However, it crashed differently as soon as the game launches, the screen goes black for a few seconds before it crashes. Can’t even play either game how nice.
Same issue here now. The game just CTDs right after the launch screen, and I’ve not changed a single setting or file since I was on yesterday. 2024 SU1 Beta for what that’s worth.
In Safe Mode, I uninstalled the NVIDIA driver using DDU – this step is very important.
After uninstalling and restarting, I installed the latest driver, version 572.16
A crucial step: During the driver installation, I selected the option to install only the driver. In the next window, I chose the driver, PhysX and the “clean installation” option.
After installation, I restarted my PC, and MSFS 2020 is now working.
As you may have noticed, I did not install the NVIDIA app.
Found a solution go to the following folder: C:\ProgramData\NVIDIA\NGX. After doing so, search for the file 190_E658703.dll in the folder, then delete it. I saw this on Reddit, and it works perfectly fine now.