nicked on 23/1/2024 at 20:30
Be interested to know the operating system of others who are affected.
vfig on 23/1/2024 at 21:00
Quote Posted by fortuni
Hopefully you're right, but this issue has now been reported 3 times in as many days. Would you advise everybody to uncomment their no_unload_FMsel? Apart from preventing this crash are there any other potential issues by uncommenting no_unload_FMsel?
dont enable the config if you are not having the problem. no sense in changing things that are working just fine.
elymmit on 24/1/2024 at 05:25
Quote Posted by nicked
Be interested to know the operating system of others who are affected.
This happened on my wife's desktop running Windows 11. I checked my laptop, which is still running Windows 10, and FMSel is working on that.
Sent from my SM-G986B using Tapatalk
is_it_rats_or_apes on 24/1/2024 at 06:17
Quote Posted by nicked
Be interested to know the operating system of others who are affected.
Windows 11
nicked on 24/1/2024 at 06:33
Sounds like Windows 11 is the culprit then.
Dr.Sahnebacke on 25/1/2024 at 09:12
Quote Posted by nicked
Sounds like Windows 11 is the culprit then.
I suggest to check out, what kind of updates in win 11 are installed the last days.
Dr.Sahnebacke on 25/1/2024 at 18:39
I have some new information (only in german), but don't know, how to use them now !?!?
This is the name of the last update in Win 11 , published on 2024-01-19:
2024-01 Kumulatives Update für .NET Framework 3.5 und 4.8.1 für Windows 11, version 23H2 für x64 (KB5033920)
vfig on 25/1/2024 at 20:43
trying to work out what changed in the windows 11 update to start triggering this issue is unlikely to be a fruitful approach.
the most useful information on what exactly is happening would be a crash dump. if someone experiencing the problem is willing to temporarily disable the workaround, and capture a crash dump, then we will have actual data on what the problem is instead of speculation.
if you are comfortable with registry editing, instructions for capturing a crash dump can be found here: (
https://helgeklein.com/blog/creating-an-application-crash-dump/) https://helgeklein.com/blog/creating-an-application-crash-dump/.
or more simply—if you have visual studio installed—you can launch thief/dromed through that, and when it crashes, save a crash dump from the Debug menu.
however, even with a crash dump, it might not be easy to locate or fix the problem, so using the config to work around it will likely still be necessary.
Constance on 25/1/2024 at 21:29
Hey, I had the same issue happen and, unfortunately, didn't take the time to read the troubleshooting.txt at the time.
I ran sfc /scannow and since it claimed to have found some issues, I just assumed my Windows install was bad and reinstalled it all from scratch.
At least I'm fairly sure tell that the problem does NOT come from KB5034123 or KB5033920 which I both reinstalled manually and could test running the game through FMsel without issue, but probably from a later update that got installed after I reconnected the computer to the Internet and performed a Windows Update. Might be something to do with the Windows Defender updates instead…
Dr.Sahnebacke on 26/1/2024 at 08:05
OK, @Constance, and now the game runs fine for your system?
For me is actually the question, should I meanwhile install darkloader instead and transfer the savegames to that? Perhaps I also find the time to test the suggestion from @vfig with the Crash-Dump.
