Hi there, I did successfully deploy the new v2 of Windows Admin Center (Build 2.4.2.1, 2410). I've got a Dell HW as a server, where I have Windows Server Core 2019 running. The server core runs as a Hyper-V host. It has been nice and easy to run Hyper-V with Windows Admin Center so far but the most recent v2 seems to be causing all kinds of head-ache. Seemingly everything worked. WAC install can be run from admin cmd as is Setup TCP port as 44301 -> ok Check firewall -> ok ensuring that my star-certificate can be used -> ok set trusted hosts as all -> ok set anonymous use as ok -> set windows authentication as the method -> ok setting my own FQDN as de-facto connect point -> ok it even checks that PS remoting is on -> ok I tested via powershell that my firewall works starting WindowsAdminCenter service running from a client pc the https://FQDN:44301 Great, it works, loads bootstrap and everything I get in with my admin (<local machine>\Administrator) Now here is where it gets funny I try to click to my "Server" -> "ajax error 500" this is so weird, no real error stack kind of getting a feeling that the WAC v2 is just incomplete How do you get pass this point? (above the screen cap on the error after clicking my Server "Hyperpilvi" -> "Connection error") Any ideas how to resolve this one?

I spent way too long on this, but the post from @Randall Okwei as well as a lot of trial and error allowed me to get this working without changing the service account from Network Service to Local System. This has to be some kind of bug in WAC. Anyway, hopefully the below helps some folks that are stuck, and maybe someone else facing this issue can pinpoint which step below actually fixed things: When the ajax 500 error appeared, I noticed the following Schannel error in the System event log: A fatal error occurred when attempting to access the TLS server credential private key. The error code returned from the cryptographic module is 0x8009030D. The internal error state is 10001. The SSPI client process is WindowsAdminCenter (PID: 9948). If you are importing a PEM cert, you may want to try this article to convert your certificate to PFX via OpenSSL. I already had a PFX cert and this article ultimately didn't fix things for me, but may be useful for some. I noticed the self-signed cert (which works properly under the Network Service account) has Basic Constraints enabled. So, within my Windows CA, I duplicated the Web Server template, changed the compatibility to Server 2008 R2 and enabled the extension "Basic Constraints" and made it critical. Probably the most important step: With a cert from the new template imported into my Personal computer store, I right-clicked the cert --> All Tasks --> Managed Private Keys... I added the following permissions to match self-signed cert: Network Service account for the local machine: Full Control Users group for local machine: Read Probably the second most important step: Reinstall WAC and point to the new certificate. I was unable to get the Set-WACCertificateSubjectName command to actually apply the new cert. The Set-WACCertificateAcl gave an error in the WAC configuration log that was unfortunately overwritten during the reinstall, but it implied it couldn't read the private key properly. I would recommend starting with steps 3 and 4 to see if that fixes it, otherwise it appears the Basic Constraints extension is required. I was NOT able to get this to work just by changing the private key permissions on an existing setup that was broken, which makes me think the private key permissions change plus the reinstall is what will fix it.

How to pass "ajax error 500" with Windows Admin Center 24.10 (v2)

Ville Tuulos 15

Hi there,

I did successfully deploy the new v2 of Windows Admin Center (Build 2.4.2.1, 2410). I've got a Dell HW as a server, where I have Windows Server Core 2019 running. The server core runs as a Hyper-V host. It has been nice and easy to run Hyper-V with Windows Admin Center so far but the most recent v2 seems to be causing all kinds of head-ache. Seemingly everything worked.

WAC install can be run from admin cmd as is
- Setup TCP port as 44301 -> ok
- Check firewall -> ok
- ensuring that my star-certificate can be used -> ok
- set trusted hosts as all -> ok
- set anonymous use as ok ->
- set windows authentication as the method -> ok
- setting my own FQDN as de-facto connect point -> ok
- it even checks that PS remoting is on -> ok
I tested via powershell that my firewall works
starting WindowsAdminCenter service
running from a client pc the https://FQDN:44301
- Great, it works, loads bootstrap and everything
- I get in with my admin (<local machine>\Administrator)
Now here is where it gets funny
I try to click to my "Server" -> "ajax error 500"
- this is so weird, no real error stack
- kind of getting a feeling that the WAC v2 is just incomplete
- How do you get pass this point?

