So i bought the Game on my Main Profile and i have a Dedicated Server Steam account that i use for hosting servers. So i got family share on so i get access to the Dedicated server tool . So i downloaded it and i try to host a server. I also Downloaded it Manually Through Steam CMD using app id 4129620 for context. But using both methods i cant start the server. When i click the StartServerForeground the command box flashes and immediately disappears and it wont start, I also Tried the Exe windroseServer. Im using a Old Dell Poweredge R710 with 128gb of Ram Ive Tried Verifying it but i dont own the game on that profile. Is that why its not starting? I host games like Ark Survival Ascended on it and it works fine. Its a Windows Server 2016 OS if that matters
#Dedicated Server wont Start
1 messages · Page 1 of 1 (latest)
Which CPU ?
12 CPUs x Intel(R) Xeon(R) CPU X5670 @ 2.93GHz , And it runs Headless with no GPU i think
Probably same as this:
https://discord.com/channels/1260209458924224542/1493632907628118246
The game client requires AVX1 instructions on the CPU, the server might have the same requirement, though this needs to be confirmed by the devs, @viral salmon
Having the same issue on Windows Server 2022
@maiden pumice Does the Dedicated Server tool require the account to own the game to run?
Not at all, you do not even need Steam client at all.
The DS package was granted to Anonymous login as well as logged in users and base game ownership.
Ive never tried seeing if AVX1 is on - idk if can - Any clue how i can check? its a Virtual Machine hosted thru Vmware ESXi
Your CPU does not support it, which is why I wanted to know which one you have.
I always either check TechPowerUp hardware database or Intel's own website, or I just remember:
https://www.intel.com/content/www/us/en/products/sku/47920/intel-xeon-processor-x5670-12m-cache-2-93-ghz-6-40-gts-intel-qpi/specifications.html
so does that mean i cant run the server? 🙁
Potentially, yes. Again, this needs to be confirmed by the game devs.
ah ok so Bambino is a dev? just waiting on a confirmation from them?
Aye aye, Cap'n 
roger! thanks i hope this can be worked arounnd =/
Just sharing, these commands can be ran in Powershell to get an easy True/False regarding AVX1 instruction assuming you cant easily find it online (e.g just a way to check if the PC sees you have instruction for it ha)
Expected reply would be
~ From pwsh : PowerShell 7.6.0
~ From the IsSupported check: True
winget is only needed if
pwshdoesnt reply / isnt on 7.6.0
whats the command?
Its in the message.txt ~ cant share them directly as Automod doesnt like commands ha
IsSupported returns True for me but the server never starts
I'm also running on Win Server 2022
Just means that the CPU may not be the cause; best bet is gonna be logs
You still need to have corresponding MSVCR package for the app, in this case it's vcredist 2022-2026.
And yea, do provide the logs.
It just gives no output and instantly closes as if nothing happened. The exe does the same.
the .bat and the .exe
Windows Event Viewer will have the log info.
Confirmed AVX I changed my VM's processor type to host in ProxMox
So it is, meaning older Intel Xeons are kinda out.
how do i run the Command to see?> lol
I had the same issue and this was the fix for me as well.
well this sucks..
I don't have eventviewer on servercore and the CPU issue doesn't seem to be relevant for me, mine is even an AMD Ryzen one and its set to host passthrough mode.
this is all i see
How did these guys make it so complicated to run a dedicated server on a server machine god
It runs out of the box on my Windows VM without a hitch. The issue isn't the DS tool.
Seriously. I can run like 5 ASA server and i cant run this i dont understand Why this server needs this AVX1 thing ( idk what it is lol )
Ok seems like the issue for me was running on windows server core ( the one without desktop env)
I installed the one with desktop env and its ok, seems like the issue was directx installation..? 
Is the Windows build the same between the 2 you had ?
The server is completely headless.
I had my VM running as x86-64-v2-AES and flipped it to Haswell-NoTSX as its an e5-2690v3 and it's now launching, just taking forever for the initial boot. I did give it significantly more RAM than I'd expect it to need, so I'm guessing thats the delay.
the same windows server 2022 ISO , it just offers you to install core or the one with full desktop env, i just made another VM with the other installation and everything worked.
¯_(ツ)_/¯
I was getting an error previously DSOUND.dll not found which chatgpt said missing DirectX runtime (DirectSound component) and i couldnt even install directx on the headless one.
You mean DirectX Runtimes June 2010 (which that DLL is part off) ?
Might be why 😂
so is there any work around for my issue?
bump, exactly the same problem, works on one machine and wont stsart on my headless server machine. Just starts and then exits immediatly.
@blazing coyote following your thread from April where you able to get the server running?
Another issues now
@loud bloom I am still trying to figure out why the batch points to 'WindroseServer-Win64-Shipping.exe' it server exe is not in the R5 folder..
tried x32 command line used power shell.. going to stand up VM x32 and try...
@waxen python ultimately I was not able to truthfully I haven't really tried since then because my server host has an older processor and did not have avx1 compatibility so according to what I was told and it would not start the server ever so I ended up just buying a dedicated server which is not my ideal situation I'd rather not pay for it but it is what it is if I want to play the game unless they change it so that way it doesn't require a vx1 to start up I don't know if I'm going to be able to but when I get home I can double check and see if it starts up
@blazing coyote Thanks I am attempting to run using SteamCMD on a PowerEdge T310. I truly didn't think about hardware.. I have run Rust server from 'her' 2016 x64 OS..
Have you tried the install from the Steam tools. I might try that if they allow the steam client on server...
I've ran it through the steam dedicated server tool as well as through downloading it through Steam CMD and it just when I go to collect the launch button it just a black terminal appears and then immediately disappears
When I talk to the guys earlier in this chat they said it needs a vx1 to start up and because my processor is so old it doesn't have that capability which the server won't start up from my understanding
Processor: Intel(R) Xeon(R) CPU X3440 @ 2.53GHz (8 CPUs), ~2.5GHz
Below minspec on AVX, so it won't run.
set up a quick VM windows 10 the silly server started.. lets see what happens nest....
@blazing coyote thanks your info helped...
yeah it still wont launch sad bvut eh lol
They probably updated the dedic with the recent patch, mind the date of that comment.
Been running it since launch day
Also, AVX2 was introduced in Intel Haswell (i.e. Intel Core iX 4000 desktop), AVX1 is older (Sandy Bridge)
EDIT: Corrected the AVX versions
I stand corrected, I guess mine does have it although I never found that setting in the bios anywhere. I'll delete my other message.
Honestly, i wasn't even aware of there being any kind of similar setting in the BIOS up until people started reporting their findings here :3
I can't believe that would be a requirement for the server it seems really lightweight. @blazing coyote jave you tried copying over the files from the windrose folder and trying that. That's what I use. You have to update that each time the game is updated, but works fine for me.
hey @maiden pumice So the Gave needs AVX1 ti Start right?
yeah nothing works on my home machine cuz its a older processor that does not ave AVX1 - so i had to pay to host it sadly.