Cannot create a Windows Server Failover Cluster on a non-domain-joined Azure VM running Windows Server 2022 Datacenter (Build 20348).

Hello,

The error you are seeing with New-Cluster in a Windows Server 2022 workgroup environment is tied to how Failover Clustering handles the creation of the cluster database and the administrative access point. Even though workgroup clusters with -AdministrativeAccessPoint None are supported starting with Windows Server 2016, the “The system cannot find the file specified” error usually indicates that the cluster service cannot initialize the cluster database path or required system objects because of missing prerequisites.

There are a few critical points to check. First, ensure that the Failover Clustering feature is not only installed but that the Cluster Service is running on the node. Run Get-Service ClusSvc and confirm it is set to Automatic and started. If the service is not running, New-Cluster will fail with this error.

Second, in a workgroup configuration, you must explicitly provide a static cluster name and ensure that the local node has administrative rights to create the cluster database under %SystemRoot%\Cluster. Verify that the folder C:\Windows\Cluster exists and that the SYSTEM account has full control. If this folder is missing or permissions are incorrect, the “file not found” error will occur.

Third, confirm that the node name you are passing to New-Cluster matches the actual hostname exactly. In your command, you used -Node Amp2TestDatabas. If that is a typo and the VM hostname is Amp2TestDatabase, the mismatch will cause the cluster creation to fail with this error. Cluster creation is strict about node name resolution, and in a workgroup environment there is no DNS or AD to correct it.

Finally, when using -AdministrativeAccessPoint None, you must run the command as a local administrator and ensure that the local security policy allows creation of objects by the cluster service. If you previously attempted with -AdministrativeAccessPoint DNS, that will not work in a workgroup because there is no domain controller to register the cluster name. Stick with None, but make sure the prerequisites above are satisfied.

In short, the most likely cause here is either the typo in the node name or missing cluster database folder/permissions. Correct the node name, verify %SystemRoot%\Cluster exists, and confirm the Cluster Service is running before retrying. If all of those are correct and the error persists, then it may be a regression in Windows Server 2022 workgroup clustering, in which case you should open a support case with Microsoft as there is no supported workaround beyond ensuring prerequisites are met.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

Domic Vo.