ShotOnError_WAC_2410_AjaxError_2025-04-06

(above the screen cap on the error after clicking my Server "Hyperpilvi" -> "Connection error")

Any ideas how to resolve this one?

Ville Tuulos 15 Reputation points

2025-04-06T20:34:25.9566667+00:00

Thinking if the Windows Hyper-V Server 2019 (Build 10.0.17763) starts to be too old for WAC v2? I just rolled back to Windows Admin Center 2110.2 version and it works like a charm. I updated within the v1 code line to more recent version of Windows Admin Center.

Any other similar experiences? Do I just need to start letting go of my beloved 2019 core, and start aiming to version 2025 instead?
Jonathan Loftus 0 Reputation points

2025-04-17T15:13:13.34+00:00

I'm having the same issue right now, and I don't believe server version to be the cause.

I've deployed the new v2 of Windows Admin Center (Build 2.4.2.1, 2410) on both server 2025 and server 2022. Both times I'm unable to add new resources, and I get the ajax 500 error when I'm using my star-certificate.

When using the self-signed certificate generated at installation it works great.
Henry Ofor 10 Reputation points

2025-04-18T16:07:03.57+00:00

Try this: "Open services, find windows admin center, go to the log on tab. It'll probably be set to network service by default, switch it to local system and restart the service. "
https://techcommunity.microsoft.com/discussions/windowsservermanagement/windows-admin-center-2410-cannot-add-computers/4358654/replies/4363099
Sergey Gryaznov 5 Reputation points

2025-08-28T08:49:38.7633333+00:00

Go to Services and switch WAC service from Network System to Local System

6 answers

Funky Funky 0 Reputation points

2025-09-15T05:33:41.83+00:00
I spent way too long on this, but the post from @Randall Okwei as well as a lot of trial and error allowed me to get this working without changing the service account from Network Service to Local System. This has to be some kind of bug in WAC. Anyway, hopefully the below helps some folks that are stuck, and maybe someone else facing this issue can pinpoint which step below actually fixed things:

When the ajax 500 error appeared, I noticed the following Schannel error in the System event log:

A fatal error occurred when attempting to access the TLS server credential private key. The error code returned from the cryptographic module is 0x8009030D. The internal error state is 10001. The SSPI client process is WindowsAdminCenter (PID: 9948).

If you are importing a PEM cert, you may want to try this article to convert your certificate to PFX via OpenSSL. I already had a PFX cert and this article ultimately didn't fix things for me, but may be useful for some.

I noticed the self-signed cert (which works properly under the Network Service account) has Basic Constraints enabled. So, within my Windows CA, I duplicated the Web Server template, changed the compatibility to Server 2008 R2 and enabled the extension "Basic Constraints" and made it critical.

Probably the most important step: With a cert from the new template imported into my Personal computer store, I right-clicked the cert --> All Tasks --> Managed Private Keys... I added the following permissions to match self-signed cert:

Network Service account for the local machine: Full Control

Users group for local machine: Read

Probably the second most important step: Reinstall WAC and point to the new certificate. I was unable to get the Set-WACCertificateSubjectName command to actually apply the new cert. The Set-WACCertificateAcl gave an error in the WAC configuration log that was unfortunately overwritten during the reinstall, but it implied it couldn't read the private key properly.

I would recommend starting with steps 3 and 4 to see if that fixes it, otherwise it appears the Basic Constraints extension is required. I was NOT able to get this to work just by changing the private key permissions on an existing setup that was broken, which makes me think the private key permissions change plus the reinstall is what will fix it.
Please sign in to rate this answer.
Randall Okwei 26 Reputation points

2025-09-15T13:17:43.46+00:00

You shouldn't have to restart the service. It should just automatically start working and all cases where I had this problem. The fix that I proposed solved the issue. The certificate I used was from a CA. I don't use self-signed certs
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

How to pass "ajax error 500" with Windows Admin Center 24.10 (v2)

6 answers

Your answer