[Bug] SetThreadDescription on Windows Server 2012 #178
Replies: 9 comments 14 replies
|
same error as me #229 can u guys take a look @titanium-cfx @promethium-cfx @technetium-cfx |
|
Can you try installing this and see if that helps? https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#visual-c-v14-redistributable Seems that some Windows Server versions don't bundle it |
|
Actually, ignore this. The issue is that cfx-server unconditionally calls the |
|
Thanks, we are looking into this. |
|
A fix for this bug has been implemented and is available in Hotfix 6. Please try again and let us know if the issue persists. Thanks for your help! |
|
Another fix for this bug has been implemented and is available in the August 4 patch. Please try again and let us know if the issue persists. Thanks for your help! |
|
Test on b104 and it is working. Although if you have Legacy Fx servers running it will crash cfx-server. But if they are not running it starts just fine. So I would consider this a different issue and this current one to be fixed and working |
when im joining the server i got this crash @wolfram-cfx @Gogsi idk what is this but ok |




Uh oh!
There was an error while loading. Please reload this page.
Summary
When starting cfx-server an error SetAThreadDescription appears causing the server to not start.

Issue type
Server
Repro rate
Always
Server build version
94
OS
No response
CPU
No response
GPU
No response
RAM
No response
Storage type
None
Connection type
None
ISP and bandwidth
No response
DxDiag
No response
Network graph
No response
Platform
Windows
OS version / distribution
Windows Server 2012 R2 Standard
CPU
Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
RAM
32 GB DDR3
Using txAdmin?
Yes
Hosting provider
Self-hosted
Machine type
Dedicated
/perf endpoint output
No response
DDoS protection
No response
ulimit -n value (Linux only)
No response
Docker Compose file (Docker only)
No response
Steps to Reproduce
1.Install Cfx Server for GTAV Enhanced release 94/artifact on Windows.
2.Run Cfx-server
3.
Expected Behavior
Server should start and run successfully
Actual Behavior
Server does not start but instead presents an error.

Evidence
No response
Additional Context
No response
All reactions