Error message: The procedure entry point GetSystemCpuSetInformation could not be located in the dyna | Enshrouded | Page 1

worthy musk Jan 24, 2024, 8:21 PM

#

Ill turn this into a thread and repete what i said just in case others come through I ran into this issue as well. I running windows Server 2012 R2. I believe this might be due to the function its trying to call not being supported based on the windows doc i read. but i have not confirmed this yet: https://learn.microsoft.com/en-us/windows/win32/procthread/getsystemcpusetinformation will defiantly ping you if i receive a response

worthy musk Jan 24, 2024, 9:41 PM

#

@Akitorino-Adrian fyi to keep track of folks having this issue

glad orbit Jan 24, 2024, 9:59 PM

#

Hopefully we will get a Solution soon

#

I was looking in the Internet and it says this Feature is only Supported Server 2016 and higher

dull grove Jan 25, 2024, 2:29 AM

#

I'm on Windows Server 2012 R2 as well and getting the same issue.

#

Looks like it's time to upgrade it to server 2019 at least

#

Microsoft is charging in the neighborhood of $600 for a Server 2019 16-core license. Screw that.

worthy musk Jan 25, 2024, 3:27 AM

#

iv seen a 2022 single server license going for 300 on amazone oem

dull grove Jan 25, 2024, 3:47 AM

#

I might just ebay one

#

a license and dvd

#

I have a Dell Power Edge R710 with 2x Xeon 6 core processors and 128GB of ram. It's a bit dated but should still run 2019 at least

#

it's a ebay special also

#

I also have a Dell R710 running Ubuntu 22.04 but I'm not too thrilled about having to run Wine for the server.

austere hare Jan 25, 2024, 4:10 AM

#

this seems like it'd be the msvcrt version

worthy musk Jan 25, 2024, 4:31 AM

#

iv got a R610 and iv doing a bit a digging. iv found some folks saying they got drivers to work in 2022 so id imagine your R710 should have a chance running a newer os

worthy musk Jan 25, 2024, 5:27 PM

#

Error message: The procedure entry point GetSystemCpuSetInformation could not be located in the dyna

tropic coral Jan 26, 2024, 2:26 PM

#

Just wanted you guys to quickly verify the update that rolled out this morning did not in fact fix this issue for you?

worthy musk Jan 26, 2024, 2:26 PM

#

I tried it and still recived the error

night island Jan 27, 2024, 10:49 AM

#

dull grove Looks like it's time to upgrade it to server 2019 at least

uhm just an FYI, for non commercial use you don't technically need to license your windows server OS on 2016 and newer. You just have to live with the watermark.

worthy musk Jan 27, 2024, 8:04 PM

#

night island uhm just an FYI, for non commercial use you don't technically need to license yo...

can you explain this a little more?

night island Jan 27, 2024, 9:09 PM

#

worthy musk can you explain this a little more?

If you're just going to use your windows server at home not for profit you don't need to buy a license. Just use it. But you will have an watermark that says 'Activate Windows' in the bottom right corner. You just need a copy of the OS which you can find on the internet.

dull grove Jan 28, 2024, 1:02 AM

#

@night island thanks, I bought one anyway from ebay for $38, has the DVD with a 16-core standard license.

#

However, I have installed the eval edition and will use a Powershell script to license it when it gets here.

#

eval will run for 180 days

slow ridge Jan 28, 2024, 1:09 AM

#

I had the same error GetSystemCpuSetInformation on the Server 2012 R2 running on ESXi. I just downloaded Server 2016 Eval for free from Microsoft and moved the server to the newly built 2016 server and it worked perfectly first go.

I also had the same error attempting to run the server on Windows 7. But server 2016 resolved the issues.

#Error message: The procedure entry point GetSystemCpuSetInformation could not be located in the dyna