[Re-report] Game closes upon attempt to create new/resume old worlds (update from 7.11.22)

When I try to create world (0 server mods) or resume already created worlds game crahes without crashlog. Before crash happens character seems to be loading in the world since save positions (after relaunching the game) are updated including change of day count. Launching second time allows to access world, however, on the next reconnect (to the different save position, but to the same world and without playing at any other worlds in between) this issue happens again.

I can access normally servers from browse list though.

This issue started to occur after A Little Drama update, and after 25.10.22 update (528116) it is still present.

Update 7.11.22.

Game closes even after I added dontstarve_steam_x64.exe and dontstarve_dedicated_server_nullrenderer_x64.exe into Windows Security's allowed/trusted programs list, and ransomwhere protection also seems to be not the case since Recently Blocked Apps list is empty. I made sure Steam is updated as well as my operating system, I tested on vanilla world (0 mods) right now. Interestingly enough my friend with different operating system (he has Windows 10, I have Windows 11) launched world just fine. On the other hand, I updated from Windows 10 to Windows 11 a while ago and only recently this problem started to occur.

Moreover, now on modded server I can't load successfully even after 2nd try (which wasn't the case before, i.e. I could load on modded server from 2nd try), and those mods were up to date, worked just fine yesterday (they didn't receive update since then), worked fine and didn't cause any problems upon launch for years before.

And not only all of this happens in case regular hosted game, I can't join even my own dedicated server that is hosted from this same machine (in first iteration of report I played on dedicated server that was hosted by Nodecraft with other person as owner, and that worked fine).

I don't know why and how last time it worked so bug was closed, but maybe my test just wasn't accurate that time: I created new world right after deleting previous one that failed to connect me, and game used that same folder, so maybe 2nd launch effect was somehow replicated.