Latest update today july 27, MSFS wont start anymore.

[Baleur]

Edit2: Okay, i have traced it via Dependency Walker to Kernel32.dll in System32 (which is what the above mentioned WTF.dll and CoherentUIGT.dll links to).
Clarification. It's the function "SetThreadDescription" which is missing from my Kernel32.dll.

Basically, Asobo just decided to make the whole game incompatible with my Win10 version. No refund allowed, no nothing.
Thanks for wasting my 70 bucks.

Just pops up on the task bar for 1 second, then closes itself.
Win 10, 32gb ram, 1070 (6gb vram), intel i7 6500k

Edit: Post July 30 hotfix, still doesn't boot.
Edit2: Second August 7 hotfix doesnt help.

I've now filed a complaint against Valve with my local governments consumer rights council to move forward with a refund. I'm not accepting Steam's blatant "nope".

[Baleur]

Interesting, i also use Process Lasso, but just disabled it (first the core engine services, then the app itself). Didnt help.
Given the other guy that just suddenly got it running, perhaps it is indeed a server thing? But for whatever reason the dll's show up as the error, if unable to connect to the authentication server perhaps?

[xwing]

引用自 GurtTractor：

My friend who has been having this issue disabled Process Lasso and that finally let him get past the black screen crash after hitting play in Steam. We tried just about everything else but that seems to have been the culprit here.

He had the WwiseLibPCx64P.dll thing showing in the event log error report.

That is it.
Problem SOLVED for me :-D
Thaaaanks

[Killer128]

引用自 xwing：

引用自 GurtTractor：

My friend who has been having this issue disabled Process Lasso and that finally let him get past the black screen crash after hitting play in Steam. We tried just about everything else but that seems to have been the culprit here.

He had the WwiseLibPCx64P.dll thing showing in the event log error report.

That is it.
Problem SOLVED for me :-D
Thaaaanks

I do not have that app in my system so that will be something else for me

[GurtTractor]

I think that the issue may be related to how Windows assigns programs to particular threads, which is why Process Lasso could cause a problem and why it randomly starts working for some people, as I think thread assignment is bit random with Windows.

Maybe for those still having the issue you could try changing the cores setting in the BIOS, like to just 4 cores or something. Just an idea.

[ZENITHORIZN]

OK, downloaded the 40 gig for PC update then another 29 gigs worth of updates, now it wont do anything if I click on anything world map or bush trip or tour CTD.

[Angel of Verdun]

引用自 Baleur：

Just pops up on the task bar for 1 second, then closes itself.
Win 10, 32gb ram, 1070 (6gb vram), intel i7 6500k

Are you running any CPU management programs / software like ProcessLasso?

I had ProcessLasso running and game did same thing... starts, I get the client window pop up for a second or two then it automatically closes and quits to desktop.

I turned off ProcessLasso and then MSFS would start up just fine.

Now, however, I am stuck on the "Checking for update" thing and has been stuck on that now for 12 hours straight.

Anyways, maybe you can get one step further if you have any CPU management software running and try disabling that.

[marc.bret.87]

I can start the game after the update, but once I hit "Fly" it just crashes to desktop... Any idea how to diagnose the issue? I have NZXT running though

[Oz Gaming]

引用自 marc.bret.87：

I can start the game after the update, but once I hit "Fly" it just crashes to desktop... Any idea how to diagnose the issue? I have NZXT running though

Same. Click the FLY button and instant crash to Desktop.

[Zabubenchik]

Hello. Sorry for the bad English - I am writing through a translator. Whoever does not have the game bugged (like me), it helps me - disable the windows service, "windows audio", start the game, then again you can start the "windows audio" service.

[Baleur]

No, i already tried completely disabling Process Lasso, makes no difference.

[Slice]

For the process lasso owners: The solution is assigning the CPU affinity to "all cores" for the MSFS process.

[Baleur]

Not for me. Disabling process lasso doesnt change anything, plus it was already on all cores while turned on. I dont get this, we must be having ten different issues producing the same problem.

[Manwith Noname]

Ultimately, it's a very similar issue, you likely have another piece of software interfering in some way. Another option is problematic redistributable installs. You can try downloading and running this...

https://github.com/abbodi1406/vcredist/releases

[Baleur]

But it worked before this update....

[xwing]

引用自 Slice：

For the process lasso owners: The solution is assigning the CPU affinity to "all cores" for the MSFS process.

And all Steam processes too.